Organisation
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 | Peer Project Analysis Review (PPAR) | Complete |
System Analysis & Design | Peer Project Design Review (PPDR) | Agile |
Build | Peer Project Build Review (PPBR) | Agile with incremental product releases |
Integration | Peer Project Integration Review (PPIR) | Agile with incremental product releases |
Acceptance | Acceptance Sign-Off Review (ASOR) | Agile with incremental product releases |
Deployment | Deployment Sign-Off Review (DSOR) | Agile with incremental product releases |
Closure | Closure Review and Approval by Project Manager, Project Sponsor and IS Applications Management Team | Standard |
Resources
Resource Estimates
Original Estimate | Revised Estimate | Reason for Revision |
IS Applications Staff Resource | 1000 | Note 666 days will be spend in 2013/14 where the majority of the development will be completed for an initial site launch in July 2014. |
Support Group Staff Resource | 2110 | Note that 850 days will be spent in 2013/04 this covers core project team members and editors for testing and post migration tasks. |
College Staff and Student Resource | 450 | An estimated 50 days in 2013/14 |
Hardware Software and Service Costs | £107.7k | £35k for infrastructure £36k for Consultancy £36.7k for MYSQL licenses (3 years) |
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?
Yes, for further information please see additional information section below.
Out of Hours Working
No out of hours work is expected during the development. However depending on the migration process, some out of hours work maybe required.
Additional Information
Project Team
This project will be delivered using the Agile project methodology as developed by IS Applications.
A core team consisting on 3 developers, technical lead, business analyst and project manager will be delivered from IS Applications. UWP will deliver a product owner, UX designer, information architect, QA/tester and senior editors, graphic design representative to the core team as required during the development iterations. Other non-core members will be brought into the core team as and when the development and testing requires. It is planned to release a client at regular intervals though out the development phase. The prioritisation of the user stories will be undertaken by UWP lead by the product owner in collaboration with developers to advise on technical dependencies between user stories.
Development Iteration Structure
Each development iteration will have duration of 3 weeks with the core team members co-located for 3 days per week from Tuesday to Thursday. The plan for each iteration is shown below:
With co-location three days per week Tuesday to Thursday this willl give the following meeting plan:
| Iteration Day | Week Day | Meeting | Duration |
|---|---|---|---|
| 1 | Week 1 Tuesday |
|
|
| 2 | Week 1 Wednesday |
|
|
| 3 | Week 1 Thursday |
|
|
| 4 | Week 2 Tuesday |
|
|
| 5 | Week 2 Wednesday |
|
|
| 6 | Week 2 Thursday |
|
|
| 7 | Week 3 Tuesday |
|
|
| 8 | Week 3 Wednesday |
|
|
| 9 | Week 3 Thursday |
|
|
A review of the iteration structure will be held after iterations 1 and 2.