Applying Business Analysis Methodologies to Build Empowering IT Systems in Public Health

Transcription

1 Applying Business Analysis Methodologies to Build Empowering IT Systems in Public Health

2 Presenters: Valerie Britt, MBA, BSEE, CBAP Project Lead, Strategic Application International Corporation (SAIC) Consultant to Centers for Disease Control and Prevention (CDC)/ffice of Infectious Diseases (ID) Lynda Vidot, BSCS, CBAP Senior Business Systems Analyst, Strategic Application International Corporation (SAIC) Consultant to Food and Drug Administration (FDA)/ffice of Regulatory Affairs (RA)

3 Presentation Goals A retrospective of a complex IT project success as a result of: Expert application of BA competencies and methodologies Practical application of BA Techniques in defining: Business architecture System architecture

4 PLDAT Approach Case Study is organized using PLDAT rganization Business Architecture Process rganization Location System Architecture Data P D A T L Application Technology Examine the Expert BA s role in each area as it relates to the project Application

5 Learning bjectives Audience will understand how BABK techniques and tasks can be applied to attain successful problem resolution on complex projects

6 Intro to Case Study Project to implement HL7 Message standard for electronic test orders and results (ETR) to support submission of specimens to CDC for identification and reference testing Who: CDC, State Public Health Laboratories When:18-month timeline Where: multiple domestic locations (Pilot) Why: Data quality, timeliness of test orders and results; standardized vocabulary Project complexity Layers of Architecture Size of team Geography Number of processes

7 Project verview

8 Business Architecture rganization Creates a Conceptual Model of the Processes, rganization, and Location that are impacted by the Solution D A T Allows analysis of the work, competencies, structure and physical constraints that the business must consider to maintain a sustainable solution Application

9 rganization L D A T Process Application... the discomfort of not knowing is an essential part of the process of creativity and change. Nina Utne

10 Processes Challenge: Determining new processes and process owners that are needed to support the desired future state wner?

11 Processes Methodology used: Prioritization Tasks: Elicitation Documentation, Specify/Model Requirements Techniques used: bservation, Process Modeling, Prototyping, Scenarios & Use Cases, Scope Modeling utputs: Process Flows, Solution Requirements, Business Rules, Prioritized Requirements Team: Business Systems Analyst as a Strategist, Information Architect, SME, Project manager, Implementation SME, Business Sponsor Underlying Competencies: Communication Skills, Interaction Skills, Analytical Thinking and Problem Solving

12 Processes Lessons Learned Begin with Scope Modeling prior to prioritization to understand project scope Ensure that process drivers and constraints for the entire domain are understood Plan for prototypes especially to give stakeholders a feel for new or modified workflow tasks that are critical

13 rganization P L D A T rganization Application People don't resist change. They resist being changed! Peter Senge

14 rganization Challenge: Reaching Consensus for To-Be State Constrained by rganizational Controls

15 rganization Methodology used: Prioritization, Facilitation & Negotiation Tasks: Elicitation, Requirements Communication, Requirements Analysis, Solution Assessment (Transition Requirements) Techniques used: Acceptance & Evaluation, Brainstorming, Business Rules Analysis, Lessons Learned, rganization modeling, Scenarios & Use Cases, Scope Modeling, Survey utput: Prioritized Requirements, Transition requirements Team: Project Manager, Business Systems Analyst, Information Architect, SME, Business Sponsor Underlying Competencies: Analytical Thinking and Problem Solving, Behavioral Characteristics, Business Knowledge, Communication Skills, Interaction Skills

16 rganization Lessons Learned Invest in Stakeholder Analysis, Business Rules Analysis, rganization Modeling, and Scope Modeling and Analysis in planning phase Identify and analyze business rules, constraints from the perspective of entire organizational domain rather from within each entity Ensure that each component within domain is represented in collaborative discussions with appropriate decision-making authority

17 rganization P D A T Location Application "It's better to get 1% of 100 people's effort than it is to get 100% of one person's effort. Zig Zieglar

