
Executive Guide to Directing Projects
Beschreibung
Weitere Details
Weitere Ausgaben
Inhalt
- The Executive Guide to Directing Projects:within a PRINCE2TM and MSP® Environment
- Contents
- List of figures
- List of tables
- Foreword
- Acknowledgements
- 1 Introduction
- 1.1 The purpose of this guide
- 1.2 Using the guide
- 1.3 About projects
- Figure 1.1 The place of the project in the product lifecycle
- 1.4 Portfolios and programmes
- Figure 1.2 The portfolio, programme and project hierarchy
- 1.5 What is PRINCE2?
- Figure 1.3 Generic project management with specific specialist application
- 2 The role of senior management in PRINCE2
- 2.1 The PRINCE2 organization
- Figure 2.1 The PRINCE2 project management organization
- 2.2 Project Board composition
- Figure 2.2 The three stakeholder interests in a project
- 2.2.1 The Executive
- 2.2.2 The Senior User
- 2.2.3 The Senior Supplier
- 3 Project Board duties and behaviours
- 3.1 Be accountable for the project
- 3.2 Provide unified direction
- 3.3 Delegate effectively
- 3.3.1 The 'stage contract'
- 3.3.2 Exceptions and escalation
- Figure 3.1 Example of stage tolerances
- 3.4 Facilitate cross-functional integration
- 3.5 Commit resources
- 3.6 Ensure effective decision making
- 3.6.1 Progress control
- 3.6.2 Risks, issues and changes
- 3.6.3 Quality control
- 3.6.4 Project Assurance
- 3.6.5 Informal decision making
- 3.7 Support the Project Manager
- 3.8 Ensure effective communication
- 4 Project Board activities
- 4.1 Starting up a Project
- Figure 4.1 Starting up a Project
- Figure 4.2 Authorize initiation
- 4.2 Authorize initiation
- 4.3 Authorize the project
- Figure 4.3 Authorize the project
- 4.4 Authorize a Stage or Exception Plan
- Figure 4.4 Authorize a Stage Plan
- 4.5 Give ad hoc direction
- Figure 4.5 Authorize an Exception Plan
- Figure 4.6 Give ad hoc direction
- 4.6 Authorize project closure
- Figure 4.7 Authorize project closure
- 4.7 Reviewing benefits
- Figure 4.8 Reviewing benefits
- 5 Programmes and portfolios
- Figure 5.1 Functions and roles in the OGC best-practice guidance
- 5.1 Overview of programme and portfolio roles
- 5.2 The programme management (MSP) context
- 5.2.1 'Vision-led' business change programmes
- 5.2.2 Integrating the MSP and PRINCE2 themes
- Table 5.1 Mapping MSP and PRINCE2 themes for integration
- 5.2.3 Integrating the MSP and PRINCE2 organizations
- Figure 5.2 MSP governance and roles
- 5.3 The Portfolio Management context
- 5.3.1 The business change portfolio
- Figure 5.3 Portfolio management cycles
- 5.3.2 Implementing PfM
- Table 5.2 PfM portfolio delivery practices and factors to consider
- 5.3.3 Integrating the PfM roles in the organization
- 6 Troubleshooting
- 6.1 Project performance
- 6.1.1 Business Case and benefits
- Table 6.1 Resolving project Business Case problems
- 6.1.2 Organization
- Table 6.2 Resolving project organization problems
- 6.1.3 Quality
- Table 6.3 Resolving quality problems
- 6.1.4 Plans
- Table 6.4 Resolving problems with plans
- 6.1.5 Risk
- Table 6.5 Resolving risk management problems
- 6.1.6 Change
- Table 6.6 Resolving change problems
- 6.1.7 Progress
- Table 6.7 Resolving problems with progress
- 6.2 Performance of the overall organization
- Table 6.8 Resolving problems with the organization's overall performance
- Appendix A: Other OGC guidance
- A.1 Portfolio, Programme and Project Office (P3O)
- Figure A.1 Example of a P3O structure of support functions
- A.2 OGC's Gateway review
- Table A.1 Gateways in the programme/project lifecycle
- A.3 Relevant OGC maturity models
- Appendix B: About PRINCE2
- B.1 PRINCE2 principles
- B.2 PRINCE2 themes
- Table B.1 The PRINCE2 themes
- B.3 The PRINCE2 processes
- Table B.2 The PRINCE2 processes
- Figure B.1 The PRINCE2 process model
- B.4 Benefits of adopting PRINCE2
- Appendix C: Project Board agendas
- C.1 Authorize initiation
- C.2 Authorize the project
- C.3 Authorize a Stage or Exception Plan
- C.4 Authorize project closure
- C.5 Re-affirm aproval for a Stage Plan
- Appendix D: Product Descriptions
- Project Initiation Documentation
- Glossary
- Index
Systemvoraussetzungen
Dateiformat: PDF
Kopierschutz: Adobe-DRM (Digital Rights Management)
Systemvoraussetzungen:
- Computer (Windows; MacOS X; Linux): Installieren Sie bereits vor dem Download die kostenlose Software Adobe Digital Editions (siehe E-Book Hilfe).
- Tablet/Smartphone (Android; iOS): Installieren Sie bereits vor dem Download die kostenlose App Adobe Digital Editions oder die App PocketBook (siehe E-Book Hilfe).
- E-Book-Reader: Bookeen, Kobo, Pocketbook, Sony, Tolino u.v.a.m. (nicht Kindle)
Das Dateiformat PDF zeigt auf jeder Hardware eine Buchseite stets identisch an. Daher ist eine PDF auch für ein komplexes Layout geeignet, wie es bei Lehr- und Fachbüchern verwendet wird (Bilder, Tabellen, Spalten, Fußnoten). Bei kleinen Displays von E-Readern oder Smartphones sind PDF leider eher nervig, weil zu viel Scrollen notwendig ist.
Mit Adobe-DRM wird hier ein „harter” Kopierschutz verwendet. Wenn die notwendigen Voraussetzungen nicht vorliegen, können Sie das E-Book leider nicht öffnen. Daher müssen Sie bereits vor dem Download Ihre Lese-Hardware vorbereiten.
Bitte beachten Sie: Wir empfehlen Ihnen unbedingt nach Installation der Lese-Software diese mit Ihrer persönlichen Adobe-ID zu autorisieren!
Weitere Informationen finden Sie in unserer E-Book Hilfe.