Revision day 1 Flashcards
A project manager…
Is responsible and accountable for successful delivery of the project outputs
Directs and motivates the project team
Manages relationships with stakeholders (especially the Sponsor)
Produces and takes ownership of the project management plan
Example project team structure
Programme
project board
project manager
team leaders with governance and project support
Project Sponsor responsibilities
Primary owner of the project on behalf
of the business (should have the
relevant level of business authority)
Accountable for the investment in the
project and the resultant benefit
delivery
Produces and ‘owns’ the Business Case
Comparison of Responsibilities… project sponsor
Strategic management
Project viewpoint
Project assurance
Benefit assurance
Benefits realisation
Business effectiveness
Comparison of Responsibilities… Project Manager
Tactical management
Stage viewpoint
Product assurance
Product delivery
Day-to-day control
Project efficiency
User
Involved in developing the detailed requirements
Approve the products/deliverables
Define and agree the acceptance criteria
Team Leaders
Specialists
Internal and/or external to the organisation
Do the work
Report to, and take direction from, the project manager
Steering Group/Project Board
Provides strategic direction and guidance
Ensures cross-functional representation from the business
Chaired by the sponsor
Includes representatives from:
Users
Suppliers
Key stakeholder groups
Resolves escalated risks and issues that the project manager and sponsor cannot resolve
‘Go/No Go’ decisions at end of each phase of the life cycle, on behalf of the business
Knowledge management
The systematic management of information and learning. It turns personal information and experience into collective knowledge that can be widely shared throughout an organisation and a profession
Information Management:
The collection, storage, curation, dissemination, archiving and destruction of documents, images, drawings, and other sources of information
Reviews
can be triggered by events (e.g. the delivery of a product or completion of a stage) or by the passage of time (e.g. quarterly or six-monthly reviews)
The frequency, conduct, and scheduling of reviews is set out in the quality management plan
Review to be effective it should include a
Controlled attendance with attendees who will add value
Defined agenda, including the findings of previous reviews
Report with clear actions and owners
Different Types of Reviews
Project evaluation reviews
Gate reviews
Audits
Peer reviews
Post-project reviews
Benefits realisation reviews
Project Evaluation Reviews
Planned by the project manager
In addition to ongoing monitoring and control
Project reviewed mainly against the PMP, but also the business case
Aims of project evaluation review
Evaluate the project management processes
Establish lessons learned and actions arising
Raise concerns and agree corrective actions
Review likely technical success
Decision Gates/Gate Review
Undertaken between phases that are used to review and confirm viability of work compared to business case
Determines whether the project should proceed – ‘go or no-go’
Decision point for senior management regarding whether to continue the investment
Opportunity to request approval for authorities
Decision gate review based on
Outputs achieved so far
Requirements for the next stage/phase
Key Decisions to be made
Is the Business Case still viable?
Audits
Undertaken by a group outside the project team
Could be:
Project office
Internal audit
Third-party organisation
The purpose is to provide an objective evaluation of the project
Peer review
A peer review is really an informal audit. It’s a chance for someone else to cast their eyes over your progress and approach, and provide you their feedback
the goal of all peer review processes is to verify whether the work satisfies the specifications for review, identify any deviations from the standards, and provide suggestions for improvements
Aims of a post project review
Evaluating the effectiveness of project management
Comparing what was actually delivered against the original requirements
Identifying lessons learned
Assessing performance, e.g. comparing the planned schedule against the actual schedule
Capturing stakeholders’ opinion of how the project was delivered
Disseminating findings
Benefits realisation review
Undertaken after a period of business-as-usual
To establish the project benefits have been, or are being, realised
Responsibility of the sponsor
Further benefit reviews may be needed, perhaps a series
Benefits of conducting reviews … think about types of reviews alongside benefits
- Lessons learnt throughout the project life cycle, not just at the end
- Reassurance for the business and senior management that projects are being run in a structured manner, following agreed methods and processes
- Enables project performance to be measured and assessed
- Aids comparison of projects
- Encourages PMs and their teams to reflect on the project status and objectively review their work
- Motivation – opportunities to recognise individual or team performance
- Forms part of an ‘audit trail’ for a project
Reasons for early closure of a project
Planned objectives are unachievable – the project cannot fulfil its purpose
No longer a viable business case
When the cost of time and resources exceeds the benefit of the outcomes i.e. no longer evidence to support sufficient value
Wider organisational objectives take priority
Why is early closure a positive?
‘failing fast’ is often implemented into the early stages of planning to prepare for such decisions and their impact on resources, stakeholders, and communication
Better utilisation of resources rather than wasting them on devalued objectives
Reviews and Decision Gates provide the best opportunity to ensure the project is on track and still viable, if this leads to project closure, they have been conducted successfully