PRINCE2 Foundation

Project characteristics
1. Change
2. Temporary
3. Cross-functional
4. Unique
5. Uncertainty
Six variables involved in a project
1. Costs
2. Timescales
3. Quality
4. Scope
5. Risk
6. Benefits
Four integrated elements
1. Principles
2. Themes
3. Processes
4. Tailoring PRINCE2 to the project environment
Principles of PRINCE2
1. Continued business justification
2. Learn from experience
3. Defined roles and responsibilities
4. Manage by stages
5. Manage by exception
6. Focus on products
7. Tailor to suit the project environment
Themes of PRINCE2
1. Business Case
2. Organisation
3. Quality
4. Plans
5. Risk
6. Change
7. Progress
Purpose of a theme: Business Case
To establish the mechanisms to judge whether the project is (and remains) desirable, viable and achievable as a means to support decision making in its (continued) investment.
Contents of a Business Case
1. An executive summary
2. Reasons
3. Business options
4. Expected benefits
5. Expected dis-benefits
6. Timescale
7. Costs
8. Investment appraisal
9. Major risks
Purpose of a theme: Organisation
To define and establish the project's structure of accountability and responsibilities (the who?).
Four levels of management within the project management structure
1. Corporate or programme management
2. Directing - Project Board
3. Managing - Project Manager
4. Delivering - Team Manager
Key characteristics of a good Project Board
1. Authority
2. Credibility
3. Ability to delegate
4. Availability
Purpose of a theme: Quality
To define and implement the means by which the project will create and verify products that are fit for purpose.
Quality planning comprises:
- Understanding the customer's quality expectations
- Defining the project's acceptance criteria
- Documenting the customer's quality expectations and the project's acceptance criteria in the Project Product Description
- Formulating a Quality Management Strategy
- Writing clear Product Descriptions containing quality criteria, quality tolerances, quality method and quality responsibilities
- Setting up the quality register
The Project Product Description includes:
- The overall purpose of the product
- Its composition
- The customer's quality expectations
- Acceptance criteria, method and responsibilities
- Project-level quality tolerance
Purpose of a process: Starting up a Project (SU)
To ensure that the prerequisites for Initiating a Project are in place by answering the question: do we have a viable and worthwhile project?
Objective of a process: Starting up a Project (SU)
1. There is business justification for initiating the project
2. All the necessary authorities exist for initiating the project
3. Sufficient information is available to define and confirm the scope of the project (Project Brief)
4. Various delivery options are evaluated and a project approach selected
5. Individuals are appointed who will undertake the work required in IP/in the project
6. Work required for IP is planned (documented in a Stage Plan)
7. Time isn't wasted initiating a project based on unsound assumptions regarding the project's scope, timescales, acceptance criteria and constraints.
Activities of a process: Starting a Project
1. Appoint the Executive and the Project Manager
2. Capture previous lessons
3. Design and appoint the project management team
4. Prepare the Outline Business Case
5. Select the project approach and assemble the Project Brief
6. Plan the initiation stage
Products of a process: Starting a Project
1. Project Brief
2. Daily log
3. Lessons log
4. Outline Business Case
5. Project Product Description
6. Stage Plan
Activities of a process: Controlling a Stage
1. Authorise Work Packages
2. Review Work Package Status
3. Receive completed work packages
4. Review stage status
5. Report Highlights
6. Capture and examine Issues and Risks
7. Escalate issues and risks
8. Take corrective action
Products of a process: Controlling a Stage
Highlight Reports
Work Packages
Issue Reports
Exception Reports
Configuration Item Record
(Used: Daily Log, Issue Register, Lesson Log, Quality Register, Risk Register and Stage Plan)
Activities of a process: Managing Product Delivery (MP)
1. Accept a Work Package
2. Execute a Work Package
3. Deliver a Work Package
Products of a process: Managing Product Delivery (MP)
Checkpoint reports (created)
Team Plans (created/updated)
Configuration Item Records (Updated)
Quality Register (Updated)
Activities of a process: Managing a Stage Boundary
1. Plan the next stage
2. Produce an exception plan
3. Update the project plan
4. Update the business case
5. Report stage end
Products of a process: Managing a Stage Boundary
1. Stage Plan
2. Exception Plan
3. Project Plan (updated)
4. Business Case (updated)
5. Benefits review plan (updated)
6. Configuration item records (updated)
7. Quality register
8. End Stage Report
Activities of a process: Closing a Project
1. Prepare planned closure
2. Prepare premature closure
3. Hand over products
4. Evaluate the project
5. Recommend project closure
Products of a process: Closing a Project
1. Product Status Account
2. End Project Report
3. Project Plan (update)
4. Risk log (update)
5. Issues log (update)
6. Benefits Review Plan (update)
7. Lessons Report
8. Communication Management Strategy (reviewed)
9. Draft project closure report