Download
1 / 19
210 likes | 418 Views
PRJ566 Project Planning and Management. Managing 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
E N D
PRJ566 Project Planning and Management Managing 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 • 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!
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
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....
(Bad) Example: • Client: “Hmm…December 2008…Do you think you could deliver the reporting component by October?” You: “Sure! No problem!” NO! NO! NO! NO! NO!
(Good) Example: • Client: “Hmm…December 2008…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.”
(Good) Example: • You go and do some research...
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.”
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!
Use Case Technique • System Use Case diagrams provide system overview • Define system scope as the actors represent the boundaries of the system
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
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
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!)
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+ …
PID Template • On the PRJ566 site; let’s have a look • Scope • Constraints • Risks • Moral/Ethical/Legal issue • Example
