Establishing Project Justification, Description, Outcomes, Scope and Milestones

Project Justification

Describe the business need, opportunity or problem that the project was undertaken to address – i.e., the project justification, the reason for the project.
2. PROJECT DESCRIPTION
Provide a high-level description of what the project is and a general statement about what the project is expected to accomplish. Describe the project outcomes using action words (verbs) such as “deliver, provide, create, research”, etc.Outcomes should be measurable, so the Project Sponsor and Team can determine whether the outcome has been successfully completed at the project’s conclusion.
3. SCOPE DEFINITION
Measures of PerformanceDriver: A single statement that describes the business result that must be achieved. It avoids “how” statements and focuses on what needs to be achieved as the project’s impact on business results.Restrictions (1-3): A boundary you must work within in order to succeed. What must you not sacrifice in order to achieve the outcome described in the Driver statement? Restrictions are limitations on how you go about delivering project results, and they always relate to the result of the project. Avoid mentioning time and cost constraints in these statements.
4. PROJECT MILESTONES
Identify the significant project milestones, for example required end date, final invoicing date or other similar must-do timelines.
5. ASSUMPTIONS, RISKS & DEPENDENCIES
List any risks (potential factors that will impact the delivery or make it difficult to manage the project) on the project or dependencies on resources or funding to the project. Consider time, cost, dates and regulatory issues as risks or dependencies to the project.List any other assumptions – conditions we assume to be true in order to execute the project.