APPLICATION DEVELOPMENT NETWORK

DIVISION OF INFORMATION TECHNOLOGY

UNIVERSITY OF MISSOURI

{Project Name}

Project Charter

{Customer Name and/or Department}

{Customer Name and/or Department}

Friday, 13 April 2012

Purpose

The what and why of the project.  Why is it being done? What will this project achieve for your department or group?

Current Status

•    Requirement Gathering, Planning, and Design:
•    Development:
•    Release and Deployment:

Application Sponsor

                         Date:
       Sponsor (Name):
 Sponsor Department:

Target Audience

Project Objectives (Features)

Objective #1:

Success Criteria #1:

ADN Staff

All ADN staff, students and DoIT resources involved in the project.

Technology Utilized

Platforms: .NET Web App, iPhone mobile app, Joomla website.

• Direct Benefit to students or staff:
• Platform/Languag:
• Database:
• UM Data Level:
• Patient Data:
• SSN Data:
• FERPA Data:
• Credit Card Data:

Success Criteria

Inital Assumptions and Constraints

Type (A or C) | Description

Project Scope

In Scope

• In Scope #1

Out of Scope

• Out of Scope #1

Deliverables and Target Schedule

Target Due Date | Deliverable Description

Flexibility Matrix

Rank Each of these in terms of "Least Flexible"; "Moderately Flexible"; "Most Flexible".

• Scope (Functionality):
• Schedule (Time):
• Cost:

Appendix A - Change Management

Changes in the Project can occur in three major areas:
1.    scope of the project,
2.    schedule, and/or
3.    budget. 
Anyone can submit a change to the project.  Changes in scope will most likely affect the schedule of the project and may affect the project budget.  Therefore scope change requests will require an analysis that discusses both schedule and budget impacts.  Any change request can be submitted by e-mail to the Primary ADN Personnel  and should include a description of the change and the reason it is required.