Organisation
Methodology Compliance
Methodology Stage | Standard Stage Sign-Off | Project Approach |
Planning | Approval by Project Manager, Project Sponsor and IS Applications Management Team (WIS) | Prepare brief / plans and submit to WIS |
Business Analysis | Peer Project Analysis Review (PPAR) |
|
System Analysis & Design | Peer Project Design Review (PPDR) | Review existing TAD for
Update as necessary, or prepare from template if none is available. |
Build | Peer Project Build Review (PPBR) | Check for and set up DEV and TEST environments as necessary for each application. Check synchronisation of environments with SVN Test the DEV and TEST environment is functioning correctly for each application Migrate......
.....to DEV Test and fix Student Counselling Services on DEV Migrate Student Counselling Services to TEST Test and fix PADS on DEV Bug fix Student Counselling Services from UAT Migrate PADS to TEST Test and fix External Examiners on DEV Bugfix PADS from UAT Migrate External Examiners to TEST Test and fix Organisational Hierarchy on DEV Bugfix External Examiners from UAT Migrate Organisational Hierarchy to TEST Test and fix Records Management on DEV Bugfix Organisational Hierarchy from UAT Migrate Records Management to TEST Bugfix Records Management from UAT
Create Implementation and Bamboo Plans for above applications
|
Integration | Peer Project Integration Review (PPIR) | Check applications and access to data |
Acceptance | Acceptance Sign-Off Review (ASOR) | Carry out UAT on
....and feed back results where developer will carry out re-work Production Management to create Deployment Checklist for each application. DevTech to re-deploy to TEST any applications that require re-work following UAT. |
Deployment | Deployment Sign-Off Review (DSOR) | Set up LIVE environments Create Request for Change form for each application. Create service alert 2 weeks prior to deployment to LIVE Copy each system to LIVE on specified date. Make necessary database changes to point to LIVE Testing of each application by business users DevTech to re-deploy application(s) following any re-work following UAT Release to LIVE |
Closure | Closure Review and Approval by Project Manager, Project Sponsor and IS Applications Management Team | Closure report and submit to WIS |
In order to handle multiple applications and migrations, the approach that will be taken is:
- Developer will go through the applications and test and fix each one in turn.
- Once the first application has been tested and fixed, it will be handed over to the business for testing.
- Developer will start testing and fixing second application, with space in their workload to fix any issues found during UAT in first application.
- First application will be released to LIVE when all UAT and bug fixes are complete.
- Developer will deploy the second application to TEST for UAT and begin working on third applicaiton with with space in their workload to fix any issues found during UAT in second application.
- Second application will be released to LIVE when all UAT and bug fixes are complete.
- Developer deploys third application to TEST for UAT and begins working on fourth application with with space in their workload to fix any issues found during UAT in third application.
- Process continues untill all application are in LIVE running Coldfusion 10 / 11.
Resources
Resource Estimates and Costs
Original Estimate | Revised Estimate | Reason for Revision |
IS Applications Staff Resource |
|
|
175 days |
|
|
Support Group Staff Resource |
|
|
N/A |
|
|
College Staff and Student Resource |
|
|
N/A |
|
|
Hardware Software and Service Costs |
|
|
None |
|
|
Post Project Resource Estimates
Original Estimate | Revised Estimate | Reason for Revision |
IS Applications Staff Resource |
|
|
|
|
|
Support Group Staff Resource |
|
|
|
|
|
College Staff and Student Resource |
|
|
|
|
|
Hardware Software and Service Costs |
|
|
|
|
|
Dedicated Project Team?
Out of Hours Working
Additional Information