Business Analysis Methodology       and Framework                        David Peters                        Principal Con...
Discussion Points• What is a Framework• What is a Methodology• Methodology Components (UMA)• Business Analysis Framework• ...
What is a Framework?• A Partially completed solution                  Various degrees                  of completion• Vari...
What is a Methodology?It Describes:    Unified Methodology Architecture:            Who              Role       (UMA)     ...
Relationships                                          Steps             Role                  TaskPrimary                ...
Practices and DisciplinesTasks (and their associated Roles and Work Products)can be grouped into:• Practices      and• Dis...
Practices and Disciplines (contd.)• Practices   – A practice is an approach to solving one or several     commonly occurri...
Business Analysis FrameworkDomain Scope                      Why                                     Value           Busin...
Practices and Disciplines Matrix                                          Why (Objective) Practice BA          Business   ...
Practices and Disciplines Matrix                                                         Why (Objective)                  ...
Practices and Disciplines Matrix                                                         Why (Objective)                  ...
Practices and Disciplines Matrix                                   Why (Objective)What (Focus)                            ...
Workflow           Click on Activity to drill             down to Role-Task-                Work Product                  ...
Workflow Detail                  15
Does one Methodology fit all?• Varying Factors?                                   16
Varying Competency Levels                                                     Supervision                     Knowledge   ...
Many Techniques Very                        Data RequirementsDetailed                (entities, Attributes                ...
Diverse JargonProblem Scope                           Domain Scope                                                        ...
Standards - Flexibility Dichotomy                          Two Approaches To Documenting Requirements   Few Fixed Template...
Does one Methodology fit all?• No, because of:  – Project Complexity  – Project Type  – Project Size  – Stakeholders  – Sk...
Eclipse Process Framework Composer                                 22
IBM Rational Method Composer                               23
Publish It             24
Let’s Look and Play                      25
Conclusions• We need to Plan• We need a Methodology• It must be easily accessible• It must be easy to use  – Novices and E...
Any Questions?The IndigoCube Business Analysis Practice iscommitted to assisting clients to performBusiness Analysis bette...
28
Methodology framework
Upcoming SlideShare
Loading in...5
×

Methodology framework

1,213

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,213
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
48
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Methodology framework

  1. 1. Business Analysis Methodology and Framework David Peters Principal Consultant 2
  2. 2. Discussion Points• What is a Framework• What is a Methodology• Methodology Components (UMA)• Business Analysis Framework• Customisation• Availability• Look and Play 3
  3. 3. What is a Framework?• A Partially completed solution Various degrees of completion• Various options to complete 4
  4. 4. What is a Methodology?It Describes: Unified Methodology Architecture: Who Role (UMA) does What Task with What input Work Productto produce What output Work Product When Process How Guidance Why Outcome 5
  5. 5. Relationships Steps Role TaskPrimary PerformsandAdditional Input GuidanceSkill SetCompetency Level Output Checklists Concepts Guidelines Templates Examples Work Product Term Definitions Artifacts, Outcomes and Deliverables etc. 6
  6. 6. Practices and DisciplinesTasks (and their associated Roles and Work Products)can be grouped into:• Practices and• DisciplinesEither or both can be used to organise tasks 7
  7. 7. Practices and Disciplines (contd.)• Practices – A practice is an approach to solving one or several commonly occurring problems. Practices are intended as "chunks" of methodology for adoption, enablement, and configuration. (Vertical Slices) See Practices and Disciplines Matrix• Disciplines – A Discipline is a categorization of Tasks based upon similarity of concerns and cooperation of work effort. (Horizontal Slices) 8
  8. 8. Business Analysis FrameworkDomain Scope Why Value Business ObjectivesSolution Scope What Entities Processes Business Requirements Traceability Business Rules (high level) Logical Data Functionality Functional what Model and Workflow How Requirements Technology PlatformSystem Scope Interfaces Non-Functional how Requirements (detail) Physical Data Model System Specification Technical (technical) Requirements DDL Code Product Data Base Application Transitional Requirements Data Process 9
  9. 9. Practices and Disciplines Matrix Why (Objective) Practice BA Business Business Functional Non-Functional Transitional Solution Planning Case Requirements Requirements Requirements Requirements Validation How (Tasks, Techniques) Outcome Deliverable Outcomes and Deliverables(Scope BA Work) (Work Plan) 10
  10. 10. Practices and Disciplines Matrix Why (Objective) Practice BA Business Business Functional Non-Functional Transitional Solution Discipline Planning Case Requirements Requirements Requirements Requirements Validation Planning & Monitoring ElicitationWhat (Focus) Analysis How (Tasks, Techniques) Management & Communication Validation & Verification Outcome (Scope BA Work) Deliverable Outcomes and Deliverables (Work Plan) 11
  11. 11. Practices and Disciplines Matrix Why (Objective) Practice BA Business Business Functional Non-Functional Transitional Solution Discipline Planning Case Requirements Requirements Requirements Requirements Validation Planning & Monitoring Prepare Elicitation Elicit Pyramid EvaluateWhat (Focus) Plan Analysis Analyse Do How Management & What produced Communication Document produced Validation & Verification Review Outcome (Scope BA Work) Deliverable Outcomes and Deliverables (Work Plan) 12
  12. 12. Practices and Disciplines Matrix Why (Objective)What (Focus) When ? Outcome Deliverable 13
  13. 13. Workflow Click on Activity to drill down to Role-Task- Work Product 14
  14. 14. Workflow Detail 15
  15. 15. Does one Methodology fit all?• Varying Factors? 16
  16. 16. Varying Competency Levels Supervision Knowledge Experience Complexity Scope• Entry Level Some but Narrow Little to none Needs constant Little understanding Narrow Deep in Some but Minimal Broadening Deepening• Junior Some areas narrow Broadening Deep in many Wide Provides Good Wide• Intermediate areas understanding Wide and Vast Leads Creative Vast• Senior deep 17
  17. 17. Many Techniques Very Data RequirementsDetailed (entities, Attributes Database Design Relationships) System Use case Description Essential Process Description Business Use case Screen Prototype Description Glossary Screen Storyboard Process Maps Workflow Diagram Workflow Diagram Business Use case Decomposition Description Workflow Diagram Diagram System Use case Description Context Level DFD Diagram Workflow Diagram Use Case Diagram User Story High Level Business Functional Requirements Requirements 18
  18. 18. Diverse JargonProblem Scope Domain Scope BAUS (Business Area Business Initiative Under Study) Value Project Scope Solution Scope System Scope BUA (Business Area Entities Processes Traceability Product Scope under Analysis) Business Rules Logical Data Functionality SUD (System Project Scope Model and Workflow under Design) Technology PlatformSystem Scope Design Scope Interfaces System Scope Physical Data Model System Specification Software Scope DDL Code Product Solution Data Base Application Data Process 19
  19. 19. Standards - Flexibility Dichotomy Two Approaches To Documenting Requirements Few Fixed Templates Many Suitable Templates VS Flexibly Packaged Appropriately“Boxed” Sent down the delivered “Conveyor” Cannot Change Methodology Can Change (Wisdom) 20
  20. 20. Does one Methodology fit all?• No, because of: – Project Complexity – Project Type – Project Size – Stakeholders – Skill Sets – And more So, we need to be able to Customise 21
  21. 21. Eclipse Process Framework Composer 22
  22. 22. IBM Rational Method Composer 23
  23. 23. Publish It 24
  24. 24. Let’s Look and Play 25
  25. 25. Conclusions• We need to Plan• We need a Methodology• It must be easily accessible• It must be easy to use – Novices and Experts• It must be customisable 26
  26. 26. Any Questions?The IndigoCube Business Analysis Practice iscommitted to assisting clients to performBusiness Analysis better through solutions in ‒ Business Analyst Assessments ‒ Methodology Provisioning Creation Customisation Implementation ‒ Skills Development 27
  27. 27. 28
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×