BAM! Business Analysis Methodologies

Report
BAM!
Business Analysis Methodologies
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
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
ChangeDriven
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)
www.mun.ca
Agile Example
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 Work
Planning 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
Decision Analysis
Used to rate available methodologies
against the organizational need
Techniques
Process Modeling
May be used to define and document the
business analysis approach
Structured Walkthrough
Used to validate a proposed approach with
stakeholders
www.mun.ca
Decision Analysis
Plan Business Analysis Approach
Process Modeling
Iterative Prototyping
BIG Bang
Process Model for Business Analysis Approach
Develop Complete
systems
requirements
Brainstorm
Initial
Requirements
Develop Complete
System
Specification
Develop Complete
Technical
Specification
Develop a
prototype for
review
Develop Complete
Requirement
Iterate
Enhance Initial
Requirements
Develop a refined
and agreed set of
Requirements
Develop Complete
Solution
When Done
Test Complete
Solution
Develop Complete
System
Specification
Implement
Complete Solution
Develop Complete
Solution
Develop Complete
Technical
Specification
Implement
Complete Solution
Test Complete
Solution
Structured
Walkthrough
Participants:
Author:
request walkthrough
Presenter: present agenda, product
Moderator: facilitate walkthrough
Reviewers: evaluate product
Scribe:
record
www.mun.ca
Your
Projects
Last year
Last 5 years
Last 10 years
Plan-driven or change-driven
What worked well?
What could be better?
www.mun.ca
Pros
&
Cons
Plan-driven
When to employ?
Documentation Required
Associated Risk
Value Delivery
Change-driven
www.mun.ca
Discussion
www.mun.ca
Presenter
Heather Rhodes
Business Analyst
Computing & Communications
Memorial University of
Newfoundland and Labrador
[email protected]
www.mun.ca/cc
www.mun.ca

similar documents