BAM! Business Analysis Methodologies

Change-driven or Plan-driven?

Plan BA Approach Approaches include Waterfall development Agile techniques Lean/Six Sigma methods Standard / formal organizational methodologies

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

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

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

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

BA Approach Project Complexity Organizational Requirements BA Work Planning Process Timing Stakeholder Communication Change Management Deliverables: Formality, Detail Requirements:Prioritization, Analysis, Management Tools

Elements of the BA Plan BA Approach Stakeholder Analysis BA Activities Communication Requirements Management BA Performance Management

Plan BA Approach Techniques Decision Analysis Used to rate available methodologies against the organizational need Process Modeling May be used to define and document the business analysis approach Structured Walkthrough Used to validate a proposed approach with stakeholders

Decision Analysis

Plan Business Analysis Approach Process Modeling

Structured Walkthrough Participants: Author: request walkthrough Presenter: present agenda, product Moderator: facilitate walkthrough Reviewers: evaluate product Scribe: record

Last year Last 5 years Last 10 years Your Projects Plan-driven or change-driven What worked well? What could be better?

Pros & Cons Plan-driven Change-driven When to employ? Documentation Required Associated Risk Value Delivery

BA APPROACHES Discussion

Presenter Heather Rhodes Business Analyst Computing & Communications Memorial University of Newfoundland and Labrador