We are called to serve!!
Proventures Education and Consulting ServicesProventures Education and Consulting ServicesProventures Education and Consulting Services
(Mon - Saturday)
trainings@proventuresindia.com
Hyderabad 500019
Proventures Education and Consulting ServicesProventures Education and Consulting ServicesProventures Education and Consulting Services

PROJECT SCOPE MANAGEMENT – PMBOK SIXTH EDITION

Project Management Body of Knowledge

Introduction

Project Scope Management did not go through any major changes in terms of processes, names correction etc. However, the changes in the lifecycle approach are aligned to scope management and the general changes to tools and techniques affected this knowledge area. This week we will look in to these updates

Key concepts for Project Scope Management

In this section how project scope is dealt with in Predictive and Agile projects is compared extensively. Below table is a short snapshot of the same

CONCEPT

PREDICTIVE LIFECYCLE

ADAPTIVE / AGILE LIFECYCLE

Project deliverables

Defined in the beginning of the project and changes are managed through progressive elaboration and change control

Deliverables are developed over multiple iterations. In each iteration the detaled scope is defined and approved at the beginning of the iteration.

Requirements

Collect requirements, Define scope and create WBS processes are performed in the beginning and updated as needed through intergrated change control

Requirements are termed as product backlog and the three proceeses (Collect requirements, Define scope and create WBS) are performed in each iteration. Prioritized requirements are delivered within each iteration

Scope baseline

Project Scope statement, WBS and WBS dictionary form part of scope baseline. This is compared with the deliverables during verfication ( Control Quality ) and validation ( Validate Scope )

Product backlog is used in place of Scope baseline

Evolving Trends and Emerging Practices in Scope Management includes but not limited to

  • Requirements Management is an emerging area in Project Management. PMI published a Practice Guide on this topic. This is highlighted in the sixth edition
  • The roles with responsibilities of business analysis should be part of Project Management plan and it is recommended to assign a business analyst to every project
  • Project Manager and Business analyst should work in collaboration partnership mode

Tailoring considerations

Because each project is unique, the project manager may need to tailor the way that the project scope management processes are applied. Consideration for tailoring include but not limited to

  • Knowledge management and requirements management systems
  • Validation and Control
  • Development Approach
  • Stability of requirements
  • Governance

The following sections briefly explains the changes to the processes

Plan Scope Management

Quality Management plan is brought in as an input to align scope with organization quality policy, methodologies and standards

Project Lifecycle and Development approach will significantly influence scope. So they are brought in as additional inputs

Different alternatives should evaluated to perform scope management activities and hence alternative analysis is used as a technique

INPUT

TOOLS & TECHNIQUES

OUTPUT

Project charter

Expert judgment

Scope management plan

Project management plan
1. Quality management plan
2. Project life cycle description
3. Development approach

Data analysis
1. Alternatives analysis

Requirements management plan

EEF & OPA

Meetings

Collect Requirements

More inputs are brought in to this process. In order to make sure the customer requirements are captured, Agreements are brought in as input. To make sure the business requirements are included, the business case is added

In the tools and techniques, focus groups and facilitated workshops are merged as Facilitation techniques. This JAD, QFD and User stories

Context diagram is explained with picture and examples

Interpersonal skills include observation and conversation as a new addition

Decision making tool includes voting

INPUT

TOOLS & TECHNIQUES

OUTPUT

Project charter

Expert judgment

Requirements documentation

Project management plan
1. Scope management plan
2. Requirements management plan
3. Stakeholder engagement plan

Data gathering
1. Brainstorming
2. Interviews
3. Focus groups
4. Questionnaires and surveys
5. Benchmarking

Requirements traceability matrix

Project documents
1. Assumption log
2. Lessons learned register
3. Stakeholder register

Data analysis
1. Document analysis

Business documents
1. Business case

Decision making
1. Voting
2. Multi criteria decision analysis

Agreements 

Data representation
1. Affinity diagrams
2. Mind mapping

EEF & OPA

Interpersonal and team skills
1. Nominal group technique
2. Observation/ Conversation
3. Facilitation

Context diagram

Prototypes

Define Scope

Overall structure remains same. But there are few changes in inputs and tools and techniques

Risk register is added as additional input to update the Project scope statement in alignment with risk response actions.

INPUT

TOOLS & TECHNIQUES

OUTPUT

Project charter

Expert judgment

Project scope statement

Project management plan
1. Scope management plan

Data analysis
1. Alternatives analysis

Project documents updates
1. Assumption log
2. Requirements documentation
3. Requirements traceability matrix
4. Stakeholder register

Project documents
1. Assumption log
2. Requirements
documentation
3. Risk register

Decision making
1. Multi criteria decision analysis

EEF & OPA

Interpersonal and team skills
1. Facilitation

Product analysis

Create WBS

Minor changes to this process.

The list of scope baseline components includes work package and planning package

  • Project Scope Statement
  • WBS
  • Work package
  • Planning package
  • WBS Dictionary

To WBS dictionary few additional items like agreement information added

Validate Scope

  • Quality report and lessons learned register added as additional inputs
  • Voting is added to T&T list
  • Lessons learned document gets updated with new lessons learned of this process

INPUT

TOOLS & TECHNIQUES

OUTPUT

Project management plan
1. Scope management plan
2. Requirements management plan
3. Scope baseline

Inspection

Accepted deliverables

Project documents
1. Lessons learned register
2. Quality reports
3. Requirements documentation
4. Requirements traceability matrix

Decision making
1. Voting

Work performance information

Verified deliverables

Change requests

Work performance data

Project document update
1. Lessons learned register
2. Requirements documentation
3. Requirements traceability matrix

Control Scope

Following minor changes are done to this process

  • Lessons learned register added as inputs and output
  • Trend analysis is added to T&T list this helps to analyse the trend of scope performance over time and decide whether it is improving or deteriorating
  • In the Outputs section, along with the three baselines performance Measurement Baseline is added as additional baseline Overall the integration Management is one of the area significantly affected as part of this revision.

Overall changes to this chapter is minimal. Those who have a good understanding of fifth edition can adapt to this chapter very easily

Our Upcoming Workshops

PMP | PMI-ACP | MSP | Primavera P6 | PgMP | PfMP

No products in the cart.