1 / 17

PRJ566 Project Planning and Management

PRJ566 Project Planning and Management. Lecture 3: Mana ging Scope and the Project Initiation Document. What is project scope?. A definition of the boundaries of the project. Why is scope important?. One of the biggest factors in project success

mallen
Download Presentation

PRJ566 Project Planning and Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PRJ566 Project Planning and Management Lecture 3: Managing Scope and the Project Initiation Document

  2. What is project scope? • A definition of the boundaries of the project

  3. Why is scope important? • One of the biggest factors in project success • Good scope definition = good client and IT understanding of what will be delivered and when • Ensures you understand WHERE you are going, HOW you will get there and WHEN you will arrive • This is where most projects start to fail!

  4. When do you define scope? • You define scope at the beginning of the project • You manage and control scope throughout the life of the project

  5. How do you define scope? • You talk to your client! • You research and clarify • You document • You negotiate • YOU DO THIS AGAIN AND AGAIN AND AGAIN....

  6. (Bad) Example: • Client: “Hmm…December 2006…Do you think you could deliver the reporting component by October?” You: “Sure! No problem!” NO! NO! NO! NO! NO!

  7. (Good) Example: • Client: “Hmm…December 2006…Do you think you could deliver the reporting component by October? You: “Let me look into it. I will get back to you with an answer by Friday.”

  8. (Good) Example: • You go and do some research...

  9. You: “I have looked into delivering the reporting component early, by October 10th. We can deliver Report A by October 10th, but our staff will be completely tied up with the main system until December 15th so we cannot deliver reports B and C until the original deadline. To give you B and C early we will have to pull people off of the main project at our busiest time which could make our project late.”

  10. Use Cases: Helping Define Scope • You can start defining systems use cases right from your initial client interviews. • This will help you develop a more accurate model of the system more quickly!

  11. Use Case Technique • System Use case diagram provides system overview • Defines system scope as the actors represent the boundaries of the system

  12. Project Initiation Document • A document describing the extent and functionality of the system you are proposing to develop. • In PRJ566 we use a specific template • Includes constraints, risks, legal/moral issues • Includes use case table

  13. Purpose of the PID • A starting point for the system—the first attempt at capturing SCOPE • Updated as the system is analyzed • Provides a good overview of the system • Provides a “checkpoint” to ensure all desired functionality is covered

  14. Scope • Remember…we define Scope at the beginning of the project and then manage it • The PID alone does not define scope and it is not cast in stone! • It must change as scope changes occur (and are managed!)

  15. PRJ566/666 Project Life Cycle Scope Phase 1: WBS for PRJ566 Phase 2: WBS For PRJ666 Execute Close Control PID + Use Case Model + UI Mock-ups+ …

  16. PID Template • On the PRJ566 site; let’s have a look • Scope • Use Case Grid • Constraints • Risks • Moral/Ethical/Legal issue • Example

  17. PID Exercise • Let’s start by answering this exercise

More Related