Page 148 -

5 - PROJECT SCOPE MANAGEMENT

5.3.1.4 organizational Process Assets

Described in Section 2.1.4. Organizational process assets can influence how scope is defined. Examples include,
but are not limited to:

• Policies, procedures, and templates for a project scope statement;
• Project files from previous projects; and

• Lessons learned from previous phases or projects.

5.3.2 define Scope: tools and techniques

5.3.2.1 Expert Judgment

Expert judgment is often used to analyze the information needed to develop the project scope statement. Such
judgment and expertise is applied to any technical detail. Such expertise is provided by any group or individual with
specialized knowledge or training, and is available from many sources, including but not limited to:
• Other units within the organization;

• Consultants;
• Stakeholders, including customers or sponsors;

• Professional and technical associations;
• Industry groups; and
• Subject matter experts.

5.3.2.2 Product Analysis

For projects that have a product as a deliverable, as opposed to a service or result, product analysis can be an
effective tool. Each application area has one or more generally accepted methods for translating high-level product
descriptions into tangible deliverables. Product analysis includes techniques such as product breakdown, systems
analysis, requirements analysis, systems engineering, value engineering, and value analysis.

122 ©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Fifth Edition
®

Licensed To: Jorge Diego Fuentes Sanchez PMI MemberID: 2399412
This copy is a PMI Member benefit, not for distribution, sale, or reproduction.