See these

Thursday, 8 April 2010

5.2 Define Scope

Planning, Scope Management

Developing detailed description of project and product. Builds upon the major deliverables, assumptions and constraints documented during project initiation. Analysis of existing risks, assumptions and constraints are done for completeness and additional risks, assumptions and constraints are added, if necessary.


Project Charter – See 4.1

Requirements Documentation – See


Tools and Techniques

Expert Judgment – May be available from following sources:

- Other Units within the organization.

- Consultants

- Stakeholders, including customer or sponsor.

- Professional and technical associations.

- Industry Groups and

- Subject Matter Experts.

Product Analysis – Can be an effective tool, where product is a deliverable rather than a service or result. Techniques such as product breakdown, system analysis, requirements analysis, systems engineering, value engineering and value analysis can be used for product analysis.

Alternatives Identification – Generating different approaches to execute and perform project work. Techniques such as brainstorming lateral thinking and pair wise comparison.

Facilitated Workshops


Project Scope Statement

- Product Scope Description

- Product acceptance criteria

- Project Deliverables – deliverables which comprise the product or service of the project as well as ancillary results, such as PM reports and documentation.

- Project Exclusions – helps in managing stakeholder expectations.

- Project Constraints – contractual provisions, may be listed in a separate log.

- Project Assumptions – impact when assumptions proved to be false.

Project Document Updates

- Stakeholder register

- Requirements documentation

- Requirements Traceability matrix

No comments:

Post a Comment

Thanks for stopping by and please go ahead and put your valuable suggestions.