Requirements/Scope Management - Part 5. Mapping RUP Requirements Management to PMBoK Scope Management

IBM RUP is a prescriptive approach for software engineering best practices.

PMI Guide to the PMBoK is a descriptive approach for project management best practices.

RUP focuses on PM best practices in the context of software development and deployment projects while the PMBOK best practices are generic and applicable to management of projects in any application domain. In the other words, RUP PM Discipline is a specific instance of the PMBOK's generic PM best practices.

Model mapping

Project type

PMBoK:

• Any project

RUP:

• Software development project

Lifecycle

PMBoK:

• Project divided into phases (usually 4-5, up to 9).
• Each phase produces predefined set of deliverables.
• End of phase defines milestone.
• Phase is reviewed by Phase Exits, Stage gates, Kill Points.

RUP:

• Project divided into 4 phases. Phases divided into iterations.
• Each iteration produces set of artifacts and executable version of software.
• End of phase defines major milestone.
• Phase is reviewed by Lifecycle Milestone Review.

Activities

PMBoK:

• Process described by set of inputs, tools/techniques and outputs.

RUP:

• Activity described by set of inputs, steps/tools/guidelines and outputs.

Activity grouping

PMBoK:

• Structural grouping - Knowledge Area
• Temporal grouping - Process Group

RUP:

• Structural grouping - Discipline
• Temporal grouping - Workflow

Mapping PMBoK Project Scope Management processes to RUP

Collect Requirements

• Project Management – Initiate Project
• Project Management – Initiate Iteration
• Project Management – Develop Business Case
• Requirements – Develop Vision

Define Scope

• Project Management – Develop Problem Resolution Plan
• Requirements – Develop Requirements Management Plan
• Configuration and Change Management – Write CM Plan
• Requirements – Develop Vision
• Requirements – Find Actors and Use Cases
• Requirements – Detail a Use Case
• Requirements – Detail the Software Requirements
• Requirements – Capture Common Vocabulary

Create WBS

• Project Management – Plan Phases and Iterations
• Project Management – Develop Iteration Plan
• Requirements – Develop Vision
• Requirements – Find Actors and Use Cases
• Requirements – Detail a Use Case
• Requirements – Detail the Software Requirements
• Requirements –Capture Common Vocabulary

Verify Scope

• Project Management – Lifecycle Milestone Review
• Requirements – Review Requirements

Control Scope

• Project Management – Report Status
• Project Management – Assess Iteration
• Project Management – Plan Phases and Iterations
• Project Management – Develop Iteration Plan
• Configuration and Change Management – Submit Change Request
• Configuration and Change Management – Update Change Request
• Requirements – Develop Vision
• Requirements – Find actors and Use Cases
• Requirements – Detail a Use Case
• Requirements – Detail the Software Requirements
• Requirements – Capture Common Vocabulary

Mapping PMBoK Project Scope Management artifacts to RUP

Collect Requirements

Project Charter:

• Project Management – Business Case
• Requirements – Vision

Project Manager Identified/Assigned:

• Project Management – Software Development Plan
• Project Management – Iteration Plan

Constraints:

• Project Management – Software Development Plan (Assumptions and Constrains)

Assumptions:

• Project Management – Software Development Plan (Assumptions and Constrains)

Define Scope

Scope Statement:

• Requirements – Vision
• Requirements – Software Requirements Specifications

Supporting Details:

• Requirements – Glossary

Scope Management Plan:

• Requirements – Project Management Plan
• Configuration and Change Management – Configuration Management Plan
• Project Management – Problem Resolution Plan

Create WBS

Work Breakdown Structure:

• Project Management – Software Development Plan (Project Plan)
• Project Management – Iteration Plan (Plan)

Scope Statement Updates:

• Requirements – Vision (updated)
• Requirements – Software Requirements Specifications (updated)

Verify Scope

Formal Acceptance:

• Review Record (result of Interception Lifecycle Objectives Milestone)

Control Scope

Scope Change:

• Configuration and Change Management – Change Request

Corrective Action:

• Project Management – Status Assessment
• Project Management – Iteration Assessment

Lessons Learned:

• Project Management – Status Assessment
• Project Management – Iteration Assessment

Adjusted Baseline:

• Project Management – Software Development Plan (new baseline)
• Project Management – Iteration Plan (new baseline)
• Requirements – Vision (new baseline)
• Requirements – Software Requirements Specifications (new baseline)

References

1. A Guide to the Project Management Body of Knowledge. http://en.wikipedia.org/wiki/A_Guide_to_the_Project_Management_Body_of_Knowledge
2. Project Management Institute. A Guide to the Project Management Body of Knowledge (2008)