Sample Project Flow Chart

September 14, 2017 | Author: iswkim | Category: Leadership, Leadership & Mentoring, Accountability, Technology, Production And Manufacturing
Share Embed Donate


Short Description

Download Sample Project Flow Chart...

Description

Eastleigh Borough Council Project Management Process

INITIATION

DEVELOPMENT / IMPLEMENTATION

(Click to access flowchart)

(Click to access flowchart)

Project Brief

Project Plan

CLOSURE (Click to access flowchart)

Project End Report

Post-Project Review Report

Depending on the type of project the tasks carried out during this stage can vary Further revision to Project Brief

Submit to Relevant Project / Programme Board

Approval to Proceed? YES YES Hold Project KickOff Meeting

Construction Project

IT Development Project

IT Development Project (External Supplier)

Feasibility Study

User Requirements

System Specification

Preliminary Design

Functional / Technical Design

Supplier Selection

Consultation System Build Detailed Design

System Test

Tender

User Test

Build

Procedures / Training

Project Initiation Document NO Further revision to PID

Further Submit to revision Relevant Project / to Programme Board Project End Report

Report Accepted?

Benefits Realisation Required?

Report Accepted?

YES YES

Benefits Realisation Review Report

YES

Procedures / Training

Go Live

Post-Project Review Required?

Go Live Submit to Relevant Project / Programme Board

NO Monitoring & Control Activities

Submit to Relevant Project / Programme Board

YES Approval to Proceed? Project Meetings

Highlight Reports

Risks & Issues Log

Change Control Log

Quality Control Log

Hold Post-Project Review

Report Accepted?

NO Project Cancelled / Abandoned

NO NO

Project Complete

Further revision to PPR

YES

Software Installation & Testing Software Customisation & Testing

Submit to Relevant Project / Programme Board

YES

Project Closed

Further revision to BRR

INITIATION This stage of the project starts from initial discussions and production of the Project Brief, and continues to the approval of the Project Initiation Document (PID) and Project Plan.

Project Brief

The first stage in the process is to complete a Project Brief. This is one of a set of standard templates designed to make project communication clearer.

Project Kick-Off Meeting

Once the Brief has been completed and agreed, this should be worked up by the Project Manager into a Project Initiation Document (PID).

The purpose of the Project Brief is to provide a foundation for the commencement of the project. It sets out high-level guidelines to the Project Manager on what the project is expected to achieve and gives authorisation to work up a Project Initiation Document. The Brief should be kept to a fairly high level of detail and not require a large effort to complete. A representative of the Programme Board, or the Project Sponsor (if one has already been identified) should normally complete this form. In reality this job can become the responsibility of the Project Manager.

When working up the PID, it is advisable for the Project Manager to seek assistance from those who would make up the project team, especially as timescales need to be determined and resource availability will be a key factor. This assistance can be sought via a project kick-off meeting; the purpose of which is to formally advise the relevant Units of the project and obtain the necessary resources. In determining the attendee list, it is advisable to approach a member of the Unit who has the required authority to assign resources to the project.

Click here to access the Project Brief Template

Click here to access the suggested agenda for the Project kick-off meeting

Project Initiation Document

This document defines the project more closely, by looking in detail at the project's objectives, why we are doing it and the benefits it will bring. As part of this process, more accurate estimates of costs and benefits should be established and analysed. The purpose of the PID is to fully define the terms of reference for the project. It should outline the business case, the scope and objectives, the roles and responsibilities of the key participants and the project plan for achieving the objectives. The document should contain all the information that the Project Manager requires to plan, organise and control the project.

Click here to access the Project Initiation Document Template

DEVELOPMENT / IMPLEMENTATION This stage includes all the work required once the PID has been approved to the actual handover, launch, "go live" or opening of the finished product, system or service.

Project Plan

Project Meetings

The project plan will have been developed as part of the PID stage. This forms the baseline for the project and should be kept up to date throughout the lifecycle of the project. The monitoring and control activities are in place to assist the identification and documentation of deviations to the plan.

Monitoring & Control Activities

Highlight Reports

Risks & Issues Logs

Change Control Log

Click here to access project plan templates

Quality Control Log

During the development stage of the project, it is advisable to hold regular meetings with the core Project Team and Project Board to ensure that all parties involved are kept up-to date. The meetings provide an opportunity to discuss progress against the plan and review risks, issues and changes that have been raised.

Click here to access project meeting agendas

Reporting has been set up to gather high-level project information, making it more widely available, and improving our knowledge and awareness of current and future projects. Highlight reports are used to document the project's progress to date and act as a mechanism for checking progress against plans.

Click here to access the highlight report template

A Risk is an event (positive or negative) that MAY occur; the likelihood of this happening and the impact if it were to occur should be recorded. An initial risk assessment will have been carried out at the PID stage. An Issue is an adverse event that HAS occurred and it's associated impact on the project. Both scenarios require careful management by the project team. They should be reviewed monthly, at a minimum, as part of the ongoing project control process.

Click here to access the risks & issues templates

Change management is intended to enable changes in requirements or design following approval of the PID; it is not intended to limit or prevent change, but provides a controlled process for changes to be considered. The change requestor should complete a Change Request Form for consideration and recording on the Change Request Log.

Click here to access the change control templates

Project deliverables are identified during the PID stage; it is necessary to ensure that as delivery progresses, they meet the required quality standard. The Quality Log should be used to record quality control activities.

Click here to access the quality control log template

CLOSURE Once the product, service or system is available, actions should be taken to signify that the project is complete and the project team can stand down.

Project End Report

A Project End Report should be completed to outline how well the project performed against its targets. It formally advises the project / programme boards that project work is complete and the project will be closed. The report should advise when the post-project review will be undertaken.

Post-Project Review

A Post Project Review should be undertaken to establish how well the project performed against its Project Initiation Document and find out if the expected benefits of the project have been realised. It is also an opportunity to review how the project was managed and identify recommendations for future projects. A post-project review workshop is the suggested method to ensure that key stakeholders are given the opportunity provide feedback.

Post-Project Review Report

This document is the result of the post-project review workshop. The key lessons learnt should be extracted from this report and stored in a shared location. PPRs should be reviewed on a regular basis, and common themes analysed so that the recommendations can be included in future guidance documentation.

Benefits Realisation Review Report

Depending on the nature of some projects, it might be necessary to allow a certain amount of time to pass before the benefits are expected to be achieved. In these instances it is appropriate to omit this section in the postproject review and carry out a benefits realisation review at a later date.

It is advisable to approach an independent facilitator to run the workshop and document results.

Click here to access the Project End Report Template

Click here to access the suggested agenda for the Post-Project Review workshop

Click here to access the Post-Project Review Report Template

Click here to access the Benefits Realisation Review Report Template

View more...

Comments

Copyright © 2017 KUPDF Inc.
SUPPORT KUPDF