Décrire la valeur du projet à l'aide d'une analyse de rentabilisation. Il peut être difficile de comparer et de hiérarchiser les projets de votre portefeuille, car il existe différents types de projets. Certains projets pourraient augmenter les revenus, d'autres pourraient diminuer les coûts et d'autres pourraient aider à renforcer les capacités internes. Tous ont un certain avantage, mais il peut ne pas être facile de savoir lesquels sont les plus utiles et lesquels sont les plus alignés sur vos objectifs et vos stratégies.

One of the ways that you compare projects is through a common Business Case. The Business Case describes the reasons and the justification for the project based on its estimated costs, the risks involved and the expected future business benefits and value. The sponsor is responsible for the Business Case.

Business Cases should contain the following information:

Executive Summary. This section contains five components:

1. Opportunity Statement. This is often written as a problem statement, describing a current situation with a negative business impact, which the implementation of this project will resolve.
2. Desired State. Given the business opportunity, what do you see as being the final result of this project?
3. Benefit Analysis. We’ll cover more detail later, but at a high level describe the benefits of implementing this project and obtaining your desired state. How will the business be better off?
4. Alternative Analysis. If multiple alternatives were explored to realize the business opportunity, briefly describe these alternatives here.
5. Recommendation. Given your opportunity, desired state, benefits, and alternatives, what is it that you’re recommending being done?

Overview

1. Project Description. Summarize the project you are proposing.
2. Project Goals & Objectives, List the goals and objectives of this project.
3. Assumptions. There may be several items you are assuming to be true, which you have not been able to verify.
4. Constraints. List any constraints that will govern or limit the project team.
5. Proposed Solution Design. Describe the high-level approach that will be taken.
6. Project Resource Needs. Briefly describe the resources you will need to deploy this project.
7. Project Duration. List the high-level milestones and best-guess as to the duration of each.
8. Risk Assessment. List initial known risks of the project.

Cost Benefit Analysis. Provide a high-level estimate of the costs and benefits of the project. The format of this section should be consistent for all projects so that the projects can be compared.

Alignment. All projects should align to your organization's strategic plan. Some align better and take the organization further. The alignment should be described so that it is clear how the project helps to move the organization to its desired future state.

ConclusionSummarize the business case and draw one or more conclusions regarding the proposed solution, business value, ROI, etc.

It may seem like this is a lot of work. In fact, it might be. However, the Business Case is used to determine the projects that get funding and those that don’t. So, it is important to spend the right amount of time on the Business Case. If you don’t do a good job on this document, your project may not compare favorably with other projects that have more detail and relevant information. by Danielle Smallwood, TenStep Thomas Mochal