Project Management Office

<Project Name>

Feasibility Study

Feasibility Study Template Instructions

(Please remove this section before completion of template)

If used, a feasibility study should be completed and attached to the PSR submitted for review. The study should review current process and application processes with the desired outcome of each. The general requirements for the project should also be outlined. These requirements will be analyzed in greater detail during the requirements gathering portion of the project. The study should also address project funding and ongoing support funding.

Be sure to maintain version control as the study is modified and/or edited.

All instructions within the template are italicized within the document.

Any examples are in a red font.

Any portion of the template that does not fit or pertain to your project should be documented that it was reviewed and is not relevant. See below for requirements for a project and deliverable approvals.

Be sure to unlock table of contents by selecting TOC then Ctrl-Shift-F11 to enable TOC updating in Word docx.

Project Deliverable	Requirements by Project Size
Pre-Project Planning Phase	Large	Medium	Small	Requirements	Approvals
Feasibility Study (SDLC)	O	O	O	This is an optional requirement for all project sizes, unless requested by the Sponsor or during the project approval process. Any feasibility study generated is attached to the PSR submitted for review.	The Feasibility Study should be approved by the Sponsor and Requestor, at a minimum.

Table of Contents

1.	Introduction	2

1.1.	Purpose	2

1.2.	Assumptions	2

2.	Version Control	3

3.	Current Business Overview	4

3.1.	Current Business Definition	4

3.1.1.	Current Business Processes	4

3.1.2.	Current Business Applications	4

3.1.3.	Current Business Technologies	4

3.2.	Current Business Problems	4

3.2.1.	Business Process Problems	4

3.2.2.	Business Data Problems	5

3.2.3.	Business Application Problems	5

3.2.4.	Business Technologies Problems	5

3.2.5.	Other Business Problems	6

4.	Future Business Overview	7

4.1.	Future Business Processes	7

4.2.	Future Business Applications	7

4.3.	Future Business Technologies	7

5.	University Impact	8

5.1.	Impact on OIT Departments	8

5.2.	Impact on IT of Schools	8

5.3.	Impact on Server Storage Locations	8

6.	Requirements	9

6.1.	Business Process Requirements	9

6.2.	Application Requirements	9

6.3.	Support Requirements	9

6.4.	Hardware Requirements	9

6.5.	Platform Requirements	9

6.6.	Network Requirements	9

6.7.	Resource Requirements	9

6.7.1.	Design Resources	9

6.7.2.	Development Resources	9

6.7.3.	Testing Resources	10

6.7.4.	Implementation Resources	10

6.7.5.	Support Resources	10

6.8.	Product or System Trial Version Requirements	10

7.	Training	11

7.1.	Training Requirements	11

8.	Funding	12

8.1.	Project Funding	12

8.2.	Long Term Funding	12

9.	Conclusion/Analysis	13

10.	Approval	14

Introduction

Purpose

This feasibility study has been conducted to determine the best course of action on the xxxxxxx.

Assumptions

This document assumes.....

Version Control

Version	Date	Person	Change
1.0	Initial Document Creation

Current Business Overview

Current Business Definition

Current Business Processes

List each of the current business processes relevant to this project. Provide a description for each major business process. Depict all business processes within a process flow diagram in order to highlight typical business transaction types (e.g. the payments process).

Current Business Applications

List each of the current business applications (e.g. financial management system) relevant to this project. Provide a description for each current business application. Depict all business applications within an applications architecture diagram in order to highlight the interfaces between current business applications.

Current Business Technologies

List each of the current business technologies (e.g. mainframe) relevant to this project. Provide a description for each major technology. Depict all business technologies within a technology architecture diagram in order to highlight the interfaces between current business technologies.

Current Business Problems

Business Process Problems

List all issues and problems associated with the current business processes (as defined above).

Examples include:

Process efficiency problems

Process timeliness problems

Process dependency problems

Process relevancy problems

Rate and prioritise the problems highlighted above.

Business Data Problems

List all issues and problems associated with the current business data (as defined above).

Examples include:

Business data quality problems

Business data management problems

Business data maintenance problems

Business data adequacy problems

Business data consistency problems

Business data reliability

Business Application Problems

List all issues and problems associated with the current business applications (as defined above).

Examples include:

Business application reliability problems

Business application scalability problems

Business application relevancy problems (i.e. fit to business objectives)

Business application performance problems

Business application architecture problems

Business application sizing problems

Business Technologies Problems

List all issues and problems associated with the current business technologies (as defined above).

Examples include:

Business technology reliability problems

Business technology scalability problems

Business technology relevancy problems (i.e. fit to business application)

Business technology performance problems

Business technology architecture problems

Business technology sizing problems

Other Business Problems

List any other business problems here.

Examples include:

Lack of compliance with safety / regulatory standards

Future Business Overview

Future Business Processes

Using the Current Business Processes section, define the Future Business Processes.

Current Process	Requirement Summary	Future Process

Future Business Applications

Using the Current Business Application section, define the Future Business Applications.

Current Application	Requirement Summary	Future Application

Future Business Technologies

Using the Current Business Technologies section, define the Future Business Technologies.

Current Technology	Requirement Summary	Future Technology

University Impact

Impact on OIT Departments

Please describe all impact on any OIT department.

Impact on IT of Schools

Please describe all impact on any IT School department.

Impact on Server Storage Locations

Please describe all impact on any of the University server rooms.

Requirements

Business Process Requirements

Define and outline any business requirements that must be met for this project.

Application Requirements

Define application requirements for this project.

Support Requirements

Define support requirements that will be needed once project is completed.

Hardware Requirements

Define all hardware requirements for this project. Include desktop, external devices, servers, etc.

Platform Requirements

Define all platform requirements for this project. Include desktop operating system, server operating system, etc.

Network Requirements

Define network requirements to support this project hardware and software.

Resource Requirements

Design Resources

Provide the level of knowledge and estimated amount of time needed for design resource(s) for this project.

Development Resources

Provide the level of knowledge and estimated amount of time needed for the development resource(s) for this project.

Testing Resources

Provide the type of testing anticipated for this project with the amount of resources to complete the testing.

Implementation Resources

Provide the level of knowledge and estimated amount of time needed for the implantation resource(s) for this project.

Support Resources

Provide the level of knowledge and estimated amount of time needed for the support resource(s) for this project once completed.

Product or System Trial Version Requirements

If any product or system has a trial version available, requirements that have already been identified should be tested, but only during the RFP or RFI Sampling Process and not before. The test results should be documented and included for informational purposes to identify new technologies and products as they apply to the requirements. The documentation must include the functionality being tested in relation to the requirements, the results of testing and the conclusion and/or next steps.

For further reference, please review the university policy below:

Major Equipment Purchases

Training

Training Requirements

Outline the training requirement for this project. Include all training resources; trainers, training rooms, training computers needed.

Funding

Project Funding

Detail the funding for the project from initiation to closing, including design, development, and implementation.

Long Term Funding

Detail the funding for product of the project after project closing, including licenses, support, upgrades, enhancement, etc for five years post project.

Conclusion/Analysis

Outline what the final conclusion or analysis is of the feasibility study. Is if feasible? Why or Why not?

Approval

The individuals below agree that they have reviewed and approved the plan outlined in this Support Documentation.

APPROVED BY:
Function Role	Name and Title	Signature	Date