Business Analyst Work Plan
Transcript of Business Analyst Work Plan
![Page 1: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/1.jpg)
Business Analyst Work Plan
Presented by:Billie Johnson, CBAP® CSM
![Page 2: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/2.jpg)
AgendaTopic
Introduction
Overview of a Business Analysis Work Plan
Initiating a Business Analysis Effort
Components of the Business Analysis PlanningBusiness Analysis Work PlanBusiness Analysis Communication PlanRequirements Management Plan
Summary
![Page 3: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/3.jpg)
Seminar Goals
• Goals– Exposure to standards for business analysis planning– Identify efficiency opportunities– Appreciate the benefits of planning your business
analysis tasks
![Page 4: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/4.jpg)
OVERVIEW OF BUSINESS ANALYSIS PLANNING
What is a business analysis work plan?Why should I create a work plan?
![Page 5: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/5.jpg)
What is Business Analysis Planning?
BABOK Chapter 2
![Page 6: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/6.jpg)
Business Analysis Planning Sequence
BABOK Chapter 2
Plan Business Analysis Approach
Conduct Stakeholder
Analysis
Plan Business Analysis Activities
Plan Business Analysis
Communication
Plan Requirements Management
Process
Manage BA Performance
![Page 7: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/7.jpg)
Benefits of Business Analysis Planning
• Provides clear business analysis approach and scope• Establishes Business Analysis Communication vehicle and
frequency• Establishes estimates time commitments for:
– Business analyst(s)– Stakeholders
• Allows determination of business analysis status• Establishes business analysis deliverables• Spending more time on requirements can actually accelerate
software development• Provides you a negotiation tool
![Page 8: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/8.jpg)
Results?
• Creditability of Business Analyst– Keeps you organized– Make the most of stakeholder time
• Efficiencies gained in business analysis planning• More accurate estimates
• Increased probability of Project Success
![Page 9: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/9.jpg)
How much time should be spent on development of requirements?
• Percentage of total project effort spent on requirements development:– Wiegers sites success devoting 15% -18% on small
projects– Young sites approximately 8% to 12% in Effective
Requirements Practices *– Large project benchmark data indicates 3.7% to 10% -
Jones 2000. *
* Unsure how many of these were successful
![Page 10: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/10.jpg)
INITIATING A BUSINESS ANALYSIS EFFORT
Outputs of Initiation PhaseIdentification of Project CharacteristicsStakeholder Analysis
![Page 11: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/11.jpg)
Outputs of the Initiation Phase
• Business Need– Product Vision
• Required Capabilities• Solution Approach• Solution Scope• Business Case
– Initial Risk Assessment– Cost/Benefit Analysis
• Project Request
These outputs represent culmination of high/mid level analysis.
Ensure that these outputs are SMART* appropriate and buy-in is obtained prior to planning detailed business analysis activities
* Specific, Measurable, Achievable, Relevant and Time-bound
BABOK Figure 4-1Jogger - Page 20
![Page 12: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/12.jpg)
Influencing Factors BA Effort
Factors that accelerate• Providers’ Skill set
– Skilled/experienced analysts– Application experienced
developers• Extensive customer involvement
– Appropriate user representatives– Timely response to questions
• Project Characteristics– Reuse from previous projects– Clear/stable vision and scope
• Frequent informal reviews
Factors that lengthen• Stakeholders
– Geographically distributed– Language barriers– Many or diverse user classes– Weak decision-making process
• Project Characteristics– Unfamiliarity– Large project– Concurrent components– Complex interactions– External dependencies
• No Business Analysis process
![Page 13: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/13.jpg)
Project Characteristics
• Project Type• Business Analysis
Approach• Project Complexity
![Page 14: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/14.jpg)
Project Types
• Process improvement• Organizational change• New software
development– In-house– Outsourced
• Software maintenance or enhancement
• Software package selection
• Feasibility studies• Integration• Others?
BABOKSection 2.3.4.2, 2.4.4.3
Opportunity for PM
Alignment
![Page 15: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/15.jpg)
Business Analysis Approaches• Characterize the business analysis approach
– Plan-Driven– Change-Driven– In practice, most projects fall somewhere between these
extremes• Determination based on:
– Timing of Business Analysis Work– Formality and level of detail of BA Deliverables– Requirements Prioritization / Change Management– Business analysis Planning Process– Communication with Stakeholders– Project Complexity BABOK
Section 2.1.4
![Page 16: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/16.jpg)
Project Complexity Increase as These Increase
• Number of stakeholders• Number of business areas affected• Number of business systems affected• Amount and nature of risk• Uniqueness of requirements• Number of technical resources required• Non-Existent “As-Is” supporting documentation• …
BABOKSection 2.1.4.8
![Page 17: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/17.jpg)
Stakeholder Analysis
• Stakeholder Identification• Stakeholder Complexity• Stakeholder Attitude and Influence• Stakeholder Authority Levels for Business Analysis Work
You will be building stakeholder profiles
BABOKSection 2.2
![Page 18: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/18.jpg)
Stakeholder Complexity Increases as These Increase
• Number and variety of user groups could require– Different approaches– Differing plans/reporting– Variance of formality– Impact a stakeholder’s ability to engage
• Number of interfacing business processes and automated system– Consider involvement of stakeholders as applicable
BABOKSection 2.2.4.2
![Page 19: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/19.jpg)
Stakeholder Attitude and Influence
• Attitude toward:– Business goals, objective, solution approach– Business analysis– Collaboration– Sponsor
• Influence over– Project– Organization– Other stakeholders
BABOKSection 2.2.3, 2.2.5.3
If the influence required vs. influence perceived is a mismatch; risk mitigation will be required
![Page 20: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/20.jpg)
Stakeholder Authority Levels
• Consider who will:– Approve deliverables– Inspect and approve requirements– Request and approve changes– Approve the requirements process to be used– Review and approve traceability structure– Veto proposed requirements or solutions
![Page 21: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/21.jpg)
Project Characteristics Reflection
• What about this project I have been assigned?– What type of project is this?– What Business Analysis Approach will be taken?
• Plan-Driven, Change-Driven, or some Hybrid
– What is the experience level of the BA assigned?– How complex is this project?– How risky is this project?– How complex is the stakeholder group on the project?
![Page 22: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/22.jpg)
COMPONENTS OF BUSINESS ANALYSIS PLANNING
Plan Elicitation ActivitiesPlan Requirements Analysis ActivitiesPlan Solution Assessment and Validation ActivitiesEstablish Communication PlanEstablish Requirements Management Plan
![Page 23: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/23.jpg)
Plan Elicitation Activities
Elicitation Portion of BA Plan
Stakeholder List, Roles and
Responsibilities
Business Analysis Approach
Organizational Process Assets
![Page 24: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/24.jpg)
Elicitation Plan Purpose• Ensure involvement of a combination of stakeholders
providing:– Collaboration– Domain knowledgeable and experience– Representation of typical users– Authority to reach closure on requirements– Commitment of time and energy
• Provides focus on requirements efforts and high-priority stakeholders
• Encourages management support of elicitation• Promotes effective use of time
![Page 25: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/25.jpg)
Elicitation ConsiderationsTechnique Stakeholder Involvement TimingBrainstorming Requires access DaysDocument Analysis
Does not require access Days or weeks
Focus Groups Requires access WeeksInterfaceAnalysis
Does not require access Days or weeks
Interviews Requires access Days or weeksObservation Requires Access Days or weeksPrototyping Requires Access Hours, days or weeksRequirements Workshops
Requires Access Days or weeks
Survey / Questionnaire
Requires Access, not physical
Weeks or months
![Page 26: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/26.jpg)
Plan Requirements Analysis Activities
Requirements Analysis Section of BA Plan
Business Analysis Approach
Organizational Process Assets
Stakeholder List, Roles and
Responsibilities
![Page 27: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/27.jpg)
Requirements Analysis Tasks
• Organize Requirements• Specify and Model Requirements
– Define Assumptions and Constraints• Verify Requirements• Validate Requirements• Prioritize Requirements
![Page 28: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/28.jpg)
Choosing the Right Analysis Models?Transactional Business Domains• Describes How – Functional decomposition, Use cases, User
stories, Process modeling, Prototyping, • Describes Why – Actors, Business rules analysis
Structural Domains• Describes What – Data models, Data Dictionary, Glossary• Describes Why – Business rules for data
Dynamic Domains• Describes When – Event-response tables, State diagrams,
Sequence diagrams, Data flow diagrams• Describes What – Data Models (and who if interfaces involved)
Control Oriented Domains• Describes Why – Business rules, Decision analysis• Describes What – Data Models
![Page 29: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/29.jpg)
Plan Solution Assessment and Validation Activities
Solution Assessment and Validation Section of BA Plan
Organizational Process Assets
Stakeholder List Roles &
Responsibilities
Project Characteristics
![Page 30: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/30.jpg)
Solution Assessment and Validation Activities Estimations
• Solution Assessment– Assess solution options– Allocate requirements
• Solution Validation– Technical design review– Review of test plans and test cases– Address inquiries and defects
• Organizational Readiness– Transition requirements– Implementation support
![Page 31: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/31.jpg)
Plan Business Analysis Communication
Business Analysis Communication Plan
Organizational Process Assets
Stakeholder List, Roles, and Responsibilities
Business Analysis Plan /
Approach
BABOK – Section 2.4.3
![Page 32: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/32.jpg)
Business Analysis Communication Plan Purpose
• Approved communication plans ensure collaboration• Involvement of knowledgeable and experience domain
stakeholders• Representation of typical users
![Page 33: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/33.jpg)
Elements of Communication Planning
• Geography• Culture• Project Type• Frequency• Formality
![Page 34: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/34.jpg)
Stakeholder Communication Considerations
• What needs to be communicated?• How does it need to be communicated?• Who is the appropriate audience?• When should the communication occur?• Stakeholder needs and constraints:
– Physical location– Communication approach– Required types of communication– Requirement types and elicitation techniques– Requirement package communications– Time and resource availability
![Page 35: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/35.jpg)
Plan Requirements Management Process
Requirements Management Plan
Organizational Process Assets
Business Analysis Plan
Business Analysis Approach
![Page 36: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/36.jpg)
Requirement Management Components
• Repository– Ensure single source– Accessible
![Page 37: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/37.jpg)
Requirement Management Components (continued)
• Traceability Architecture– Associations– Necessity– Effort– Subset– Cover– Value
![Page 38: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/38.jpg)
Requirement Management Components (continued)
• Requirement AttributesUnique Identifier Priority
Author Resource Assignment
Ownership Revision Number
Source Complexity
Cost Risk
Stability Status
Urgency
![Page 39: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/39.jpg)
Requirement Management Components (continued)
• Requirement Prioritization Process– Risks– Cost– Benefits– Implementation Time– Dependencies– Resource Constraints
![Page 40: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/40.jpg)
Requirement Management Components (continued)
• Change Control Process– Request for change process– Change Request Form Definition– Who performs impact analysis– Who authorizes changes
• Gauge likely volatility of change
![Page 41: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/41.jpg)
Practical Example
![Page 42: Business Analyst Work Plan](https://reader035.fdocuments.in/reader035/viewer/2022071601/613d3749736caf36b75ab126/html5/thumbnails/42.jpg)
In Summary…
• Planning provides– Opportunity to determine tasks and time estimates for
effective requirements development– Highlight BA responsibility to raise issues to
management (PM) such as plan revisions, lack of user involvement, scope issues, etc
• Go forth confidently and humbly to negotiate and navigate the environment.