Project Management C5 -scope_management

  • 228 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
228
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
15
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Project Scope Project scope is everything about a project – work content as well as expected outcomes. Scope management is the function of controlling a project in terms of its goals and objectives and consists of: 1) Conceptual development 2) Scope statement 3) Work authorization 5-2 4) Scope reporting 5) Control systems 6) Project closeout Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 2. Conceptual Development The process that addresses project objectives by finding the best ways to meet them. Key steps in information development: • Problem/need statement • Information gathering • Constraints • Alternative analysis • Project objectives 5-3 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 3. Problem Statements Successful conceptual development requires: • Reduction of overall project complexity • Goals and objects are clearly stated –Reference points are provided • Complete understanding of the problem 5-4 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 4. Statement of Work (SOW) A SOW is a detailed narrative description of the work required for a project. 1. 2. 3. 4. 5-5 Effective SOWs contain Introduction and background Technical description Timeline and milestones Client expectations Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 5. The Scope Statement Process 1. Establish the project goal criteria a) b) c) d) e) cost schedule performance deliverables review and approval gates 2. Develop the management plan for the project 3. Establish a work breakdown structure 4. Create a scope baseline 5-6 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 6. Work Breakdown Structure a process that sets a project’s scope by breaking down its overall mission into a cohesive set of synchronous, increasingly specific tasks. What does WBS accomplish?  Echoes project objectives  Offers a logical structure  Establishes a method of control  Communicates project status  Improves communication  Demonstrates control structure 5-7 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 7. Work Breakdown Structure and Codes The project is the overall project under development 1.0 1.2 1.3 1.4 1.2.1 1.3.1 1.2.2 1.3.2 1.2.3 1.2.3.1 1.2.3.2 5-8 Deliverables are major project components Subdeliverables are supporting deliverables Work Packages are individual project activities Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 8. Organizational Breakdown Structure Organizational Breakdown Structure (OBS) allows • Work definition • Owner assignment of work packages • Budget assignment to departments OBS links cost, activity & responsibility 5-13 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 9. Responsibility Assignment Matrix LEAD PROJECT PERSONNEL Task Ann Dave Sue Jim Bob Deliverable & Code HR R&D R&D IS IS Match IT to Problem Org. Tasks Analysis 1.1.1 1.1 Develop 1.1.2 info Interview Identify IS user needs 1.2.1 1.2 users Develop 1.2.2 show Gain user “buy in” 1.2.3 Prepare Find cost/ 1.3.1 proposal 1.3 benefit info Notification Responsible 5-14 Support Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Approval
  • 10. Work Authorization The formal “go ahead” to begin work Follows the scope management steps of: 1. scope definition 2. planning documents 3. management plans 4. contractual documents 5-15 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 11. Contractual Documentation Most contracts contain: Requirements Valid consideration Contracted terms Contracts range from: Lump Sum Cost Plus also called “Turnkey” 5-16 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 12. Scope Reporting determines what types of information reported, who receives copies, when, and how information is acquired and disseminated. Typical project reports contain 1. Cost status 2. Schedule status 3. Technical performance 5-17 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 13. Types of Control Systems o Configuration o Design o Trend monitoring o Document o Acquisition o Specification 5-18 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 14. Project Closeout The job is not over until the paperwork is done… Closeout documentation is used to: Resolve disputes Train project managers Facilitate auditing Closeout documentation includes: Historical records Post project analysis Financial closeout 5-19 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 15. What about IT Projects???? 5-20 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 16. FLOWCHART 5-21 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 17. 5-22 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 18. 5-23 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 19. Sample WBS in MS Project 5-24 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 20. 5-25 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 21. 5-26 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 22. Responsibility Assignment Matrix LEAD PROJECT PERSONNEL Task Ann Dave Sue Jim Bob Deliverable & Code HR R&D R&D IS IS Match IT to Problem Org. Tasks Analysis 1.1.1 1.1 Develop 1.1.2 info Interview Identify IS user needs 1.2.1 1.2 users Develop 1.2.2 show Gain user “buy in” 1.2.3 Prepare Find cost/ 1.3.1 proposal 1.3 benefit info Notification Responsible 5-27 Support Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Approval
  • 23. 5-28 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall
  • 24. 5-29 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall