Comprehensive Methodology

The following list is a summarized description of our preferred approach to implementing PeopleSoft' applications.  Note: the methodology described below uses the PeopleSoft Student application as the document's example.  However, this methodology applies to the Finance and HR applications as well.

 

I. The As Is Analysis - Where Are We Now and Where Are We Going (and How Fast)

Task: Determine exactly what functionality will be delivered - and when

Perform an As Is analysis, rank PeopleSoft functions according to the Needs Assessment priorities and reengineer client processes based on requirements, PS functionality, and the Needs Assessment Priorities.  Perform a fit-gap analysis using PS Process Maps as tools to find the right mix - NOT by comparing As-Is to PS "vanilla".  The final "aligned" process maps will be used as the sources for building the PeopleSoft Navigators, which will in turn determine individual panels and navigation paths.  Determine hardware and network configuration needs.  Identify key client resources and form module teams.

Deliverables: As-Is document (process flowcharts and narratives; legacy data descriptions), Fit-Gap document, Needs Assessment document, Phase I Project Plan, Hardware Requirements document

II. The Prototype - What You See Is What You're Going To Get (Almost)

Task: Prototype college policy into PS business processes.

Verify prototype at module level.  Determine how academic structure and calendar will be modeled in PS.  Integrate and verify processes at application level.  Complete conversion specifications.  Define interfaces.  Determine archiving and retrieval rules.  Begin developing training materials.  Complete User Manual (the design document).  Order hardware and security and monitoring software.  Document report and report distribution requirements.

Deliverables : Re-engineered process flowcharts and narratives, Enhanced Features document, User Manual, Set-up and Conversion Activities Task List, Business Process Maps and Navigators, Interface Specifications document, Client Signoff on prototype

III. Implementing Infrastructure - OK, Now Build It

Task: Setup and Load the Full Database

Install and configure hardware.  Build interfaces.  Convert legacy data to PeopleSoft.  Design and implement any infrastructure extensions.  Load tables.  Develop test scripts.  Begin performance tuning and system monitoring.  Identify users and user access requirements.  Set up panel access security for users.  Begin holding demos for users.  Determine how training will be done.

Deliverables : User Setup Checklists, Test Scripts

IV. Training - The Field Goes Live

Task: Bring it Up

Finalize and publish training materials.  Schedule classes.  Hold training and distribute staff userids.   Develop handouts for student web users and for faculty.  Distribute faculty Web ID's.

Deliverables : Training schedules, userids for all staff and web users, training materials, web handouts.

V. Turnover - Make the Client Self-Sufficient

Task:   End Phase I, plan for Phase II and III

Plan Phase II functionality and further automation with workflow.  Stabilize production environment.  Turnover patch and upgrade tasks to client if required.  Plan for Phase III reporting/query database.  Continue performance tuning and monitoring.    

Deliverables : High-level project plans for Phase II and III.

 

Contact IMS

About Us

News

White Papers