Project Processes

The Project lifecycle is broken down into four main processes and below describes the steps required to successfully run a project from inception to close. Please note that these steps should be reviewed and tailored as required to meet each project.

Project Initiation

1. Assign Project Number & Code and update Project Register
2. Create Project SharePoint Site
3. Create and agree Project Brief with Sponsor

1.  Define the business objectives of the project with Project Sponsor
2.  Investigate different options available (including the do nothing option)
3.  Investigate initial costs for project
4.  Create and populate first draft of Risk Register
5.  Create initial Stakeholder map
6.  Create Project Initiation Document (owned by Project Sponsor)

PROJECT INITIATION DOCUMENT REVIEWED BY PROJECT BOARD
AGREEMENT TO PROCEED BY PROJECT BOARD

Project Planning

1.  Project Planning Meeting
2.  Produce detailed Project Plan and MS Project Plan (Gantt Chart)
3.  Create detailed Project Cost and Delivery Date
4.  Update Risk Register taking account of Risk Appetite
5. Determine if Privacy Impact Assessment (PIA)​ is required and if so complete and return to Governance
6.  Review and Define post-project operational requirements
7.  Update Project Pipeline with timelines and resources required
8.  Update Project Initiation Document with new information

RESOURCES REQUIRED AGREED BY RESOURCE MANAGER
PROJECT INITIATION DOCUMENT AND PROJECT PLAN REVEIWED BY PROJECT BOARD
AGREEMENT TO PROCEED BY PROJECT BOARD

Project Implementation/ Control

1.  Kick off meeting with full team
2.  Organise Regular Project meetings
3.  Baseline Gantt chart and monitor for slippage
4.  Input time against tasks and monitor
5.  Monitor costs incurred and track baseline versus actual
6.  Produce regular Project Status report
7.  Create Test Plan
8.  Track and agree changes using standard change process and change log
9.  Develop Training documentation and operational document as required
10. Monitor and manage risks and escalate risks and issues to Project Board as requ​ired
11. Update Business Case as required
12. Train users on new functionality
13. Complete System Testing
14. Action User Acceptance Test Plan and record results
15. Review results and re-test and re-work areas as required

Recommendation of 1 day User Acceptance Testing per week of development
PROJECT BOARD REVIEW TEST RESULTS AND AGREE TO GO-LIVE

Go-live/Handover

1. Monitor Product produced
2. Project Team resolves issues as they arise from users
3. Complete handover documentation
4. Average of 5 days post go-live support (dependant on size and complexity of project)

Project Closure

1. Post Project Review meeting with team
2. Produce final Risk Register and handover open risks to Operations
3. Produce Project Completion report - this will also include Lessons Learned and Final Budget
4. Provide Operational Handover document
5. Complete Project File
6. Update Project Register 

PROJECT BOARD REVIEW PROJECT CLOSE REPORT AND AGREE TO CLOSE PROJECT