Project Management Methodology and Scoping
When scoping for a new product, put together a small Project Charter document which lists the scope of what it is you are trying to create and the strategy of how you intend to deliver it.
The document's purpose is to ensure all proposed users of your product agree, what it is they are looking for.
- What is the product you are building?
- What are the high level objectives and goals?
- Often it is necessary to also list what is out of scope to prevent "scope creep"
- What are the timescales?
- What are the costs?
- It's probably useful to also include some "blue prints" at this stage
- Have you got well defined roles and responsibilities defined for the project?
- Is there an effective and constant process in place for the management of risks and issues?
- Is there a change managementprocess in place, and you have assigned a change manager from the business. Many projects encounter unknowns (i.e. unpredicted requests for change or issues) which need to be managed effectively to keep a project on track.
- Are people ready to change?
- How will you measure after that you have succeeded, i.e. do you have a list of success factors.
- Are there clearly defined and open lines of communication to ensure everyone will know at all times where your project is at?
- Ensure the scope is signed off by all proposed users before proceeding so there are clearly defined expectations from the offset.
Return to Project Methodology Definition
Be a pioneer and write the first comment.
Note: Current average rating of based on reviews and ratings. (1-Low, 5-High)
Note: Comments and ratings help this site get better; if you see something missing, see something wrong, have a question, or want to suggest something to improve then comment below and join the dialogue;