Understand Project Scope Management Flashcards
Explain how to define scope in terms of outputs, outcomes and benefits - SCOPE
Scope comprises the totality of the outputs, outcomes and benefits and the work required to produce them
Definitions - Output
- The tangible or intangible product typically delivered by a project
- Also called Project Product/ Deliverable/ Configuration
Definitions - Outcome
- The changed circumstances or behaviour that results from the use of an output and leads to realisation of benefits
Definitions - Benefit
- The quantifiable and measurable improvement resulting from completion of deliverables that is perceived as positive by a stakeholder
Product Breakdown Structure (PBS)
- A hierarchical decomposition of a project into products and products into component products
- A graphic diagram that helps clarify scope
- Forms an input to the constriction of a Work Breakdown Structure
- Each product/ component product identified needs a set of acceptance criteria
Work Breakdown Structure (WBS)
- useful tool for effective cost control and enables project costs to be controlled at appropriate levels, providing visibility and enhanced understanding
- Each work package in the WBS will have costs associated with labour, materials, expenses and possibly other cost categories as indicated above
- A hierarchal decomposition of the project into tasks (activities)
- Sets of related tasks/ activities can form Work Packages
- WBS is an activity based decomposition of the work to be carried out
- Dividing the scope of the project into manageable pieces of work is a fundamental aspect of effective project planning and hence project management
- Increases the level of understanding within the project team
Explain How to Establish Scope Through Requirements Management Processes
The process of capturing, assessing and justifying stakeholders’ wants and needs
Importance of Good Requirements Management - SCOPE
- The requirements form the basis of the project’s scope … i.e. what is actually going to be delivered and the work required to deliver the product
- Having a good understanding of the business need will help define the most appropriate requirements as early as possible in the project life cycle
Importance of Good Requirements Management - QUALITY
- Without this understanding, the quality of each deliverable may be significantly undermined
Importance of Good Requirements Management -CHANGE CONTROL
- Changes to the project scope with also have an obvious impact on the project requirements and part of the impact analysis should determine what effect any change has on the projects’ requirements, feature set and ultimately its ability to satisfy the stated business need
Requirements Management Solves Requirements Problems
- Duplication
- Conflicting
- Are difficult to test
- They assume solutions
- User uncertainty
- Omissions
Requirements Management Steps - GATHER
- Capturing, documenting, and structuring the requirements (and also its associated acceptance criteria)
Requirements Management Steps - ANALYSIS
- Analyse to look for overlaps, gaps and conflicts and prioritise requirements based on their ability to realise benefits whilst taking the project context into account (business priorities, availability of resources, available budget etc)
- Record in functional specification
- May include a requirements catalogue
- Particular attention to:
> duplicated and overlapping requirements
> conflicting requirements
Characteristics of Good Requirement
SMART
Specific Measurable Achievable Relevant Time-bound
Requirements should be …
- Balancing functional and project authority of projects
- Project manager’s authority is accepted at project level
- Functional departments deliver to agreed standards
- Project managers do not supervise how jobs are done
