D471 - Consolidate Prototype Results
DEFINITION
Review the findings and conclusions from the iterative prototype sessions. Consider, in particular, what might need to be refined further in future iterations.
SUMMARY
- Compile the results of all of the prototype sessions conducted for the various business areas
- Identify and resolve conflicting recommendations
- Identify policy issues and formulate recommendations
- Ensure all issues related to business policies and processes resulting from prototype sessions are addressed.
PATH PLANNING GUIDANCE
This process is optional. It is normal practice in iterative prototyping.
DEPENDENCIES
Prerequisites (Finish-Finish):
- Set up, execute and manage prototyping workshops (D392)
- Design/prototype - implementation papers (D400/D450)
Dependent procedures (Finish-Finish):
- Review outstanding policy issues
RECEIVABLES
- Issues List
- Prototype Plan
- Prototype Procedures
- Prototype Session Results
- Prototype Results Summary
DELIVERABLES
- Prototype Results Summary
- Policy Decisions
TOOLS
- Issue/Resolution Log
DETAILED DESCRIPTION OF TASKS
The purpose of this process is to consolidate the results of the prototyping across business areas and sites and formulate remaining policy issues for core team resolution. The summary list of prototype results should include the following:
- summary of changes to current procedures
- summary of package options and configuration
- requests for modifications to the package modules or other software
- requests for additional custom software
- requests for changes to other systems
- pending policy issues and recommendations.
Detailed design decisions and process/procedure design for each prototyping topic will have been documented in the corresponding implementation papers during the prototyping process - see process D400/D450. A summary of results should be compiled for the prototyping and should be in sufficient detail to ensure effective follow-up on any outstanding issues and decisions resulting from the prototype process. The recommended format is textual with supporting diagrams.
This process will either be scheduled as a continuous activity or, at least, performed at the end of each iteration during an iterative prototyping approach. It is used in particular to identify aspects requiring further attention during subsequent prototyping or requiring reference to higher levels of management.
No comments :
Post a Comment