Project Scope Management for Plan , collect , define

 Project Scope Management :

include the process required to ensure the project include all the work required and only work required to success the project .

defining and controlling what is and is not included the project .

Product Scope :

 features and functions that characterized the product , service and result .

Project Scope :

 the work performed to deliver a product , service or result with specified features and functions .

Scope Creep :

 lack of scope management leads to adding work not authorized or budgeted of the project .

so we said , any process have ITTOS [INPUT-TOOLS AND TECHINQUES _OUTPUT]

the first process in scope management :

plan scope management :

creating a scope management plan that document how the product and project scope will be define , validated and controlled .

The key benefit : provide guidance and direction on how scope will be managed .

Inputs : 

• Project charter :
  project purpose ,high project description ,requirements , assumptions and constrains .
• Project management plan :
  quality management plan , project life cycle and development approach .
• Enterprise environmental factor 
  
• organizational process assets 
  

Tools and techniques :

• Expert judgment :group with special knowledge ,training or experts in scope management .
• Data analysis :various ways to collect requirements , elaborating project and product scope ,validating and control.
• Meetings :to develop the scope management plan [get approval ].

Output :

• scope management plan :
  component of project management plan that describes how the scope will be defined , developed , monitoring and control .
• Requirements management plan :
  component of project management that describes how project and product requirements will be analyzed .

Collect Requirement :

Determining , documenting and managing stakeholder needs and requirements .

Key Benefits : provides the basis for defining the product and project scope .

Inputs:

• Project Charter : high level project description and requirements .
• Project management plan : 

1. -Scope Management plan : how the project scope will be defined and developed .
2. -management of stakeholder : how requirements will be collected , analyzed and document .
3. -stakeholder engagement plan : stakeholder communication requirement .

• Project document : assumption log ,lessons learned , stakeholder register .
• Business document : business needs .
• Agreements : project and product requirements .
• EEFS 
• OPA

Tools and Techniques : 

• Expert Judgment : business analysis , requirements analysis , documentation , facilitation and conflict management .
• Data gathering : brainstorming , interviews , focus group , questionnaires , and benchmarking .
• Data analysis : review and assessing any relevant documented  info to elicit requirement .
• decision making : voting [ unanimity (majority - plurality) - Autocratic (individual decision - multicriteria ) ] .
• Interpersonal and team skills : 

1. Nominal group technique 
2. observation conversation 
3. facilitation 

Outputs :

• Requirements Documentation :

1. requirements must be measurable and testable .
2. business requirements : needs of organizations .
3. stakeholders requirements : needs of stakeholders .
4. solution requirements : functionals / non functional .
5. Transition requirements : capability to move from state to other .
6. Quality requirements : criteria for deliverables acceptance .

• Requirements traceability matrix [RTM] .

Define Scope : 

developing a detailed description of project .

Key Benefits : describe the product , service , result boundaries and acceptance criteria .

Inputs : 

Project Charter : 

Project management plan : scope management plan .

Project Document : assumption log / requirement documentation / register of risk .

EEFS

OPAS

Tools and Techniques :

Expert judgement :

Data analysis :alternative analysis - system analysis - value analysis .

Decision making : like collect requirements .

Interpersonal and team skills : the same too .

Product analysis : translating high level of project requirements and description into meaningful deliverables .

Output :

Project scope statement : 

description of project scope ,deliverables , assumptions and constrains .

Project scope updated :

Assumption log / requirements documentation /stakeholders requirements .