Home The Workings Help Site
Milestones Charter Strategies Mission & Scope
Previous TOC Next
charter 1 | charter 2 | charter 3 | charter 4 | charter 5
charter 6 | charter 7 | charter 8 | charter 9 | charter 10
Brandeis PEAK Project Charter
Project Plan
Administration
High Level Financials Project Plan
High Level HR/Payroll Project Plan
Administration
Issue Resolution Process
Standing Meetings
up

High Level Financials Project Plan
Click here to see the detailed project plan.
Click here to see our current progress through these milestones.
Milestone Target Date Deliverables
Initiate project Spring '98 Project started
Evaluate software Sum '99 Task complete
Complete needs assessment Sum '99 Task complete
Negotiate contract Spring '00 Signed contract
Initial planning meeting Sum '00 Planning workshop complete
Development system installed Sum '00 Development system in place
Define technical infrastructure Fall '00 Document complete
Up
Complete project plan Fall '00 Project plan to EVP/COO
Complete communications plan Fall '00 Publish to community
Communicate project information Fall '00 Deliver to campus community
Project team training - Phase I Fall '00 Task complete
Complete draft Chart of Accounts Fall '00 Publish to community
Complete fit/gap analysis Fall '00 Publish to community
Plan for HR System Win '00 Complete workshop
Complete conversion Strategy Win '00 Present to key users
Up
Production system installed Spring '01 Production system in place
Complete documentation Spring '00 Publish to community
Complete cut-over preparation Spring '00 Publish to community
Plan for Finance Phase II Spring '01 Complete one day workshop
Complete system test & reports Sum '01 Task complete
Review project funding Sum '01 Report to EVP/COO
Complete performance test Sum '01 Task complete
Complete end-user training Sum '01 Task complete
Complete cut-over Sum '01 PeopleSoft environment ready for production data
Central administrative departments deployment Sum '01 First rollout complete
Go live Sum '01 Yea!
Complete Phase I Fall '01 Task complete
up

High Level HR/Payroll Project Plan
Milestone Target Date Deliverables
Initiate project
 Summer '01
 Project started
Develop Time Entry Application
 Fall/Winter '02
 Task complete
Prepare Infrastructure
 Fall/Winter '02
 Task complete
Complete Needs Assessment
 Fall/Winter '02
 Task complete
Complete Conversion
 Fall/Winter '02
 Task complete
Setup Table Loading
 Fall/Winter '02
 Task complete
Complete Unit Testing
 Winter '02
 Task complete
Build Interfaces
 Winter '02
 Task complete
Build Process Reports
 Winter '02
 Completed reports
Complete Integration Testing
 Winter '02
Task complete
Up
Develop Procedures
 Winter '02
 Completed Procedures
Document Procedures
 Winter '02
 Publish to community
Complete Parallel Testing
 Winter '02
 Task complete
Setup User Security
 Winter '02
 Security in place
Document User Security
 Winter '02
 Publish to community
Complete Query and Reporting Approach for End Users
 Winter '02
 Publish to community
Complete Functional User Documentation
 Winter '02
 Publish to community
Complete Functional User Training
 Winter '02
 Task complete
Test System
 Winter '02
 Task complete
Complete Final Conversion
 Late Winter '02
 Task complete
Perform Cutover - Go-live
 Late Winter '02
 Task complete
Provide Post-production Support
 Spring '02
 Task complete
Complete Post Implementation Review
 Summer '02
 Publish to community
up

Project Administration
Issue Resolution Process

Definition

A project issue is:
a situation in which the software conflicts with the business process,
a roadblock to progress, or
a situation in which the software does not worK

Purpose

Project issues need to be tracked in order to:
ensure that progress is made towards task completion,
manage scope creep,
provide adequate notice of problem areas and adequate time to resolve problems,
allow for discussion by the implementation team while ensuring that date due is met,
communicate to everyone on the team issues that affect them.
Up

Process

Initially a project issue is:
identified,
classified, and
prioritized.

It will have:
responsibility assigned,
date due assigned,
area affected assigned,
status assigned, and
economic impact assessed.

Comments may be added for additional reference.

As issues are uncovered and recorded they will be reported during a project status meeting.
  1. Each new issue will be reported.
  2. All items still pending will have a progress status report.
  3. All newly closed items will be reported once and then will become inactive.
  4. Any new items that need to be added to the database will be reported and will be included as the first items to be covered the following meeting.
(See Appendix A for a sample Project Issue Log.)
up

Standing Meetings

Sponsor Meeting
Held on a monthly basis.

Steering Committee Meeting
Held on a bi-weekly or ad-hoc basis as necessary.
The agenda will include an overall project assessment and a review of the issue log. It will focus on significant issue

Community-At-Large
Faculty/Chair Meetings
Trustee Meetings
Senior Manager Meetings
Academic/Departmental Administrator Meetings
Up

User Community
Status Meeting
Working Sessions

Project Team
Status Meeting
Working Sessions

Finance Advisory Group
Status Meeting
Working Sessions

ITS Technical Team
Status Meeting
Working Sessions

HR Advisory Team
Status Meeting
Working Sessions

ITS Systems and Networks Team
Status Meeting
Working Sessions

Legacy System Support Team
Status Meeting
Working Sessions
up
Previous TOC Next
Home | The Workings | Overview | Help | Site
Search
Milestones | Project Charter | Strategies | Mission & Scope
 About us
bps site v1.0, last modified: 1/3/2002, 04:18 PM