Information contained within this document is proprietary. The information may not be copied, reproduced or disclosed, in any manner, whole or in part, without prior written permission.

(Remove all this text to put your information in) The Executive Summary provides high level view of the situation and its impact on the organization and overview of Business strategy. – The greater the detail on this an every other section the better the grade on this assignment – if you provide basic information you will get a basic grade. You may (should) conduct some research into the product and requirements)

Solution Overview

(Remove all this text to put your information in) Provide a brief overview of the CHOSEN solution and what it will do for the organization and how it will align with the Business Strategy

Stakeholder Analysis

The Stakeholder Analysis provides an overview of all individuals affected by the project. The level of impact the project will have on them, the level of influence they have on the success or demise of the project, their attitude about the project, and their communication preference via RACI (Responsible, Accountable, Consulted, Informed regarding aspects of the project)

Name

Role in Org.

Level of Impact/Influence

High or Low

Attitude about Project

For or Against

Communication Preference

RACI

Chris P. Bacon

CIO

High/High

For

Assumptions

(Remove all this text to put your information in) List any assumptions for the project – Assumptions are supposed to be true, but may not always end up true (Examples: Equipment will be delivered by a certain date or Electrical Power and Ethernet capabilities will be in place before project begins- remember, assumptions are risks if it is found they are not true)

Constraints

(Remove all this text to put your information in) List any limitations that may constrain this project- DO NOT put Non-Functional Requirements here. (Examples: Budge is X amount of $, or you only have so many hours that personnel can work on the project, any other roadblocks that constrain the project -which may also be risks)

Requirements

Functional Requirements:

(Remove all this text to put your information in) List out all Functional requirements – Anything that effects HOW the system BEHAVES (Remember they shall have the word shall, they should conform to the “Good Requirement” listed on the course slide presentation (examples given below-yes you can keep these if they fit but you need to add more)

EXAMPLE: The system shall allow multiple concurrent logins and users

The system shall…

Non-Functional Requirements:

(Remove all this text to put your information in) List out all Non-Functional requirements, anything that does not impact the functionality, such as storage, security, again use the words shall

EXMPLE: The system shall have an easy to use common user interface for ease of access and familiarity in usage when switching between programs.

EXAMPLE: The system shall have greater than XXTB of storage.

The system shall….

Alternative Analysis

No Project (Status Quo)	Reasons for Not Selecting Alternative
Keep the current system
Alternative Option	Reasons for Not Selecting Alternative
Solution #2
Alternative Option	Reasons for Not Selecting Alternative
Solution #3
Chosen Solution

Project Recommendation

Schedule/Milestones

(Remove all this text to put your information in) What is the proposed schedule for this project? What metrics(requirements) must be met along the way

(example) – Month 1 after approval begin hiring process for required personnel

Month 1- begin research on various server blade manufactures

Month 2 -….

Risks

Risk score is Frequency multiplied (Do NOT touch this table; Entries are in the next table)

Frequency	Numeric	Description	Severity	Numeric	Description
Frequent	5	Happens most of the time	Catastrophic	5	Failure of project
Probable	4	Will probably happen	Critical	4	Potential for severe delay
Occasional	3	May happen in some form	Moderate	3	Potential for moderate delay
Remote	2	Possible but unlikely	Minor	2	Potential for minor delay
Improbable	1	Very unlikely to happen	Negligible	1	No significant delay

What are the risks that can keep the project from being completed? Risk score= Frequency x Severity

Risk #	Risk Name	Description	Factors	Effect	Freq	Sev	Risk Score	Trigger	Mitigation	Contingency
1	Hardware	Hardware may not show up on time	Using new vendor	May cause schedule delay	3	3	9	Vendor provides receive date later than required	Contact vendor to find out lead time for early ordering	Order from Secondary Vendor and pay for overnight shipping

Justification

Benefits

(Remove all this text to put your information in) What are the benefits of this project such as Financial (how), Morale, Competitive Advantage, Innovation (What is the return on investment)

Organizational Impact

Impact

(Remove all this text to put your information in) Are there any policy, governance, or employee changes (hiring/layoffs)

Personnel Requirements

(Remove all this text before submitting How many individuals are proposed for this project and what are their skill sets. Type of person (engineer, project manager, etc You may need more or less than what is listed below as they are examples) and their cost… Labor cost is hourly not annually (go to Salary.com to find pay scales – remember to break it down to hourly)

Type of Personnel	Burdened Labor Cost = hourly cost plus 50%
Project Manager	$
Software developer	$
Sever maintenance	$
Customer Support	$
Software Trainer	$
Infor Assurance	$

Cost Benefit Analysis

TCO

Provide a total cost of ownership

Provide a Return on Investment (ROI) on expenditures required to complete project vs predicted income generated from completing project.

Conclusion & Recommendation

(Remove all this text to put your information in) Provide your conclusion & recommendation here.. Brief overview of situation, chosen solution, costs, benefits, changes to org and any other reason you are recommending this project) (AND Cite any websites, articles you used for research during the building of this business case)

Page | 6

CONFIDENTIAL Internal Document