Understand Project Scope Management

Question 1

2.2.6

Answer 1

2.2.6

Question 2

Explain the way in which an organisational breakdown structure is used to create a responsibility assignment matrix

Answer 2

OBS = hierarchy structure of a project 
OBS = valuable for communicating the reporting structure for the projects to all stakeholders 

WBS assigned to OBS a RAM can be created.
RAM will be used to communicate to those who have been assigned work and also to communicate to their like managers that one or more of their people have been assigned work

Question 3

Explain how to define scope in terms of output, outcomes and benefits (product, cost and WBS)

Answer 3

Structured approach to scope definition is necessary - early stages the pm and team have most influence over the project and where change is most manageable.

If the project team can’t get scope defined and agreed at this stage = longer the project continues, higher costs to change, less chance there will deliver a satisfactory outcome to stakeholders

Governance check = nothing overlooked

Question 4

Explain how to establish scope through requirement management processes ( gather, analysis,justify requirements, baseline needs)

Answer 4

Linear: value at the end when the project is delivered
Agile methodology: attempt to draw value out of a iterative life cycle and various points during overall project delivery

Measure the interm value

MOSCOW prioritisation technique = decision making planned in the lifecycle

Question 5

Explain how to manage scope through configuration management processes (planning, identification, control, status accounting,and verification audit)

Answer 5

Configuration management = version control

Change in design without following it through and understanding the impact on the project = cost impact

Question 6

Explain the different stages of a typical change control process ( request, initial evaluation, detailed evaluation, recommendation, updated plans and implement)

Answer 6

Project members must follow the process for it to be successful and manage correctly

Note the relationship between change control and configuration management

Change control relies on receiving the most current information to allow the best decision to be made. When the change is implemented, those who made the decision must update all configuration items affected are updated and new versions created (sealing old records)