Justify It

It is crucial that the business case and measurable outcomes be clearly stated before even moving on. The commitment to proper vetting will insure you aren't working on make work or someone's pet projects. In reality, I don't see this fundamental discipline being adhered to.

OK, let's get down to practicalities. Here are some key questions to be asked and answered before you even start a project.

Business Case

Project Justification

1. Why do this project?
2. What happens if we don't do it?
3. Why do it now?
4. How critical will the impact of the project be?

Measurable Outcome

1. What are the measurable outcome to PROVE that the project objectives were met? This is KEY because just saying sales will increase just doesn't cut it.
2. Do the measurable outcomes make sense?
3. What baseline measurements will be used?
4. How and when will measurements be made?

Risk

1. What could go wrong? (both systems-related and user-related)

Costs

1. List all hardware, software, network, staff, facilities and other costs

Project Objective

1. Expressed as To, in a way that, so that construct

Background

1. Briefly describe how this project came about

Project Scope

1. What business functions are in and out of scope?
2. What are the critical requirements?
3. What business procedures are required?
4. What production operations procedures are required?

Constraints

1. What is the maximum cost of the project?
2. What is the latest project completion date?
3. What are the interproject dependencies?
4. What production operations procedures are required?

Current Issues

1. Briefly describe any issues that will need to be addressed prior to or during the project