Organisation
Project Methodology
Overview
We propose to work to a 'Fixed Cost against Prioritised Scope' proces. Previous examples of this working methodology can be found within the COM005 project.
Therefore a fixed budget from the programme will be sought. The project team will then work through the deliverables using basic MSCW prioritisation analysis. The 'Must ' haves will initially be limited to 60% of the project deliverables and then there will be weekly adjustments to the priorities, estimations and potentially scope as the project moves forward with its delivery.
The initial 'Must' haves will form the basis of our milestones for WIS planning approval.
Day to Day Running
We agreed to the following:
- Weekly meeting to include a core representation of the Project Team (max one from each department)
- At these meetings we report on work completed then priortise tasks for the forthcoming week and beyond.
- The project will retain 'thresholds' for Analysis, Delivery and Closure. Leaving the remaing days in a tightly controlled pot from which we take out deliverables through BUILD, INTEGRATION, and ACCEPTANCE.
- The project will use the JIRA tool alonside Hip Chat and the Projects Website.
- Weekly meetings are reported to the wider project group through a weekly meeting document (an example taken from COM005 below)
- In essence the weekly review gives the Sponsor and departmental leads easy access to project status and ultimately quick control of scope for satistactory delivery of the project.
Link to Image of Example Report
Work/Task Breakdown
Each task will go though the following process
- BRD As the budget is now capped at 50 days there is not enough time to a full BRD. Will instead be specifications drawn up by Service Management
- Estimate Work Required and Schedule
- Development with Implementation Plan
- Create and Document UAT TEST scenarios
- Document a TEST Plan
- UAT
- Deploy to LIVE
Resources Skills and Cost
This project will run using a fixed budget, variable scope methodology where regular estimations are required and approved by the project sponsor.
Effort is then allocated out from the central pot.
