As a member of your Business Analysis team, will undertake duties and responsibilities as a Sr. Business Analyst/Sr. Business Systems Analyst providing analytical support. MOST RECENT POSITION DESCRIPTION: Responsible for supporting my internal client (Conduent (aka StrataCare)) software's applications handling both triage to execution of enhancements (new functionality) and of defect (repairs) patches and Software Change Requests (SCRs). Wrote simple business requirements for one-off issues or complex specifications after Joint Application Requirement and Development (JAR/JAD) sessions. Their Software Delivery Life Cycle (SDLC) included: * Critical Design Review (CRD): which included a fifty thousand-foot view of all the external client's requirements and a quick assessment as to whether the current software had all or partial capability to address the external client's need. Items in the CRD had both an internal and external client identification number for traceability and each requirement was defined as being a Day 1 or Day 2 initiative. * Project Planning: which after reviewing the CRD was to define the timeline for the Joint Application Review (JAR), Joint Application Development (JAD) sessions, and Functional Specification Document (FSD) writing, as well as for Development, Testing (Quality Assurance), User Acceptance Testing by the BA and Implementation/Release Management handled by Configuration Management. Project Planning also took into consideration for Change Management to avoid what is called scope creep (where the external client tries to squeeze in additional requirements after the CRD is signed off). * Discovery: where there was a review of each requirement with the external client bundled in logic groups (e.g. User Interface (UI screens), Database (Db) and Engine (expectations for input, processing and output of the logic grouped requirement individually or holistically)). After each Discovery session, the BA sent out notes with Discovery, examples and follow-up items assignment to an owner and an expected reply time for each task. * Functional Specification Document (FSD) writing: this is where the CRD requirements. those that are not one hundred percent supported by the current application reside. This documentation included executive summary focused on the less technical person, specifications sections (input, processing and output) focused on the Developer and then Use Cases or sometimes called Use Stories directed to assist QA writing their test cases. The FSD often included examples within the requirements or if Database -specific it included the required data elements/database objects (DBO). DBO are used in SQL queries to help communicate to the Developer the data touchpoints versus using plain English. The document often includes Visio drawings. * SCRs: these items detail the specific programming that needs to be done, tied back to a CRD identification number or a Customer Relationship Management (CRM) case. Each SCR included a problem statement, steps to recreate or create an issue and often samples of the issue if a defect. SCRs include training tips and release notes. JOHN S SPOLL Spolzie59@gmail.com * 6313 South Bonham Street Amarillo TX 79118 (806) 223 - 6731

Highlights:

• Business Analysis
• Business Analyst
• Medical
• Management
• Management Information Systems
• Project Management
• Project Manager
• Risk Management
• Acceptance Testing
• Application Development
• sql
• it jobs
• agile
• software
• SDLC, TFS, JIRA,
• Microsoft Office Suite (Excel, Word, Project, Visio), CRM, SharePoint, SQL, ASP, SaaS, Multiple Bill Review Engines (BRE), Softtrax, Clinical Edits, ODG, Redbook, PBM, Business Process Modeling.