bam! business analysis methodologies. change-driven or plan-driven?
TRANSCRIPT
BAM!
Business Analysis Methodologies
www.mun.ca
Change-driven
or
Plan-driven?
www.mun.ca
Plan BA Approach
Approaches include• Waterfall development• Agile techniques • Lean/Six Sigma methods • Standard / formal organizational
methodologies
www.mun.ca
Plan –Driven Approach
Waterfall, Business Process Re-engineering
Requirements defined in advance Minimize uncertainty• Solution defined before implementation
to minimize risk and maximize control
• High risk of failure
• Formal sign-off events throughout project
• Project sponsor and advisors – approval authority for Solution requirements
• Timing of BA Activities: most at beginning
BA TASKS
www.mun.ca
Plan-Driven
Formality&Detail
High
Requirements docs
Change Management - necessary, justified
Communications formal
• Formal Change Request Forms and procedures
All documentation archived
BA actively engaged in evaluating effects of changes on agreed solution
www.mun.ca
Change-Driven Approach
Agile methods, Process Improvement• Rapid delivery• Risk• Solution exploratory, prototyping iterations• Formal sign-off events• Project owner ultimate approval authority
BA Activities: • High level requirements first
(envisioning, user story)• High priority requirements first
(backlog maintained)
Agile Example
www.mun.ca
Change –Driven Approach
Formality&Detail
Low
Requirements definition interaction, feedback
Formal documentation after implementation
Change Management informal• all requirements not identified up front
Project Lifecycle has many iterations• address prioritized requirements• backlog
Stakeholders Communications frequent• Informal communication over official docs
Documentation finalized after the Solution
www.mun.ca
BA Approach
Project Complexity
Organizational Requirements
BA WorkPlanning Process
Timing
Stakeholder Communication
Change Management
Deliverables: Formality, Detail
Requirements: Prioritization, Analysis, Management Tools
www.mun.ca
Elements of the BA Plan
BA Approach
Stakeholder Analysis
BA Activities
Communication
Requirements Management
BA Performance Management
www.mun.ca
Plan BA Approach
Techniques
Decision AnalysisUsed to rate available methodologies against the organizational need
Process ModelingMay be used to define and document the business analysis approach
Structured WalkthroughUsed to validate a proposed approach with stakeholders
Decision Analysis
Process Model for Business Analysis Approach
Iter
ativ
e P
roto
typ
ing
BIG
Ba
ng Develop Completesystems
requirements
Develop CompleteSystem
Specification
Develop CompleteTechnical
Specification
Develop CompleteSolution
Test CompleteSolution
ImplementComplete Solution
BrainstormInitial
Requirements
Develop aprototype for
review
Enhance InitialRequirements
Develop a refinedand agreed set of
Requirements
Develop CompleteRequirement
Iterate
When Done
Develop CompleteSystem
Specification
Develop CompleteTechnical
Specification
Develop CompleteSolution
Test CompleteSolution
ImplementComplete Solution
Plan Business Analysis ApproachProcess Modeling
www.mun.ca
Structured Walkthrough
Participants:
Author: request walkthrough
Presenter: present agenda, product
Moderator: facilitate walkthrough
Reviewers: evaluate product
Scribe: record
www.mun.ca
Last year
Last 5 years
Last 10 years
Your Projects
Plan-driven or change-driven
What worked well?
What could be better?
www.mun.ca
Pros &Cons Plan-driven
Change-driven
When to employ?Documentation RequiredAssociated RiskValue Delivery
www.mun.ca
BA APPROACHES
Discussion
www.mun.ca
Presenter Heather Rhodes
Business Analyst
Computing & Communications
Memorial University of Newfoundland and Labrador
www.mun.ca/cc