Organisation
Work/Task Breakdown
For the projects that are following an iterative delivery focussed approach, the following will be the steps for the work/task breakdown, user stories will be documented in the Agile jira project to be opened.
- Document requirements with the business, to include business and system changes
- Produce a prioritised list of system changes with estimates
- Define iteration/release cycle at the foundation stage
- Iteration build including user testing and sign off
- Define and prepare training requirements, communication with users and handover to Operations
- Track the enhancement's achievements, issues, and next steps on the monthly project report.
Resources Skills and Cost
The following is the sort of information that should be provided for this section.
All resource requirement within Core SSP so there is no current requirement for resource from the wider IS apart from the go-live which will be treated in the same way as the small scale enhancements.
Core Agile Project Team 2 x Developers (Web/E-Vision)
Dev Tech for deployment of PHP
Apps Management for Brief review, SITS deployment, handover
1 x Business Analyst / Project Manager 0.5 x Tester
Allocation for 14/15 is 102 IS Apps days and 50d SSP BPE.
The 102 day budget is split over financial years as follows
- delivery will be done in 14/15: 96 days
- post live support/maintenance/closure in 15/16: 6 days
Estimated IS Apps Days | Medium- 102d 2 developers will be assigned to this project, working from April to July. Expected 96d Dev Tech/ deployment IS Apps resources 4d Programme Manager/IS Governance 2d |
Estimated Business Partner Days | Small (50) SSP will provide the BA, PM and testing resource Student Systems Operations will be involved during whole project with business lead, and will take part into testing, deployments and handover as a service |
Estimated Confidence | Reasonably confident to be able to deliver the 1st deliverable for PT. The other deliverable will be determined after the estimation done at the foundation stage. Statement from Greg Tyler: The estimated time should be suitable to comfortably complete the two “must have” deliverables, and to also leave us ample time to work on the lower priority stories. |
Estimation References and Assumptions | The estimation assumes that the high-priority stories will not change significantly in scope, and that no other work will take priority away from them. We have taken into account the mixture of skills on the project team: One developer has had significant exposure to the system but the rest of the team are relatively new to it from a technical perspective. There is other ongoing work that the project’s developers will be engaged in over coming months. It is expected that this will leave suitable time to work on this project, but there is always a risk that the balance of work may have to shift if the scope of that additional work changes. Greg Tyler is the lead developer and has worked on the previous 2 Path projects. |