Transcript Program Release 2008 - University of Wisconsin–Madison

Program Release
2008
Update to the Administrative
Council
August 9, 2007
1
Program Release Scope

Strategic
Administrative
Projects






ATS
Effort
Grants
LAST
SFS
Supply Chain /
APPO

Strategic
Interoperability
Points










ACH
Commitment
Control
DOA
IAA
Non-Sponsored
Projects
Person Data
PCBU/Activity ID
Project Numbering
Project Status
Control
Salary Cost
Transfer
2
Program Release Timeline

July 2007


July – August 2007


Systems Testing – two cycles for
each project
October 2007


Implementation of JET, Madison
APPO
Planned ECRT implementation
September 2007 – January 2008

Strategic Systems Integration
Testing – all teams
3
Current Challenges

Release of PeopleSoft
Maintenance Pack on August 30,
2007



Contains PeopleSoft Bundles 16
and 17 which are of interest to ATS
Timing is challenging because it
may impact the start of Strategic
Systems Integrated Testing
Sub-group to develop framework
for making decision on how to
proceed with the Maintenance
Pack
4
Risks and Action Plans


Risk identification sessions were
held for all major stakeholder
groups
Approximately 140 risks were
identified for the Program
Release



A number of the risks were
duplicates
Some of the risks were facts, not
risks
The risks were prioritized by
each team

Rated on probability and impact
5
Risks and Action Plans

Risks were grouped into categories:








Business Process
Constraints (Scope, Schedule, Resources,
etc.)
Coordination / Decision Making
Data Conversion
Performance / Operations
Testing
Training
Sub-groups of the Joint Steering
Committee are developing action
plans to address the highest risks
6
Communication Plan

One of the areas identified as a
risk to the Program Release was
Communication and
Organizational Change
Management


Identified the need for structured,
consistent communication about all
of the changes being introduced by
the Program Release
A sub-group of the Joint Steering
Committee was formed to
address this issue

Team includes Alice Gustafson and
Brian Rust
7
Communication Plan

A communication template was
developed and completed for
each Strategic Administrative
Project



Project name, description, target
audience, specific goals, timeline,
what’s in it for me, possible
surprises, and other
A communication plan has been
drafted
Links for the Program Release
and the projects will be place on
www.vc.wisc.edu
8
Strategic Systems Integration
Testing


Strategic Systems Integration
Testing (SSIT) is the integrated
testing of all projects within the
Program Release in a shared
environment
There are six iterations of testing
planned


We may have to modify this to
accommodate the need for two
month-end cycles
Testing will be conducted by the
project team members and
extended staff
9
SSIT Goals





All key functional business
requirements are met
System performs at acceptable
levels
Operational guidelines are in
place
Current SFS functionality is not
negatively impacted
Program Release meets “Go
Live” readiness criteria
10
Determining Readiness for
Go-Live


How do we determine whether or not
the Program Release is ready for
implementation?
Criteria to be used for determining
readiness:







Business Process Readiness
Testing – quality and completeness
Performance – online and batch
Defined Support Plan
User Readiness
Defined Security Plan
Documentation
11
Determining Readiness for
Go-Live



The Joint Project Managers are
adding further detail to the
criteria and more specific
measurements
The criteria will be reviewed by
the Joint Steering Committee
The goal is to have the criteria
for assessing readiness defined
prior to having to make a
decision
12