Understand project scope management Flashcards
what does the term scope refer to project management
the totality of the outputs, outcomes and benefits and the work required to produce them
why are boundaries important for scope management
it is important to be clear of boundaries and interfaces with other projects to avoid duplication, conflict or omission of work
what is the product breakdown structure (PBS )
a hierarchical structure with the project output at the top level. the next level shows the components for the higher level. this is repeated to the level of individual products. this will include acceptance criteria and quality control methods
what interaction is there with stakeholders on the PBS
the PBS is used for scope verification to obtain agreement the product as as expected and what is in/out of scope
what is the work breakdown structure (WBS)
PM directs products to technical resource for detailed scope definition. this results in baseline scope of work as WBS detailing activities to be scheduled and resourced
why does the WBS have a coded reference
in order to be tracked within the BMS
what is the cost breakdown structure (CBS)
for each work package costs for people, equipment, materials or other resources are recorded using the WBS coding structure. this creates the CBS, a hierarchical breakdown of the project in cost elements
how does the WBS affect the project organisation
work packages in the WBS are reviewed and decisions are made who will be responsible for carrying out the work, supervisory activity and reporting. the OBS describes the project organisation that will carry out the WBS
what are a projects requirements
the stakeholders wants and needs with clearly defined acceptance criteria
what must requirements management ensure
- there’s a clear link between benefits, success criteria, project objectives and requirements
- requirements are clear and unambiguous
what is requirements management
process of capturing, assessing and justifying stakeholder wants and needs
how does requirements management help define scope
once requirements are agreed they become the project deliverables so the project team can structure the work to meet the requirements
what are the 4 steps of requirement management
- gather - interviewing stakeholders, surveys, focus groups
- analysis - gathered requirements must be tested for feasibility, validity, compatibility, acceptability, applicability and consistency.
- justifying requirements - assumptions from analysis are tested and fed back to stakeholders to build consensus
- baseline needs - product owner ensures requirements are relative to business needs giving acceptance criteria. This results in a baselined set of options.
What is the MoSCoW prioritisation technique
if more requirements are requested than can be delivered prioritisation exercise is needed to highlight most essential requirements to be baselined
(M) must have
(S) should have
(C) could have
(W) won’t have
in agile (C) and (S) would be sacrificed if running over budget or late delivering only the (M) in the form of most valuable product (MVP)
what is the project configuration
the PBS plus detailed descriptions of each product. Once baselined it is subject to version control
