Your SlideShare is downloading. ×
Prince2 Methodology
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Prince2 Methodology

11,487
views

Published on


0 Comments
30 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
11,487
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
30
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • PRINCE2 Introduction V3.5 © 2008 Rational Management Pty Ltd
  • Transcript

    • 1. PRINCE2
    • 2. Contact Details Cell Phone: 250-507-4343 Victoria , BC Canada [email_address] 15 years healthcare specialist experience and practice management consulting. Utilizing extensive industry experience within medical equipments, IT healthcare (PACS/RIS/CIS & CVIS), pharma, biotech, clinical research and healthcare to execute and implement certain process as well as methodology into diverse operational roles at all organizational levels.
    • 3. PRINCE
      • PRINCE stands for P rojects IN C ontrolled E nvironments .
      • Designed to meet the Central Computer and Telecommunications Agency’s (CCTA) desire for better project management in Government IT departments.
    • 4. PRINCE2
      • PRINCE 2 is ‘son of PRINCE.’
      • Introduced in October 1996, it is targeted at any project.
      • It is incredibly laborious, and does not guarantee on-time, on-cost projects. But then, nothing does...
    • 5. The Approach
      • PRINCE 2 sets out a series of interlocking processes, which define inputs and outputs at different stages of the project.
      • The idea is to leave nothing to chance.
      • Designed to generalise PRINCE to apply to any project.
      • Onerous for small projects.
    • 6. A PRINCE2 Project
      • Solves a business need
      • Has a defined, unique set of products
      • Has corresponding activities to construct the products
      • Has the necessary resources
      • Has a finite lifespan
      • Sets up an organisational structure with defined responsibilities
    • 7. PRINCE Philosophy
      • Adds emphasis on:-
        • A planning method that derives the needed activities from the defined end products
        • Controls which deliver the desired quality, schedule and cost
        • A statement of the steps (or processes ) required to start, control, and conclude a project.
    • 8. PRINCE2 method
    • 9.
      • 7 principles
      • 7 themes
      • 7 processes
      • 8 duties and behaviours for the project board
      • 8 project roles
      • 2 guides
      • 2 detailed techniques
      • 33 referenced techniques
      • 26 management products
      • 6 performance targets
      • More than 20 pages of guidance on tailoring
      PRINCE2 method
    • 10. PRINCE2 Principles Business Justification A PRINCE2 project has continued business justification Learn from experience PRINCE2 project teams learn from previous experience (lessons are sought, recorded and acted upon throughout the life of the project) Roles & Responsibilities A PRINCE2 project has defined and agreed roles and responsibilities with an organisation structure that engages the business, user and supplier stakeholder interests Manage by Stages A PRINCE2 project is planned, monitored and controlled on a stage by stage basis Manage by Exception A PRINCE2 project has defined tolerances for each project objective to establish limits of delegated authority Product Focus A PRINCE2 project focuses on the definition and delivery of products, in particular their quality requirements Tailor PRINCE2 is tailored to suit the project’s size, environment, complexity, importance, capability and risk
    • 11. PRINCE2 Themes Business Case Establish mechanisms to judge whether the project is (and remains) desirable, viable and achievable as a means to support decision-making in its continued investment. Why? Organisation Define and establish the project’s structure of accountability and responsibilities. Who? Quality Define and implement the means by which the project will create and verify products that are fit-for-purpose. What? Plans Facilitate communication and control by defining the means of delivering the products Where and how by whom, and estimating the when and how much? Risk Identify, assess and control uncertainty, and as a result improve the ability of the project to succeed. What if? Change Identify, assess and control any potential and approved changes to baselined objectives. Only if? Progress Establish mechanisms to monitor and evaluate actual achievements with planned in order to provide a forecast for the project objectives, including its continued viability. Where are we now? Where are we going? Should we carry on?
    • 12. What are Key Themes?
      • Key Themes are:
        • aspects of project management that need to be continually addressed. They are not one off activities
        • And
        • aspects of project management that requires specific treatment for the PRINCE2 processes to be effective
    • 13. PRINCE2 Processes Processes Activities Recommended Actions “ The processes provide the lifecycle based list of project management activities”
    • 14. PRINCE2 Processes Starting Up a Project Directing a Project Managing a Stage Boundary Managing a Stage Boundary Closing a Project Initiating a Project Controlling a Stage Controlling a Stage Managing Product Delivery Managing Product Delivery Corporate or Programme Management Directing Managing Delivering Pre-project Initiation stage Subsequent delivery stage(s) Final delivery stage
    • 15. PRINCE2 Processes = process applies = process optional Pre-project Initiation Stage Stage 2, 3, etc Final Stage Stage Process Starting Up a Project Directing a Project Initiating a Project Controlling a Stage Managing Product Delivery Managing a Stage Boundary Closing a Project
    • 16. Role Descriptions
      • 8 roles
      • Role Descriptions oriented to product responsibilities
      • Role Descriptions include suggested competencies
      PRINCE2 organization structure
    • 17. Program Manager Project Managers Team Members Team Leaders
    • 18.
    • 19. Highest Authority and Represents the Interests Of All Parties For Duration of the Project These Are Roles and Not Positions And Can Be Combined or Expanded Project Board
    • 20.
      • Executive
      • Senior User
      • Senior Supplier
      Top Management Project
      • Mandate
      • Direction
      • Control
      Project Board
    • 21. Project Board Executive
      • Chairs the Project Board
      • Owns the Business Case
      • Ensure value for money
      • Conflict resolution
    • 22. Project Board Senior User(s)
      • Represent user interests
      • Large projects more than one
      • User specification
      • Monitor product delivery
    • 23. Project Board Senior Supplier(s))
      • Secure specialists
      • Build deliverables
      • Facilitate implementation
      • Procurements as required
    • 24.
      • Project Manager:
        • Reports to Project Board
        • Ensure delivery on time, on budget, quality and fit for purpose (specification)
      • Project Manager thus:
        • Plans
        • Lead and motivate
        • Relationship management and liaison
        • Assigns responsibility
    • 25. Project Environment Embedding Tailoring Done by the organisation to adopt PRINCE2 Done by the project team to adapt the method to the context of a specific project
      • Focus on:
      • process responsibility
      • scaling rules / guidance (e.g. score card)
      • Standards (templates, definitions)
      • training and development strategy
      • integration with business processes
      • tools
      • process assurance
      • learning lessons (corporately)
      • Focus on:
      • Adapting the themes (through the strategies and controls)
      • Incorporating specific terms/language
      • Revising the Product Descriptions for the management product s
      • Revising the role descriptions for the PRINCE2 project roles
      • Adjusting the processes to match the above
      Guidance in PRINCE2 Maturity Model and P3O Guidance in the Method
    • 26. Project Board Guidance
    • 27. Transition plans 30% of policies Design of financial statement Business requirements 70% of policies Policy Training Change management communications Learning strategy Communications strategy Learning framework Change management strategy Workload analysis Change Management Testing & systems integration Reports Data conversion tools Customization Prototype for key business areas Functional specs for key business areas IT Project Board Guidance
    • 28.
      • Less prescriptive
      • Greater emphasis on seeking lessons
      • Greater emphasis on product quality
      • Greater emphasis on Business Case an Benefits
      • Fewer management products – more easily scaled
      • More guidance on tailoring
      • Improved guidance on tolerances
      • More guidance for Project Board members
      • Revised approach to issues and changes
      • Revised terminology
      Project Board Guidance
    • 29. Tolerances Tolerance Areas Project level Tolerances Stage level Tolerances Work Package level Tolerances Product level Tolerances Time +/- amounts of time on target completion dates Project Plan Stage Plan Work Package NA Cost +/- amounts of planned budget Project Plan Stage Plan Work Package NA Scope Permitted variation of the scope of a project solution, e.g. MoSCoW prioritisation of requirements (‘ M ust have, S hould have, C ould have, W on’t have now’). Project Plan Stage Plan Work Package NA Risk Limit on the aggregated value of threats (e.g. expected monetary value to remain less than 10% of the plan’s budget); and Limit on any individual threat (e.g. any threat to operational service) Risk Management Strategy Stage Plan Work Package NA Quality Defining quality targets in terms of ranges, e.g. a product that weighs 300g +/- 10g Project Product Description NA NA Product Description Benefits Defining target benefits in terms of ranges, e.g. to achieve minimum cost savings of 5% per Branch, with an average of 7% across all branches Business Case NA NA NA
    • 30. Managing Successful Projects Using PRINCE2 - Structure
      • Introduction
      • Principles
      • Intro to Processes
      • Starting Up a Project
      • Directing a Project
      • Initiating a Project
      • Controlling a Stage
      • Managing Product Delivery
      • Managing a Stage Boundary
      • Closing a Project
      • Intro to Key Themes
      • Business Case
      • Organisation
      • Quality
      • Plans
      • Risk
      • Change
      • Progress
      • Project Environment
      • Wider Role of the Project Manager
      A – Product Descriptions B – Product/Process Map C – Roles D – Product Based Planning examples E – Checklists F - Trouble-shooting  
    • 31. Directing Successful Projects Using PRINCE2 - Structure
      • Introduction
      • PRINCE2 Overview
      • Project Board Duties and Behaviours
      • Directing a Project Activities
      • Starting Up a Project
      • Authorising Initiation
      • Authorising a Project
      • Authorising a Stage (or Exception) Plan
      • Giving Ad Hoc Direction
      • Confirming Project Closure
      • Reviewing Benefits
      A – Role Descriptions B – Product Descriptions C - Trouble-shooting D – Checklists  
    • 32. PRINCE2 Processes, Themes and Techniques Product Based Planning Technique Change Control Technique Quality Review Technique Business Case Change Control Quality Management of Risk Controls Plans Organisation Managing Product Delivery Planning Corporate or Programme Management Directing a Project Starting Up a Project Initiating a Project Controlling a Stage Managing Stage Boundaries Closing a Project
    • 33.
      • Business case
        • Contains: Reasons, Options considered; Benefits; Risks; Costs and Timescales; Investment appraisal
        • Sensitivity analysis: Good, Average, Poor
        • Need to (continue to) make sure that system is going to deliver a cost effective solution
      • Project Board
        • Consists of:
          • Executive: representing the Business: does the project meet the needs of the business overall
          • Senior user: representing the Users: will the project deliver a useable result (‘fit for purpose’)
          • Senior supplier: representing the Supplier(s): responsible for delivery of system
          • Project assurance: see below
        • Need to make sure that above three constituencies are adequately represented
        • Meets periodically review progress/risks/issues
      PRINCE2 Highlight
    • 34. PRINCE2 Highlight
      • Project manager (personal view)
        • Understands business and technology
        • Good communication skills
        • Experienced
        • Good communication skills
        • Efficient and well organised
        • Driven
        • Good at delegating
      • Project assurance
        • Independent assessment of the project
        • Understands business and technology
        • Experienced
    • 35. PRINCE2 Highlight
      • Project initiation document
        • What, why, who, how and when
        • Project definition: Objectives, Approach, Scope, Deliverables, Exclusions, Constraints, Interfaces, Assumptions
        • Project organisation structure: Team structure, Job descriptions
        • Communication plan
        • Quality plan
        • Project controls
        • Initial Business case
        • Initial Project plan
        • Initial Risk log
    • 36. PRINCE2 Highlight
      • Stage boundaries
        • Set points at which to review previous stage – confirm viability of project
        • Review business case
        • Plan next stage
      • Risk Log
        • Risk log:
          • Risk Description
          • Impact
          • Likelihood
          • Mitigation: Prevent, Reduce, Transfer, Accept, Provide contingency
          • Status
          • Outstanding actions
        • Brainstorm
        • Periodic reviews (e.g. Stage boundaries)
    • 37. PRINCE2 Highlight
      • Issue Log
        • Issues: Request for change; Off-specification; Question; Statement of concern
        • Capture:
          • Description
          • Priority
          • Impact analysis
          • Decision
    • 38. Product Based Planning
    • 39. Product Based Planning
    • 40. Product Based Planning
    • 41. Product Based Planning
    • 42. Product Based Planning
    • 43. Product Based Planning
    • 44. Product Based Planning
    • 45. Risk Management
    • 46. Benefits of PRINCE2
      • PRINCE2 can be applied to any type of project
      • It provides a common vocabulary and approach
      • PRINCE2 integrates easily with industry-specific models
      • The product focus clarifies for all parties what the project will deliver
      • PRINCE2 applies ‘management by exception’ providing efficient use of senior management time
      • It ensures a focus on the continuing viability of the project
      • PRINCE2 provides explicit understanding of roles and responsibilities so everyone can answer what is expected of them and what is expected of others
    • 47. Thank you for your attention! Any Questions?

    ×