FM180 utilises Prince2 Methodology on all projects
The FM180 implementation and support team are all experienced and qualified Project Managers in the field of FM and ICT. We will totally manage your solution from the issue of order to project sign off, ensuring that all concerned are informed and engaged in the project.
We will require the client staff to adopt roles within the project such as project board members and user groups. This will ensure the success of stages throughout the project resulting in affiliated project signoff.
The first stage is to build and document the scope; this document is used and updated throughout the project incorporating the PID.
Effective and efficient FM is about knowing exactly the correct status of operations and services at any time. If you do not know what the status is then you are not in control.
Dr Brian Atkin FM Researcher
Overview of FM180 project delivery
PRINCE2 is a process-driven method of project management, and defines 8 distinct project stages containing 45 unique sub-processes. This approach is in contrast to adaptive or reactive methodologies such as Scrum or Agile.
1. Directing a Project (DP)
Directing a Project runs from the start of a project through its close out.
The project is directed by a Project Board which monitors it through reports and controls the project through authorization powers and ad hoc direction.
Initiation (starting the project off on the right foot); Stage boundaries (commitment of more resources after checking results so far);
Ad hoc direction (monitoring progress, providing advice and guidance, reacting to exception situations); Project closure (confirming the project outcome and controlled close)
2. Starting up a Project (SU)
Typically a very short stage, Starting up a Project is when a project’s reason and objective is defined, and to put in place the project team and manager.
Ensuring that the information required for the project team is available; Designing and appointing the Project Management Team; Creating the Initiation Stage Plan.
"Product-based" planning is a central to the PRINCE2 methodology. What is meant by product-based planning is that all the work products necessary to the successful completion of a project are identified and analysed. The purpose of this effort is to be able to estimate the effort, schedule and risk associated with each work product to more accurately arrive at an overall project plan.
Designing a plan; Defining and analysing products; Identifying activities and dependencies; Estimating; Scheduling; Analysing risks; Completing the plan.
4. Initiating a Project (IP)
This process proceeds naturally from the SU process. Project files are created, detailing the business case, project controls and overall plan.
These documents are used by the Project Board to authorise the launch of the project.
Agree whether or not there is sufficient justification to proceed with the project; Establish a stable management basis on which to proceed; Document and confirm that an acceptable Business Case exists for the project; Ensure a firm and accepted Foundation to the project prior to commencement of the work; Agree to the commitment of resources for the first stage of the project; Enable and encourage the Project Board to take ownership of the project; Provide the baseline for the decision-making processes required during the project’s life; Ensure that the investment of time and effort required by the project is made wisely, taking account of the risks to the project.
5. Managing Stage Boundaries (MSB)
In PRINCE2, projects are broken down into logically defined stages which progress in a linear fashion through to the completion of the project. The process of Managing Stage Boundaries enables the Project Board to determine if the project should be continued or not, and what steps to take if a stage has exceeded its tolerance levels.
Assure the Project Board that all deliverables planned in the current Stage Plan have been completed as defined; Provide the information needed for the Project Board to assess the continuing viability of the project; Provide the Project Board with information needed to approve the current stage’s completion and authorise the start of the next stage, together with its delegated tolerance level; Record any measurements or lessons which can help later stages of this project and/or other projects.
6. Controlling a Stage (CS)
It is in this stage that the efforts of the FM180 Project Manager are most in demand as the person who handles the day-to-day needs of the project.
Authorizing work to be carried out; Gathering progress information about that work; Watching for changes; Reviewing the situation; Reporting; Taking any necessary corrective action.
7. Managing Product Delivery (MP)
This process addresses the manner in which a work package is assigned, executed and delivered.
Making certain that work on products allocated to the team is effectively authorised and agreed accepting and checking Work Packages; Ensuring that work conforms to the requirements of interfaces identified in the Work Package; Ensuring that the work is done; Assessing work progress and forecasts regularly; Ensuring that completed products meet quality criteria; Obtaining approval for the completed products.
8. Closing a Project (CP)
Closing a Project is the process of wrapping up all activities involved with the project, such as preparing an end of project report, freeing up allocated resources, ensuring deliverables, etc.
Check the extent to which the objectives or aims set out in the Project Initiation Document (PID) have been met; Confirm the extent of the fulfilment of the Project Initiation Document (PID) and the Customer’s satisfaction with the deliverables; Obtain formal acceptance of the deliverables; Ensure to what extent all expected products have been handed over and accepted by the Customer; Confirm that maintenance and operation arrangements are in place (where appropriate); Make any recommendations for follow-on actions; Capture lessons resulting from the project and complete the Lessons Learned Report; Prepare an End Project Report; Notify the host organisation of the intention to disband the project organization and resources.