PRINCE II AND BUSINESS ANALYSIS BODY OF KNOWLEDGE (BABOK) Engagement Model
AGENDA <ul><li>Methodologies Unpacked </li></ul><ul><li>Methodology Integration </li></ul><ul><li>BABOK Deliverables </li>...
METHODOLOGIES UNPACKED
BABOK Guide V2 Business Analysis Planning and Monitoring . . ................................. Elicitation Requirements Ma...
<ul><li>Business Analysis Planning and Monitoring </li></ul><ul><ul><li>defines the resources and tasks associated with th...
<ul><li>Directing a Project </li></ul><ul><ul><li>Directing a Project runs from the start-up of the project until its clos...
<ul><li>Initiating a Project </li></ul><ul><ul><li>The summarised objectives of Initiating a Project are to: </li></ul></u...
<ul><li>Closing a Project </li></ul><ul><ul><li>The purpose of this process is to execute a controlled close to the projec...
METHODOLOGY INTEGRATION
BABOK integration with Prince II BABOK integration with Prince II Prince II Process Model Corporate or Program Management ...
BABOK integration with Prince II BABOK integration with Prince II Prince II Process Model Corporate or Program Management ...
BABOK integration with Prince II BABOK integration with Prince II Prince II Process Model Corporate or Program Management ...
BABOK integration with Prince II BABOK integration with Prince II Prince II Process Model Corporate or Program Management ...
BABOK integration with Prince II BABOK integration with Prince II Prince II Process Model Corporate or Program Management ...
BABOK integration with Prince II BABOK integration with Prince II Prince II Process Model Corporate or Program Management ...
BABOK DELIVERABLES
BABOK DELIVERABLES <ul><li>Business Analysis Planning and Monitoring </li></ul><ul><li>Elicitation </li></ul><ul><li>Enter...
ENGAGEMENT MODEL
ENGAGEMENT MODEL Business Analysis Approach – Engagement Model Engagement Model Business Analysis Planning Solution Assess...
ESTIMATED TIME FRAMES PID Analysis Reports 6 Weeks As-Is Status Reports 6 Weeks To-Be Status Reports Deployment Reports TB...
THANK-YOU
Upcoming SlideShare
Loading in...5
×

Prince I Iand Babok Ver1 0

1,228

Published on

Prince II and BABOK - and integrated Approach - with an Engagement Model

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

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

No notes for slide

