The following terms briefly explain the major tasks to be performed during the project, and the general nature of work that will be performed by the team members.

Task Name & Description	Work Effort
Business Process Review- Pre Fit Sessions
Review current system and business processes. Review existing documentation on current business functions, policies and procedures, reports, interfaces, and data in current systems.	Provide insight to consultants on the nature and procedures of business processes. Ensure all critical processes are covered. Review any documents that are produced. Test proposed ChartField structure and ensure it will meet all of the organization’s needs.
Set Up Sessions – Fit Sessions
Based on knowledge gained during business process reviews, the consultants lead the project team members through the main issues that are involved in setting up the system. The decisions made during these sessions are used to setup the initial prototypes of the applications.	Team members must understand basic PeopleSoft architecture and design, and be able to relate them to the current methods of doing business. Major strategies and issues are identified and resolved so the initial prototype can be setup by the consultants.
Functional Testing
Using the base-line PeopleSoft system, test the organization’s business requirements. Using a list of key tasks, load control tables and application data, create scripts, test the scripts against the database, and document results. The resulting gaps identify business processes that may need to be modified.	This is the first opportunity for team members to look at particular pieces of the system in some depth. Time is spent on gaining more knowledge of how PeopleSoft functions as delivered, and understanding and researching how business processes can be accomplished. The consulting team provides generic test scripts, which usually do not require revisions.
Configuration / Fit Sessions
· Using information and knowledge gained during Set up and Functional Testing, Consultants and team members meet and discuss system functionality in more detail in order to resolve outstanding issues and recommend solutions for all existing gaps. · Configuration Document will be used to load production environment prior to going live and should reflect the most current decisions for company table entries. Review existing system and policy security requirements. Compare current security requirements with available security in PeopleSoft. Identify user types and define access to panels and processes. Setup and test security requirements in PeopleSoft.	· Project team members must have gained enough PeopleSoft knowledge during functional testing to be able to discuss gaps and issues in detail, and provide creative and workable suggestions. · Staff must have authority to make decisions and choose the best proposal. · Based on lead of consultant, staff will identify and document all company tables required to implement module. Identify required fields on company tables and enter values based on decisions made during the fit analysis sessions and module prototype. Document should be updated as tables entries are revised due to additional testing and prototyping.
Business Process Testing
· Decisions made and solutions proposed during Configuration Sessions are modeled and tested. The purpose of this task is to resolve all issues, close all gaps and ensure that real business solutions work in PeopleSoft. · Develop list of current business process examples. Business processes should cover full life cycle for the module being implemented. Gather data and/or documents that reflect list of processes. Prepare table to document results and issues that result from testing processes. Prepare documentation with expected results for verification against testing results. · If no feasible solution can be found using PeopleSoft delivered functionality, functional modifications must be designed.	· Project team members must test all proposed solutions. This involves detailed testing of various scenarios and variations of processes. Results are recorded and compared with expected outcome. Document and resolve business process issues that result from testing. Testing should model the production environment as much as possible. Testing is still focused within each application. · If necessary, staff will design functional modifications and customizations to panels, tables, processes, menus, reports, transactions, security, tolerances, edits, queries, reports, etc.
Interfaces and Conversion
· Besides setting up the default and option parameters, there is a substantial amount of financial and non-financial information stored in the system, such as vendors and last year’s receivables. · After going into production, data will be continue to be passed back and forth between PeopleSoft and foreign systems. Interfaces must be built to facilitate the flow of this information.	· The team must determine what data to convert, how far back the historical information will go, what must be archived, and resolve issues that arise from using new tables and data formats. · The project team will be responsible for the design, development and testing of production interfaces.
Integrated Testing
Whereas previous testing has been focused on the workings of each application, the emphasis is now on how well the modules talk to each other. Testing is performed to ensure data passed is accurate, complete, and correct.	Team members must gain knowledge beyond and outside of the module they have been primarily responsible for in order to ensure their data flows correctly to and from the other applications. Staff works closely with other module leads to resolve cross application issues.
User Acceptance Testing
All previous testing is done by the project team members, who have gained a lot of knowledge of how the system works. User acceptance testing is usually conducted by key staff representing a subset of the user community that have not participated heavily in the project up to this point. Their acceptance indicates to management that the entire package of training, business processes and integrated software is ready for production.	Project team members must set criteria for user acceptance testing, identify test participants, train users, and oversee testing activities. This ensures that knowledge transfer from consultants to staff is complete and team members are now the organization’s experts in their field.
Trouble Shooting
During testing, several issues will arise with the PeopleSoft software. Some are due to the way the system was configured, others are due to errors in the software. Team members will be shown methods for determining the cause of the problem, and a procedure will be developed for tracking and resolving every issue.	Functional staff must exercise the system heavily enough to ensure every transaction path and scenario works correctly. If not, techniques are learned and applied to determine the source of the problem. Technical staff will be involved in tracing software bugs, determining the cause of hard to find problems, and working directly with PeopleSoft to develop solutions.
Technical Support
Besides troubleshooting, the IS / IT staff will help provide technical solutions to functional problems. Using PeopleSoft tools, the technical team members will guide functional team members to the best alternatives for performing business processes.	Develop detailed technical design for modifications. Review detailed design with functional team and users requiring the modification. Program, install and unit test modifications, compare results with functional modification requirements. Conduct walk-through of modification with project team.