1 / 19

BAM!

BAM! . Business Analysis Methodologies. Change-driven or Plan-driven?. Approaches include Waterfall development Agile techniques Lean/Six Sigma methods Standard / formal organizational methodologies. Plan BA Approach. Waterfall , Business Process Re-engineering

fausto
Download Presentation

BAM!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BAM! Business Analysis Methodologies

  2. Change-drivenorPlan-driven?

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

  4. 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 Approach

  5. BA TASKS

  6. 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 Plan-Driven Formality&Detail

  7. 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) Change-Driven Approach

  8. Agile Example

  9. 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 Change –Driven ApproachFormality&Detail

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

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

  12. 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 Plan BA ApproachTechniques

  13. Decision Analysis

  14. Plan Business Analysis ApproachProcess Modeling

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

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

  17. Plan-driven Change-driven Pros &Cons When to employ?Documentation RequiredAssociated RiskValue Delivery

  18. Discussion BA Approaches

  19. Heather Rhodes Business Analyst Computing & Communications Memorial University of Newfoundland and Labrador hrhodes@mun.ca www.mun.ca/cc Presenter

More Related