2.3 Product Walk Through (PWT)

This topic provides information about the Product Walk Through (PWT).

Product Walk Through (PWT)

This is an exercise where the end users evaluate the features of the system with reference to their business processes. As mentioned earlier, this exercise is normally conducted before implementation so that the client would be able to identify whether and how the product fits into their requirement. However, there could be situations where the PWT is coupled with an implementation and would normally be the first step in the implementation cycle.

Evaluation
The evaluation would normally focus on
  • broad processes existing in the system
  • features offered under processes and the functions performed
  • work flows in the system
  • Performance issues
Users
The users involved in the PWT would include key personnel from various functions of the organization. They would include:
  • Users from the Agency branches who are the organization’s front office interacting with clients
  • Users from the head office who perform the Fund Management function
  • IT personnel
  • Top management
Plan

The plan is broken up into a set of logical days with a set of features being covered in a logical day. The features covered flows in a logical manner so as to cover all operations in a normal business cycle. A separate database is created for the PWT exercise as a part of the installation milestone. On completion of the PWT, the PWT database can be utilized for the User Training exercise.

A day in the PWT would normally go as follows:

Prerequisites
  • Before starting the PWT, the Oracle Financial Services Software Limited consultant should discuss, with the client Project Manager, and work out the structure of the exercise for a day. The activities for a day would include
    • Demonstration of features
    • Discussions which could be along with the demonstration or a separate session
    • Preparation of minutes of discussions
    • Review of minutes of discussions and incorporation of changes where required.
PWT Execution
Based on the availability of the users, the time for each of the above activities can be worked out and the same communicated to all participants. The above can form part of the PWT plan which would be communicated to the client during the pre-implementation phase. This would help the client plan for the for the time of users during this exercise
  • The Oracle Financial Services Software Limited consultant handling the PWT would explain the working of the features as per the plan. Data, from business situations of the client, would be fed into the system and the results evaluated by the users.
  • Discussions on the various features evaluated would occur either as the PWT goes on or a designated time could be fixed for discussions.
  • Time should be kept aside towards the end of the day to document the discussions that occurred during the day in the form of minutes of meetings. The responsibility for preparation of the minutes lies with the Oracle Financial Services Software Limited consultants. These minutes should be exchanged with the Project Manager from the client side for review. Any difference should be discussed and the minutes duly modified. The final agreed document should be signed off and copies exchanged. Preparation of the minutes of meetings every day is extremely important and these minutes will form part of the PWT Report.
Deliverables
The deliverables at the end of the Product Walk Through exercise include:
  • a PWT Report
  • a PWT Sign off from the client
PWT Report
The PWT Report is a document resulting from the evaluation exercise during the PWT. It should contain:
  • The gaps identified during the PWT. A gap is any feature required by the client which is either not available in the system or available but inadequate. The gaps should be explained in as much detail as possible as this forms the requirements specifications for building the gap into the product. Illustrations, worked examples, supporting documents which help understand the requirement should be incorporated into the document. A well detailed gap document helps in the follow up exercises after the PWT which include:
    • Analysis of impact of the gaps on design of system
    • Estimation of effort involved to build the gaps into the system
    • Building design specifications for the gaps
    • Information on the operational work flow existing in the business operations of the client
    • The organization structure of the client organization
    • Any other information which would help in understanding the business processes of the client
Organization of PWT Report
The organization of the PWT Report should follow certain guidelines on:
  • The structure of the document in terms of the chapters to be incorporated
  • Numbering conventions for chapters and sections under chapters
  • Format for the sign off ( sample available in the Annexure H )
  • Annexures containing minutes of meetings, supporting documents, etc.

A look at any existing PWT Reports would give an idea on the organization of the same.

Controls
  • In a situation where the PWT exercise is not part of an implementation, the team should ensure that all software installed and databases created are deleted before leaving the client site. Under no circumstances should any component of the software be left at the client site after the Oracle Financial Services Software Limited team has left. Where the PWT is part of the implementation, the PWT database can be utilized for a subsequent exercise such as user training exercise, UAT, etc.

Parent topic: Implementation Tasks