Inputs | Tools and Techniques | Outputs |
---|---|---|
|
|
|
Project Charter: The project charter provides high-level information about the project, including its objectives, constraints, and assumptions, which influence scope management planning.
Project Management Plan: Elements such as the scope management plan, project schedule, and project budget provide context for scope planning.
Enterprise Environmental Factors : External factors such as industry standards, organizational culture, and marketplace conditions can influence how scope is managed.
Organizational Process Assets : Past project files, templates, and lessons learned related to scope management provide valuable insights for planning.
Expert Judgment: Input from individuals or groups with expertise in scope management or similar projects can provide valuable insights for planning.
Data Gathering: Techniques such as brainstorming, surveys, or focus groups can be used to collect information about scope requirements and stakeholders' expectations.
Data Analysis: Analyzing historical project data, stakeholder requirements, and organizational process assets helps in understanding scope management requirements.
Decision Making: Techniques such as decision trees or multi-criteria decision analysis (MCDA) may be employed to make decisions about scope management approaches.
Interpersonal and Team Skills: Effective communication, negotiation, and conflict resolution skills are essential for defining scope management processes.
Scope Management Plan: The scope management plan is a component of the project management plan that describes how scope will be defined, validated, controlled, and managed throughout the project lifecycle.
Requirements Management Plan: Sometimes included as part of the scope management plan, this document outlines how requirements will be analyzed, documented, and managed.
Project Scope Statement: A narrative description of the project scope, including its objectives, deliverables, constraints, and assumptions.
Requirements Documentation: Detailed descriptions of the project requirements, including functional and non-functional requirements, constraints, and assumptions.