
Executive Guide to Directing Projects
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
More details
Other editions
Additional editions

Content
- 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
System requirements
File format: PDF
Copy-Protection: Adobe-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Install the free reader Adobe Digital Editions prior to download (see eBook Help).
- Tablet/smartphone (Android; iOS): Install the free app Adobe Digital Editions or the app PocketBook before downloading (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (only limited: Kindle).
The file format PDF always displays a book page identically on any hardware. This makes PDF suitable for complex layouts such as those used in textbooks and reference books (images, tables, columns, footnotes). Unfortunately, on the small screens of e-readers or smartphones, PDFs are rather annoying, requiring too much scrolling.
This eBook uses Adobe-DRM, a „hard” copy protection. If the necessary requirements are not met, unfortunately you will not be able to open the eBook. You will therefore need to prepare your reading hardware before downloading.
Please note: We strongly recommend that you authorise using your personal Adobe ID after installation of any reading software.
For more information, see our eBook Help page.