Margo Visitacion Principal Analyst Forrester Research


Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Resource splitting can be avoided. In project-centric organizations, resources are allocated for a project and a project manager. The project manager “owns” the resource for the time required and is empowered to ensure commitment to the project without having that resource pulled off for another commitment. Once the project is completed, the team disbands and goes on to other projects. Project managers relay progress to project and/or program offices so that if there are delays, other projects that may be affected can be analyzed for alternatives.
  • Margo Visitacion Principal Analyst Forrester Research

    1. 1. March 31, 2004. Call in at 8:55 am Eastern Time Margo Visitacion Principal Analyst Forrester Research ForrTel: Implementing PRINCE 2 Project Management Methodology
    2. 2. PRINCE 2 — Pragmatic Application PRINCE 2 methodologies applies a pragmatic approach to project management
    3. 3. Agenda <ul><li>Why consider PRINCE 2? </li></ul><ul><li>Key success factors </li></ul><ul><li>How PRINCE 2 compares to other “methodologies” </li></ul>
    4. 4. Successful project management requires: Scope Planning Execution Control Closure Successful Delivery = Time + Communication + Quality Clear definition Strong leadership - the right resource - at the right time Building in quality by employing standards
    5. 5. PRINCE 2 — why is it a logical approach for IT? <ul><li>Organized approach to project management </li></ul><ul><li>Emphasizes business-oriented approach </li></ul><ul><li>Strong focus on defined teams and processes </li></ul><ul><li>Emphasized collaboration </li></ul>
    6. 6. PRINCE 2: good project management requires: <ul><li>A controlled and organized start, middle and end </li></ul><ul><li>Regular reviews of progress against plan and against the Business Case </li></ul><ul><li>Flexible decision points </li></ul><ul><li>Automatic management control of any deviations from the plan </li></ul><ul><li>The involvement of management and stakeholders at the right time and place during the project </li></ul><ul><li>Good communication channels between the project, project management, and the rest of the organization </li></ul>
    7. 7. PRINCE 2 — critical success factors Roles Reality Check Process <ul><li>Clear role definition </li></ul><ul><li>Visible executive support </li></ul><ul><li>Go beyond documentation — </li></ul><ul><ul><li>Get training </li></ul></ul><ul><li>Set governance processes up at project offset — refine them for the enterprise </li></ul><ul><li>Get business active and involved </li></ul><ul><li>Respect the schedule </li></ul><ul><li>Cross training is critical </li></ul><ul><li>Be pragmatic </li></ul>
    8. 8. Key success factor #1 — roles <ul><li>Pick champions with a cross-section of talent </li></ul><ul><li>Roles must be clearly defined — draw lines of authority AND responsibility </li></ul><ul><li>Form a pilot team to develop and implement — retain them as mentors </li></ul>
    9. 9. Key success factor #2 — process <ul><li>Pilot PRINCE 2 — small to medium to start </li></ul><ul><li>Measure results </li></ul><ul><li>Executive sponsorship </li></ul><ul><li>Utilize the framework </li></ul><ul><ul><li>Make it scalable </li></ul></ul><ul><ul><li>Develop thresholds </li></ul></ul><ul><ul><li>Specialized measurement criteria </li></ul></ul>
    10. 10. Key success factor #3 — reality check <ul><li>Respect the schedule </li></ul><ul><ul><li>Process is critical but so are delivery dates </li></ul></ul><ul><li>Visible accountability </li></ul><ul><ul><li>Project manager of process = project schedule controller </li></ul></ul><ul><li>Flexibility is critical </li></ul><ul><ul><li>Adaptation is okay </li></ul></ul>
    11. 11. Process/Methodology Comparison: PRINCE2 and CMM <ul><li>Framework of practices </li></ul><ul><li>Management focus </li></ul><ul><li>Emphasizes: </li></ul><ul><ul><li>Change control </li></ul></ul><ul><ul><li>Issue Mgmt </li></ul></ul><ul><ul><li>Risk Mgmt </li></ul></ul><ul><ul><li>Project Mgmt </li></ul></ul><ul><ul><li>Repeatable Processes </li></ul></ul><ul><ul><li>Documentation </li></ul></ul><ul><ul><li>Workflow </li></ul></ul><ul><ul><li>Schedule independent </li></ul></ul>Similar practices = similar challenges <ul><li>Challenges </li></ul><ul><li>Perception: </li></ul><ul><ul><li>Bureaucracy </li></ul></ul><ul><ul><li>Misinterpretation — tendency to over-implement </li></ul></ul><ul><ul><li>Inability to apply appropriate scale </li></ul></ul><ul><ul><li>Professional rigidity </li></ul></ul>
    12. 12. Process/methodology comparison: PRINCE2 and PMBOK PRINCE2 ≠ PMBOK <ul><li>PMBOK </li></ul><ul><li>Singular focus </li></ul><ul><li>Hierarchical model </li></ul><ul><li>What </li></ul><ul><li>Schedule driven </li></ul><ul><li>Success </li></ul><ul><li>Measurements </li></ul><ul><li>PRINCE2 </li></ul><ul><li>Team-driven </li></ul><ul><li>Collaborative model </li></ul><ul><li>How </li></ul><ul><li>Schedule independent </li></ul><ul><li>Quality </li></ul><ul><li>Measurements </li></ul>
    13. 13. Recommendations for process improvement implementation <ul><li>Primary success factor — Cultural adoption </li></ul><ul><ul><li>Design a phased implementation; pilots are critical to develop next steps and lessons learned </li></ul></ul><ul><ul><li>Educate management with metrics — good AND bad </li></ul></ul><ul><ul><li>Make sure the executive board has real executives </li></ul></ul><ul><ul><li>The project manager and the executive sponsor own the project </li></ul></ul><ul><ul><li>Cross-train organization to better manage possible cultural missteps </li></ul></ul><ul><ul><li>Mind the schedule; process improvement is useless if the project misses its date </li></ul></ul>
    14. 14. Thank you Margo Visitacion [email_address] Entire contents © 2004 Forrester Research, Inc. All rights reserved.