CHATER 5 PROJECT SCOPE MANAGEMENT
Projects can be completed in two ways: <ul><li>Planned and then executed or  </li></ul><ul><li>Executed, stopped, planned ...
Project Scope Management <ul><li>includes the processes required to ensure that the project includes all the work required...
Project Scope Management Processes <ul><li>Collect Requirements:   The process of defining and documenting stakeholders’ n...
Project Scope Management Processes <ul><li>Verify Scope :   The process of formalizing acceptance of the completed project...
Context of Scope <ul><ul><li>Product scope . The features and functions that characterize a product, service, or result </...
Scope Baseline <ul><li>The approved detailed project scope statement and  </li></ul><ul><li>its associated WBS and WBS dic...
Collect Requirements
Collect Requirements  <ul><li>Collect Requirements is the process of defining and documenting stakeholders’ needs to meet ...
Collect Requirements: Inputs, Tools & Techniques, and Outputs
GROUP CREATIVITY TECHNIQUE <ul><li>Brainstorming  </li></ul><ul><li>Nominal Gp </li></ul><ul><li>The Delphi Technique </li...
MIND MAP
http://www.jiludwig.com/Requirements_Management.html
GROUP CREATIVITY TECHNIQUE <ul><li>Brainstorming  </li></ul><ul><li>Nominal Gp </li></ul><ul><li>The Delphi Technique </li...
Affinity Diagram <ul><li>Affinity diagrams are great tools for assimilating and understanding large amounts of information...
Group Decision Making Techniques <ul><li>Unanimity </li></ul><ul><li>Majority </li></ul><ul><li>Plurality </li></ul><ul><l...
OUTPUTS <ul><li>Requirement Doc </li></ul><ul><li>Requirement Mgmt Plan </li></ul><ul><ul><li>How requirement activity wil...
 
Define Scope
Define Scope:  Inputs, Tools & Techniques, and Outputs
 
WBS
Create WBS: Inputs, Tools & Techniques, and Outputs  <ul><li>Points to remember; </li></ul><ul><ul><li>100% Rule </li></ul...
 
 
 
 
Verify Scope:  Inputs, Tools & Techniques, and Outputs
 
CONTROL SCOPE
Control Scope <ul><li>Process of monitoring the status of project and product scope and managing changes to the scope base...
Control Scope:  Inputs, Tools & Techniques, and Outputs
 
Control Scope:  Inputs, Tools & Techniques, and Outputs
Upcoming SlideShare
Loading in …5
×

802003 634318955109991250

1,226 views

Published on

hr

Published in: Business, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,226
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
68
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

802003 634318955109991250

  1. 1. CHATER 5 PROJECT SCOPE MANAGEMENT
  2. 2. Projects can be completed in two ways: <ul><li>Planned and then executed or </li></ul><ul><li>Executed, stopped, planned and then executed. </li></ul>
  3. 3. Project Scope Management <ul><li>includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. </li></ul><ul><li>Managing the project scope is primarily concerned with defining and controlling what is and is not included in the project. </li></ul>
  4. 4. Project Scope Management Processes <ul><li>Collect Requirements: The process of defining and documenting stakeholders’ needs to meet the project objectives. </li></ul><ul><li>Define Scope: The process of developing a detailed description of the project and product . </li></ul><ul><li>Create WBS: The process of subdividing project deliverables and project work into smaller, more manageable components. </li></ul>
  5. 5. Project Scope Management Processes <ul><li>Verify Scope : The process of formalizing acceptance of the completed project deliverables. </li></ul><ul><li>Control Scope : The process of monitoring the status of the project and product scope and managing changes to the scope baseline </li></ul>
  6. 6.
  7. 7. Context of Scope <ul><ul><li>Product scope . The features and functions that characterize a product, service, or result </li></ul></ul><ul><ul><ul><li>Completion of the product scope is measured against the product requirements </li></ul></ul></ul><ul><ul><li>Project scope . The work that needs to be accomplished to deliver a product, service, or result with the specified features and functions. </li></ul></ul><ul><ul><ul><li>Completion of the project scope is measured against the project management plan </li></ul></ul></ul>
  8. 8. Scope Baseline <ul><li>The approved detailed project scope statement and </li></ul><ul><li>its associated WBS and WBS dictionary are the scope baseline for the project. </li></ul><ul><li>This base lined scope is then monitored, verified, and controlled throughout the lifecycle of the project. </li></ul>
  9. 9. Collect Requirements
  10. 10. Collect Requirements <ul><li>Collect Requirements is the process of defining and documenting stakeholders’ needs to meet the project objectives. </li></ul><ul><li>Requirements become the foundation of the WBS. </li></ul><ul><li>Product requirements can include information on technical requirements, security requirements, performance requirements etc. </li></ul>
  11. 11. Collect Requirements: Inputs, Tools & Techniques, and Outputs
  12. 12.
  13. 13. GROUP CREATIVITY TECHNIQUE <ul><li>Brainstorming </li></ul><ul><li>Nominal Gp </li></ul><ul><li>The Delphi Technique </li></ul><ul><li>Idea Mind Maping </li></ul>
  14. 14. MIND MAP
  15. 15. http://www.jiludwig.com/Requirements_Management.html
  16. 16.
  17. 17. GROUP CREATIVITY TECHNIQUE <ul><li>Brainstorming </li></ul><ul><li>Nominal Gp </li></ul><ul><li>The Delphi Technique </li></ul><ul><li>Idea Mind Maping </li></ul><ul><li>Affinity Diagram </li></ul>
  18. 18. Affinity Diagram <ul><li>Affinity diagrams are great tools for assimilating and understanding large amounts of information. </li></ul><ul><li>When you work through the process of creating relationships and working backward from detailed information to broad themes, you get an insight you would not otherwise find. </li></ul>
  19. 19.
  20. 20. Group Decision Making Techniques <ul><li>Unanimity </li></ul><ul><li>Majority </li></ul><ul><li>Plurality </li></ul><ul><li>Dictatorship </li></ul>
  21. 21. OUTPUTS <ul><li>Requirement Doc </li></ul><ul><li>Requirement Mgmt Plan </li></ul><ul><ul><li>How requirement activity will be planned </li></ul></ul><ul><ul><li>Configuration mgmt activity as how changes to the product </li></ul></ul><ul><li>Requirement Prioritization Process </li></ul><ul><ul><li>Product matrix </li></ul></ul><ul><li>Traceability structure </li></ul>
  22. 22.
  23. 24. Define Scope
  24. 25. Define Scope: Inputs, Tools & Techniques, and Outputs
  25. 27. WBS
  26. 28. Create WBS: Inputs, Tools & Techniques, and Outputs <ul><li>Points to remember; </li></ul><ul><ul><li>100% Rule </li></ul></ul><ul><ul><li>Rolling Wave Planning </li></ul></ul><ul><ul><li>Control account </li></ul></ul><ul><ul><li>Work Package </li></ul></ul>
  27. 33. Verify Scope: Inputs, Tools & Techniques, and Outputs
  28. 35. CONTROL SCOPE
  29. 36. Control Scope <ul><li>Process of monitoring the status of project and product scope and managing changes to the scope baseline </li></ul><ul><li>This step ensures all requested changes and recommended corrective or preventive actions are processed through ICC </li></ul><ul><li>Uncontrolled changes are often referred to as scope creep </li></ul>
  30. 37. Control Scope: Inputs, Tools & Techniques, and Outputs
  31. 39. Control Scope: Inputs, Tools & Techniques, and Outputs

×