Transcript of "Prince I Iand Babok Ver1 0"

  1. 1. PRINCE II AND BUSINESS ANALYSIS BODY OF KNOWLEDGE (BABOK) Engagement Model
  2. 2. AGENDA <ul><li>Methodologies Unpacked </li></ul><ul><li>Methodology Integration </li></ul><ul><li>BABOK Deliverables </li></ul><ul><li>Engagement Model </li></ul>
  3. 3. METHODOLOGIES UNPACKED
  4. 4. BABOK Guide V2 Business Analysis Planning and Monitoring . . ................................. Elicitation Requirements Management and Communications Enterprise Analysis ... Requirements Analysis Solution Assessment and Validation Prince II Process Model Corporate or Program Management Planning Directing a Project Starting up a Project Initiating a Project Controlling a Stage Closing a Project Managing Stage Boundaries Managing Product Delivery 1 2 3 4 5 6
  5. 5. <ul><li>Business Analysis Planning and Monitoring </li></ul><ul><ul><li>defines the resources and tasks associated with the planning and management of requirements gathering activities throughout the requirements process. </li></ul></ul><ul><li>Elicitation </li></ul><ul><ul><li>Serve’s as the foundation for the solution to the business needs it is essential that the requirements be complete, clear, correct, and consistent. Leveraging proven means to elicit requirements will help meet these quality goals. </li></ul></ul><ul><li>Enterprise Analysis </li></ul><ul><ul><li>This knowledge area is the collection of pre-project or early project activities and approaches for capturing the necessary view of the business to provide context to requirements and functional design work for a given initiative and/or for long term planning. </li></ul></ul><ul><li>Requirements Analysis </li></ul><ul><ul><li>Describes how stakeholder needs are analyzed, structured and specified for use in the design and implementation of a solution. The objective is to define and describe the characteristics of an acceptable solution to a business problem, so that the project team has a clear understanding of how to design and implement it. </li></ul></ul><ul><li>Solution Assessment and Validation </li></ul><ul><ul><li>covers the business analysis tasks necessary to ensure that the solution meets the stakeholder objectives, is thoroughly tested, and is implemented smoothly. </li></ul></ul><ul><li>Requirements Management and Communications </li></ul><ul><ul><li>Defines the resources and tasks associated with the planning and management of requirements gathering activities throughout the requirements process. Communications is the collection of activities and considerations for expressing the output of the requirements analysis and documentation to a broad and diverse audience. </li></ul></ul>BABOK Guide V2 Business Analysis Planning and Monitoring . . ................................. Elicitation Requirements Management and Communications Enterprise Analysis ... Requirements Analysis Solution Assessment and Validation 1 2 3 4 5 6
  6. 6. <ul><li>Directing a Project </li></ul><ul><ul><li>Directing a Project runs from the start-up of the project until its closure. This process is aimed at the Project Board. </li></ul></ul><ul><ul><li>The key processes for the Project Board break into four main areas: </li></ul></ul><ul><ul><ul><li>Initiation (starting the project off on the right foot) </li></ul></ul></ul><ul><ul><ul><li>Stage boundaries (commitment of more resources after checking results so far) </li></ul></ul></ul><ul><ul><ul><li>Ad hoc direction (monitoring progress, providing advice and guidance, reacting to exception situations) </li></ul></ul></ul><ul><ul><ul><li>Project closure (confirming the project outcome and controlled close). </li></ul></ul></ul><ul><li>Starting Up a Project </li></ul><ul><ul><li>It is a pre-project process, designed to ensure that the pre-requisites for initiating the project are in place. The process expects the existence of a Project Mandate which defines in high level terms the reason for the project and what outcome is sought. </li></ul></ul><ul><li>Managing Product Delivery </li></ul><ul><ul><li>The objective of this process is to ensure that planned products are created and delivered </li></ul></ul>Prince II Process Model Corporate or Program Management Planning Directing a Project Starting up a Project Initiating a Project Controlling a Stage Closing a Project Managing Stage Boundaries Managing Product Delivery
  7. 7. <ul><li>Initiating a Project </li></ul><ul><ul><li>The summarised objectives of Initiating a Project are to: </li></ul></ul><ul><ul><ul><li>Agree whether or not there is sufficient justification to proceed with the project </li></ul></ul></ul><ul><ul><ul><li>Establish a stable management basis on which to proceed </li></ul></ul></ul><ul><ul><ul><li>Document and confirm that an acceptable Business Case exists for the project </li></ul></ul></ul><ul><li>Managing Stage Boundaries </li></ul><ul><ul><li>The summarised objectives are : </li></ul></ul><ul><ul><ul><li>Provide the information needed for the Project Board to assess the continuing viability of the project </li></ul></ul></ul><ul><ul><ul><li>Record any measurements or lessons which can help later stages of this project and/or other projects. </li></ul></ul></ul><ul><li>Controlling a Stage </li></ul><ul><ul><li>This process describes the monitoring and control activities of the Project Manager involved in ensuring that a stage stays on course and reacts to unexpected events. </li></ul></ul>Prince II Process Model Corporate or Program Management Planning Directing a Project Starting up a Project Initiating a Project Controlling a Stage Closing a Project Managing Stage Boundaries Managing Product Delivery
  8. 8. <ul><li>Closing a Project </li></ul><ul><ul><li>The purpose of this process is to execute a controlled close to the project. </li></ul></ul><ul><ul><li>Most of the work is to prepare input to the Project Board to obtain its confirmation that the project may close. </li></ul></ul><ul><li>Planning </li></ul><ul><ul><li>Planning is a repeatable process, and plays an important role in other processes </li></ul></ul><ul><li>PRINCE2 provides a product-based start to the planning activity. </li></ul><ul><li>It also provides a planning framework which can be applied to any type of project. </li></ul><ul><li>This involves: </li></ul><ul><ul><li>Establishing what products are needed </li></ul></ul><ul><ul><li>Determining the sequence in which each product should be produced </li></ul></ul><ul><ul><li>Defining the form and content of each product </li></ul></ul><ul><ul><li>Resolving what activities are necessary for their creation and delivery. </li></ul></ul>Prince II Process Model Corporate or Program Management Planning Directing a Project Starting up a Project Initiating a Project Controlling a Stage Closing a Project Managing Stage Boundaries Managing Product Delivery
  9. 9. METHODOLOGY INTEGRATION
  10. 10. BABOK integration with Prince II BABOK integration with Prince II Prince II Process Model Corporate or Program Management Planning Directing a Project Starting up a Project Initiating a Project Controlling a Stage Closing a Project Managing Stage Boundaries Managing Product Delivery <ul><li>Business Analysis Planning and Monitoring </li></ul><ul><li>Plan Business Analysis Approach </li></ul><ul><li>Conduct Stakeholder Analysis </li></ul><ul><li>Plan BA Activities </li></ul><ul><li>Plan BA Communication </li></ul><ul><li>Plan Requirements Management Process </li></ul><ul><li>Manage BA Performance </li></ul>1 <ul><li>BA Planning and Monitoring Outputs </li></ul><ul><li>Business Analysis Approach </li></ul><ul><li>Stakeholder List, Roles and Responsibilities </li></ul><ul><li>Business Analysis Plan(s) </li></ul><ul><li>BA Communication Plan </li></ul><ul><li>Plan Requirements Management Process </li></ul><ul><li>BA Performance Assessment </li></ul><ul><li>Inputs </li></ul><ul><li>Business Need </li></ul>
  11. 11. BABOK integration with Prince II BABOK integration with Prince II Prince II Process Model Corporate or Program Management Planning Directing a Project Starting up a Project Initiating a Project Controlling a Stage Closing a Project Managing Stage Boundaries Managing Product Delivery <ul><li>Enterprise Analysis </li></ul><ul><li>Define Business Need </li></ul><ul><li>Assess Capability Gaps </li></ul><ul><li>Determine Solution Approach </li></ul><ul><li>Define Solution Scope </li></ul><ul><li>Define Business Case </li></ul><ul><li>Enterprise Analysis Outputs </li></ul><ul><li>Business Need </li></ul><ul><li>Business Case </li></ul><ul><li>Required Capabilities </li></ul><ul><li>Solution Approach </li></ul><ul><li>Solution Scope </li></ul>3 <ul><li>Inputs from Requirements Elicitation </li></ul><ul><li>Elicitation Results (Requirements) </li></ul><ul><li>Stakeholder Concerns </li></ul><ul><li>Inputs from Requirements Analysis </li></ul><ul><li>Assumptions and Constraints </li></ul><ul><li>Inputs from Solution Assessment & Validation </li></ul><ul><li>Solution Performance Assessment </li></ul>2 4 5
  12. 12. BABOK integration with Prince II BABOK integration with Prince II Prince II Process Model Corporate or Program Management Planning Directing a Project Starting up a Project Initiating a Project Controlling a Stage Closing a Project Managing Stage Boundaries Managing Product Delivery <ul><li>Requirements Elicitation </li></ul><ul><li>Prepare for Elicitation </li></ul><ul><li>Conduct Elicitation </li></ul><ul><li>Document Elicitation Results </li></ul><ul><li>Confirm Elicitation Results </li></ul>2 <ul><li>Requirements Elicitation Outputs </li></ul><ul><li>Elicitation Results </li></ul><ul><li>Stakeholder Concerns </li></ul><ul><li>Scheduled Resources </li></ul><ul><li>Supporting Materials </li></ul><ul><li>Inputs from Enterprise Analysis </li></ul><ul><li>Business Need </li></ul><ul><li>Business Case </li></ul><ul><li>Solution Scope </li></ul><ul><li>Inputs from BA Planning and Monitoring </li></ul><ul><li>Stakeholder List, Roles and Responsibility </li></ul><ul><li>Requirements Management Plan </li></ul>1 3
  13. 13. BABOK integration with Prince II BABOK integration with Prince II Prince II Process Model Corporate or Program Management Planning Directing a Project Starting up a Project Initiating a Project Controlling a Stage Closing a Project Managing Stage Boundaries Managing Product Delivery <ul><li>Requirements Management & Communication Outputs </li></ul><ul><li>Approved Requirements </li></ul><ul><li>Requirements Traceability </li></ul><ul><li>Requirements Maintained and Re-Usable </li></ul><ul><li>Requirements Package </li></ul><ul><li>Requirements Communication </li></ul><ul><li>Requirements Management & Communication </li></ul><ul><li>Manage Solution Scope and Requirements </li></ul><ul><li>Manage Requirements Traceability </li></ul><ul><li>Maintain Requirements for Re-Use </li></ul><ul><li>Prepare Requirements Packages </li></ul><ul><li>Communicate Requirements </li></ul>6 <ul><li>Inputs from Requirements Analysis </li></ul><ul><li>Requirement Structure </li></ul><ul><li>Inputs from BA Planning and Monitoring </li></ul><ul><li>Stakeholder List, Roles and Responsibility </li></ul><ul><li>Requirements Management Plan </li></ul><ul><li>BA Communications Plan </li></ul><ul><li>Inputs from Enterprise Analysis </li></ul><ul><li>Solution Scope </li></ul>1 4 3
  14. 14. BABOK integration with Prince II BABOK integration with Prince II Prince II Process Model Corporate or Program Management Planning Directing a Project Starting up a Project Initiating a Project Controlling a Stage Closing a Project Managing Stage Boundaries Managing Product Delivery <ul><li>Inputs from BA Planning and Monitoring </li></ul><ul><li>Stakeholder List, Roles and Responsibility </li></ul><ul><li>Requirements Management Plan </li></ul><ul><li>BA Communications Plan </li></ul><ul><li>Inputs from Enterprise Analysis </li></ul><ul><li>Solution Scope </li></ul>1 3 <ul><li>Requirements Analysis </li></ul><ul><li>Prioritise Requirements </li></ul><ul><li>Organise Requirements </li></ul><ul><li>Specify and Model Requirements </li></ul><ul><li>Define Assumptions and Constraints </li></ul><ul><li>Verify Requirements </li></ul><ul><li>Validate Requirements </li></ul>4 <ul><li>Requirements Analysis Outputs </li></ul><ul><li>Prioritise Requirements </li></ul><ul><li>Requirements Structure </li></ul><ul><li>Stakeholder Requirements </li></ul><ul><li>Solution Requirements </li></ul><ul><li>Assumptions and Constraints </li></ul><ul><li>Verified Requirements </li></ul><ul><li>Validate Requirements </li></ul>
  15. 15. BABOK integration with Prince II BABOK integration with Prince II Prince II Process Model Corporate or Program Management Planning Directing a Project Starting up a Project Initiating a Project Controlling a Stage Closing a Project Managing Stage Boundaries Managing Product Delivery <ul><li>Solution Assessment and Validation </li></ul><ul><li>Assess Proposed Solution </li></ul><ul><li>Allocate Requirements </li></ul><ul><li>Assess Organisations Readiness </li></ul><ul><li>Validate Solutions </li></ul><ul><li>Evaluate Solution Performance </li></ul>5 <ul><li>Solution Assessment and Validation Outputs </li></ul><ul><li>Assessment of Proposed Solution </li></ul><ul><li>Allocated Requirements </li></ul><ul><li>Organisational Readiness Assessment </li></ul><ul><li>Transition Requirements </li></ul><ul><li>Identified Defects </li></ul><ul><li>Mitigating Actions </li></ul><ul><li>Solution Validation Assessment </li></ul><ul><li>Solution Performance Assessment </li></ul><ul><li>Inputs from Requirements Elicitation </li></ul><ul><li>Stakeholder Concerns </li></ul><ul><li>Inputs from Enterprise Analysis </li></ul><ul><li>Solution Scope </li></ul><ul><li>Inputs from Requirements Analysis </li></ul><ul><li>Prioritised Requirements </li></ul><ul><li>Assumptions and Constraints </li></ul><ul><li>Inputs from Requirements Management & Communication </li></ul><ul><li>Approved Requirements </li></ul>4 6 3 2
  16. 16. BABOK DELIVERABLES
  17. 17. BABOK DELIVERABLES <ul><li>Business Analysis Planning and Monitoring </li></ul><ul><li>Elicitation </li></ul><ul><li>Enterprise Analysis </li></ul><ul><li>Requirements Analysis </li></ul><ul><li>Solution Assessment and Validation </li></ul><ul><li>Requirements Management and Communication </li></ul><ul><li>Business Analysis Approach </li></ul><ul><li>Elicitation Results </li></ul><ul><li>Business Need </li></ul><ul><li>Prioritise Requirements </li></ul><ul><li>Assessment of Proposed Solution </li></ul><ul><li>Approved Requirements </li></ul><ul><li>Stakeholder List, Roles and Responsibilities </li></ul><ul><li>Stakeholder Concerns </li></ul><ul><li>Business Case </li></ul><ul><li>Requirements Structure </li></ul><ul><li>Allocated Requirements </li></ul><ul><li>Requirements Traceability </li></ul><ul><li>Business Analysis Plan(s) </li></ul><ul><li>Scheduled Resources </li></ul><ul><li>Required Capabilities </li></ul><ul><li>Stakeholder Requirements </li></ul><ul><li>Organisational Readiness Assessment </li></ul><ul><li>Requirements Maintained and Re-Usable </li></ul><ul><li>BA Communication Plan </li></ul><ul><li>Supporting Materials </li></ul><ul><li>Solution Approach </li></ul><ul><li>Solution Requirements </li></ul><ul><li>Transition Requirements </li></ul><ul><li>Requirements Package </li></ul><ul><li>Plan Requirements Management Process </li></ul><ul><li>Solution Scope </li></ul><ul><li>Assumptions and Constraints </li></ul><ul><li>Identified Defects </li></ul><ul><li>Requirements Communication </li></ul><ul><li>BA Performance Assessment </li></ul><ul><li>Verified Requirements </li></ul><ul><li>Mitigating Actions </li></ul><ul><li>Validate Requirements </li></ul><ul><li>Solution Validation Assessment </li></ul><ul><li>Solution Performance Assessment </li></ul>
  18. 18. ENGAGEMENT MODEL
  19. 19. ENGAGEMENT MODEL Business Analysis Approach – Engagement Model Engagement Model Business Analysis Planning Solution Assessment and Validation Validate and Verify Requirements Develop Proposed Solution Organisational Readiness Assessment Assessment of Proposed Solution Conclusion and Closure Development of RFP Acceptance of RFP To-Be Consolidation To-Be Business Processes Develop To-Be Use Cases To-Be Business Models Interview Subject Matter Experts Joint Application Design (JAD) Review Current Systems Document Analysis Focus Groups Feasibility Study for EIP Elicitation (As-Is Status) Business Model Development Use Case Development Consolidate Business Processes Business Architecture Artifacts Solution Performance Assessment
  20. 20. ESTIMATED TIME FRAMES PID Analysis Reports 6 Weeks As-Is Status Reports 6 Weeks To-Be Status Reports Deployment Reports TBO 6 Weeks 6 Weeks Assessment Status Reports Business Analysis Planning Change Management, Monitor and Control Incentive Document Analysis Interview Subject Matter Experts Joint Application Design Review Current Systems Focus Groups Elicitation (As-Is State) Business Model Development Consolidate Business Processes Use Case Development Business Architecture Artifacts To-Be- Consolidation Feasibility Study for EIP Develop To-Be Use Cases To-Be Business Processes To-Be Business Models Solution Assessment Validation Conclusion and Closure Validate and Verify Requirements Develop Proposed Solution Assessment of Proposed Solution Organisational Readiness Assessment Solution Performance Assessment Development of RFP Acceptance of RFP
  21. 21. THANK-YOU
  1. A particular slide catching your eye?

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

×