• All work involved in creating the product(s) of the project
• The processes used to create it/them

• any product produced as part of a project
• examples: hardware, software, planning documents, meeting minutes, etc.

• PLANNING

• ---

• Scope management planning
• How will each scope management process be completed

• ---

• DOING

• ---

• Requirements collection
• documents for the processes required
• Scope definition
• based initially on project charter
• Work breakdown Structure (WBS) development
  
• subdividing/decomposing major project deliverables into smaller, more manageable components
• Scope verification
• formalizing acceptance of the delivered project scope

• ---

• Monitoring and Controlling

• ---

• scope control
• controlling changes to the project scope

• Project charter, stakeholder register
• other project management plan elements
• organizational process assets... methods, tools, templates, etc.
• Enterprise enviornmental factors... internal/external

Collecting requirements...

• More complex projects may suggest "phasing" collection activities... for control and effectiveness
• Elicitation, analysis, specification, validation
• Complexity, impact, and stakeholder expectations can also drive level of detail and effort required

• Documentation review
• Interviews
• Focus groups and facilitated workshops
• Group activity and decision-making techniques
• Questionnaries and suveys
• Observation
• Prototyping
• Software tools

Documenting requirements...

Ways of documenting

• Can be documented in a variety of ways and media:
• Text, diagrams, videos, etc.
• Can be categorized... technical, functional/operational, service (reliability and maintainability), training, etc.

Documenting Requirements...

Degree and methods of documentation

• Will vary with organization and project
• requirements and management plan... the "what" and "how" is part of scope planning and overall project plan
• May require legal department review in some cases

Documenting requirements...

Requirements traceability matrix

• Tool to track requirements from origin to scope/WBS deliverable to test to acceptance

Project scope statement...

Key inputs

• Project charter
• Requirements documentation
• Organizational process assets relating to scope
• (Polices, procedures, templates)
• (Applicable lessons learned, organization knowledge base)
• Approved change requests
• Over time, project scope should become clearer and more specific, but not larger ( no scope-creep)

Project Scope statement...

Over time project scope should...

Work Breakdown Structure

(WBS)

• Is a deliverable orientated grouping of the work invovled in a project
• defines the total scope of the project
• forms foundation of documentation, which... provides the basis for planning project schedules, costs, resources, and changes
• The process of subdividing project deliverables into small elements is called decomposition
• WBS can be broken down by function or phase

WBS Development approaches...

• Guidelines
• Some organizations, such as the Dept of Defense (DoD) provide guidelines for preparing WBSs
• Analogy approach
  
• Review WBSs of similar projects and tailor to your project
• The "been there, done that" approach
• Top-Down approach
• Start with the largest items of the project and break them down
• Bottom-up approach
• Start with specific tasks and roll them up
• Mind-Mapping apporoach
  
• Write tasks in a non-linear, branching format
• create the WBS structure from that "map"

• WBS tasks are planning aids, often vague
• May require explanation/detail to aid in...
• Knowing what to do and how to do it
• Estimating how long the work will take (schedule) and what it will cost to do it (budget
• The WBS dictionary provides detailed information about each WBS item
• Scope baseline:
• includes approved project scope statement, associated WBS and WBS dictionary, and is used to measure performance in meeting project scope goals

• A unit of work should appear in only one place in the WBS
• The works content of a summary WBS item is the sum of the WBS items below it
• A WBS item should be the responsibility of only one individual, even though many people may be working on it
• The WBS must be consistent with the way in which work is actually going to be performed
• It should serve the project team first, and other purposes only if practical 
• Project team members should be involved in developing the WBS to ensure consistency and buy-in
• (May provide a "sanity check")
• Each WBS item must be documented in a WBS dictionary ... What is really in.. and not in... that item
• The WBS must be a flexible tool... Change happens... Work content must change to support the scope statement 

• Verification involves customer inspection/sign off on deliverables 
• - Planning for verification must include agreements on tests, protocols, acceptance metrics, etc.
• - actual verification applies the specified tests and standards to project deliverables 
• •Verification inputs
  –Scope statement/scope management plan
  –WBS dictionary
  –Deliverables
  •For verification processes to  be effective, plans must ensure
  –Clear, unambiguous scope/requirement definitions
  –Clear, understandable documentation of work performed and deliverables produced
  –Clear, unambiguous verification and acceptance processes, procedures, protocols, etc. and …
  –Equally clear, unambiguous acceptance metrics

• Develop a good project selection process and insist on organization
• Place users into important roles
• Hold regular meetings with defined agendas
• Have deliverables on a regular basis
• Co locate users with developers