Background
Scope, Objectives and Deliverables
Benefits
Success Criteria
UAT Scenarios from Business Requirements Document
User testing should be based on the test scenarios and acceptance criteria identified in the Business Requirement Document. Any deviation from these scenarios should be noted here.
BRD Ref | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome (PASS / FAIL) |
Approval Record
Check List Item | Quality Criteria | Complete Y/N | Reviewed By |
Category and Billing Arrangements |
| Y | Miles MacCalman Dave Berry, Iain Fiddes, Stefan Kaempf |
Definition
Role | Unit | Name |
Project Manager |
|
|
Project Sponsor |
|
|
Business Analyst (Owner) |
|
|
Systems Analyst Designer |
|
|
Technical Architect |
|
|
Methodology Compliance
Methodology Stage | Standard Stage Sign-Off | Project Approach |
Planning | Approval by Project Manager, Project Sponsor and IS Applications Management Team (WIS) | Standard |
Business Analysis |
Cost Benefit Analysis
Five Year Costs
Tangible Costs Summary | ||||
5 Year Summary | IT Services i.e. IS staff, hardware, software and services | Support Group Staff Costs | College Staff Costs | Total |
Executive Summary
In spring 2011, improvements to the speed of the Polopoly interface were being investigated.
The upgrade project was one avenue being explored, but another was to change the way the underlying code worked so that Ajax could be introduced to speed up interface response times.
Mairi Fraser worked with Ana Heyn under our support budget into work through these enhancements and roll them out onto the TEST server. Following an initial round of UAT, a number of bugs were discovered that needed further investigation.