Business Case
Project Name Goes Here
The cover page is optional. It is intended to provide a neat, uncluttered welcome to the
document. It can serve as a separator page in a binder or folder of related documents
and highlights any watermark that is present.
Document1
Page 1 of 3
Contents
Overview ....................................................................................................................................................... 3
Problem Statement ................................................................................................................................... 3
Proposed Future State .............................................................................................................................. 3
Goals and Objectives................................................................................................................................. 3
Success Criteria ......................................................................................................................................... 3
Analysis ......................................................................................................................................................... 3
Strategic Alignment................................................................................................................................... 3
Preferred Approach .................................................................................................................................. 3
Cost/Benefit Analysis ................................................................................................................................ 3
Technical Alignment.................................................................................................................................. 3
Risks, Constraints, Assumptions ............................................................................................................... 3
Appendix ....................................................................................................................................................... 3
The table of contents is optional. It is intended to highlight the structure and thoroughness of the
document.
The elements of the Overview section are intended to provide a brief (one page) summary of the project
at an “executive summary” level. They are “the pitch” and may be the only opportunity to sell the
project to management.
The elements of the Analysis section should provide more details and discussion of the Overview. They
should anticipate the follow-up questions likely to come from the Overview.
The footer should include the file name and page numbers, for easy reference when reviewing and
discussing the document. A version number or date can also be useful.
Document1
Page 2 of 3
Overview
Problem Statement
Describe what needs to be introduced, changed, and/or retired, and why. What are the processes,
technologies, and associated roles? What is driving the need?
Proposed Future State
Describe the vision of the processes/technologies/roles as they will be after successful completion of the
project. How will they work and integrate? Who will do what? How does it solve the problem?
Goals and Objectives
Break down the vision into specific, measurable, attainable, relevant, and timely goals. Is the goal
unambiguous? Can it be proven to be achieved? Is it reasonable and meaningful to the University? Is
there a deadline? “Lose weight by New Year’s.”
For each goal, describe a set of specific objectives. “Exercise more.”, “Eat less.”
Success Criteria
Each objective should include definitive criteria that will determine if the project’s performance in this
area is successful. “Burn at least 500 calories per day.”, “Skip dessert five days a week.”
Analysis
Strategic Alignment
Describe specifically how the project meets or directly supports a strategic objective of the University,
MAU, or department. Explain how the project’s goals match the organization’s.
Preferred Approach
Describe how the problem will be solved: begin to bridge the gap between the current and future states
with tactical steps.
Cost/Benefit Analysis
Estimate, within a +/-75% range, the project’s cost in terms of dollars and personnel. Identify savings
from the project’s goals and compare them to the cost estimates. Narratives are sufficient; number
ranges are preferred. If known, identify potential funding sources.
Technical Alignment
Ensure the compatibility of any technology deliverables with UA standards and/or identify any new or
disruptive technologies.
Risks, Constraints, Assumptions
Identify, in a bulleted list, any:



Risks (potential issues affecting the project scope, schedule, cost, or quality)
Constraints (known issues outside of the control of the project team; e.g., compliance mandates
or the academic calendar)
Assumptions (important considerations, positive and negative, to be noted)
Appendix
Include any further details or reference documents.
Document1
Page 3 of 3