Project Scope - if it's true that a project succeeds or fails at the start/inception - then one of the prime factors in that is the project scope. Many projects begin without a well defined scope and often varying definitions of it depending on who you ask. SO - to increase the
likelihood of success - take the extra time to properly define the scope and communicate it out well. Thinking through it - a project scope should consist of (notice the mind map above...):
- Deliverables
- Boundaries
- Impacts
- Costs
- Success Factors
Drilling down on
deliverables a bit (as an example) - sub items to
deliverables should include:
- product list (HW, SW, delivery mechanism)
- in/out list
- quality level (no one expects perfection - state what the realistic goal is in some meaningful language)
- training
- artifacts - aka documentation
(you can click on the above mind map for more detail)
Project Scope - if it's true that a project succeeds or fails at the start/inception - then one of the prime factors in that is the project scope. Many projects begin without a well defined scope and often varying definitions of it depending on who you ask. SO - to increase the likelihood of success - take the extra time to properly define the scope and communicate it out well. Thinking through it - a project scope should consist of (notice the mind map above...):
No comments:
Post a Comment