COMMON MANAGEMENT SYSTEMS
Project Data Form
<<Project Title >> Data Form
<<Date>>
Document Control and Approval
Date
By
Action/Change Reference
Document Creation
1. Goal Description
What are we trying to achieve?
2. Triggering Problems/Opportunities
What is occurring that we are trying to improve?
3. Performance Measures and Targets
How will we know we are successful with this project?
4. Deliverables
What are the high level products or services that will result from this project?
5. Project Organization & Resource Requirements:
Role
Definition
Executive Sponsor
Senior Director or VP who is responsible to SSU for the success of the
project and navigating high level project issues such as budget. E.g. Jason
Wenrick or Larry Furukawa Schlereth.
Division or Department Head of area the project will benefit. E.g. Mathew
Lopez Phillips, Student Affairs and Enrollment Management
IT Director responsible for stewardship of resources E.g. AIS Director Lou
Ann Seaman
Functional CMS staff responsible for managing project from request to
completion. E.g. Student Records Lead
Technical staff member responsible for managing and often completing
technical tasks of project. E.g. AIS Analyst Programmer
Staff members who exhibit the highest level of expertise in performing a
specialized job, task, or skill. SMEs define requirements and are often heavily
involved in testing and training. E.g. Director of Academic Scheduling.
Staff members who have specific tasks on a project schedule and actively
contribute to project’s goals. E.g. Academic Records Specialist.
Are there any additional stakeholders than need to be made aware of this
change or who this change directly affects? E.g. Administrative Managers,
Admissions and Records.
Project Sponsor
IT Sponsor
CMS Project Lead
Technical Project
Lead
Subject Matter
Expert
Project team
members
Other stakeholders
Who
6. Project Budget
Any dollars/ accounts assigned to the project
7. Risks
What will we do if project is not completed successfully?
8. Solution Options Investigated
At the time this form is completed, an assessment should be made as to the solution options available and a recommendation.
Specifically, an assessment is made as to whether the need can be met through:
a. A change in business process
b. Existing functionality
Page 1 of 2
6/30/2016
COMMON MANAGEMENT SYSTEMS
Project Data Form
c.
d.
A modification already created by another Campus
A new local modification.
a) Options
Option
E.g. Option 1:
PeopleSoft modification from San
Marcos/Longbeach.
Considerations
 Due to limited resources and competing priorities, extended
delivery time.
 Internal cost of maintenance.
 Limited resources for further development.
Option 2:
Benefits
 Can be tailored to our requirements.
 Utilizes existing software, no outgoing cost, just
internal for development and maintenance.
 No interfaces required.
 Infrastructure already exists. E.g. connection to
CashNet.

Option 3:



b) CMS Recommendation:
Option 1:
PeopleSoft modification from San Marcos/Longbeach.
c) Option chosen:
Option 2:
9. Scope
a) Included:
What will occur?
b) Excluded:
What won’t occur?
10. Project Timeline: Major Milestones
Milestone (major sign of progress)
Date to be completed


10/13/09
E.g. Project Plan complete
E.g. User training completed
11. Technical Support Requirements (Business and IT)
Do we need an additional server, software licenses? Will solution be supported by Chancellors Office or SSU?
12. Communication Requirements
What user or project communication is required?
13. Training Requirements
What training is required? Staff, IT?
14.
Page 2 of 2
6/30/2016