18 Location Challenge: Consideration of Different Locations While Collaborating Virtually Project team dispersed geographically Setting up meetings to accommodate timezones Project team participation Project team representation

19 Location Methodology used: Prioritization & Facilitation, Voting Tasks: Business Analysis Planning & Monitoring, Elicitation, Requirements Analysis, Requirements Communications and Management, Solution Assessment Techniques used: Acceptance and Evaluation Criteria, Brainstorming, Lessons Learned (from other collaborative projects), rganization Modeling, Survey/Questionnaire utputs: Meeting Notes, Shared Network Resources, Regularly Scheduled Meetings (Communication Plan) Team: Business Analyst, SME, End User, Implementation SME, Project Manager, Sponsor Underlying Competencies: Analytical Thinking and Problem Solving, Behavioral Characteristics, Business Knowledge, Communication Skills, Interaction Skills

20 Location Lessons Learned Create a project organization chart Conduct Stakeholder Analysis Set and communicate timelines for reaching decisions Ensure communication plan considers all locations and that stakeholders agree to guidelines for sharing and communicating information

21 System Architecture rganization Creates a Conceptual Model of the Data, Applications and Technology used to support the Business Architecture P L Brings together system elements to create structural and behavioral capabilities that none could produce alone Application Uses BA methodologies techniques and tasks

22 rganization P L A T Data Application Information is not knowledge Albert Einstein

23 Data Messaging Challenge: Test rder and Test Results Data Requirements from Diverse Stakeholders

24 Data Messaging Methodology used: 5 whys, Bottom Up Tasks: Elicitation, Analysis, Design Techniques used: Requirements Workshops, Data Modeling utputs: Message Specification, Data Model, Business Rules Team: Business Analyst as a Strategist, Information Architect, SME, Business Sponsor Underlying Competencies: rganization Knowledge, Interaction Skills, Analytical Thinking and Problem Solving

25 Data Messaging Lessons Learned Identify Stakeholders at a granular level; individuals not organizations Commit to rules of order Ensure that methodology aligns with overall business architecture vision

26 rganization P L D T Applications Application Architecture is the work of nations - John Ruskin

27 Application Architecture Challenge: Build the Applications Architecture needed to support the Business Architecture

28 Application Architecture Methodologies used: Structured design, Bottom up approach Tasks: Analysis, Design Techniques used: Functional Analysis utput: Architecture to support Vocabulary, Message Structure, Business Rules Team: Business Analyst as a Systems Analyst, Information Architect, Enterprise Architect, Systems Architect, SME, Business Sponsor Underlying Competencies: Solution Knowledge, Analytical Thinking and Problem Solving

29 Application Architecture Lessons Learned Understand that the Statement of Work as a constraint must be managed Build the Application Architecture the same way you would a build a new workflow A business need is not enough justification to build services. You need rganizational buy-in from the Service users Support from Architects that report to a central group

30 rganization P L D A Technology Application Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clark

31 Technology Challenge: Validate technology direction Services riented Architectures have opportunities and challenges Understand the business needs of both the service provider and consumers Understand the pros and cons of the technology Governance is critical to the direction and the strategy

32 Technology Methodology used: Top Down Approach Techniques used: SWT Analysis, Decision Analysis utput: Documented Technology Context Diagram Team: Business Analyst as a Architect, Enterprise Architect, Systems Architect, SME, Business Sponsors Underlying Competencies: Solution Knowledge, Analytical Thinking and Problem Solving

33 Return on Investment According to Forrester Research, more than $100 billion is spent annually in the U.S. on custom and internally developed software projects. Evaluate the value of using expert BAs and BA methodologies and best practices Project Management Technique: EVM Compare current project value against historical data of known projects Less schedule variance Less rework Increased user adoption BA Task: BA Planning and Monitoring Create a schedule of BA activities that are part of the overall Project Schedule Monitor BA performance and make adjustments Evaluate the efficiency of the project investment for workflow harmonization and automation BA Tasks: As-Is Elicitation BA Task: Solution validation and assessment BA Technique: Key Performance Indicators and Metrics