- Pass The PRINCE2 Exam First Time
- PRINCE2 In Bite-Sized Chunks.
- Key Foundation and Practitioner Learning Points - PRINCE2
- Change Management
- Managing and Controlling a PRINCE2 Delivery Stage
- PRINCE2 Project Closure
- PRINCE2 Starting Up A Project Process
- Using PRINCE2 Initiating A Project Process
- PRINCE2 Authorizing Initiation
- The PRINCE2 Controlling a Stage Process
- Appoint The Executive and Project Manager
- Authorising a PRINCE2 Project
- Authorize a Stage or Exception Plan
- Authorize a Work Package
- Capture and Examine Issues and Risks
- Change Control
- Change control procedures
- Configuration Management
- Configuration Management and Change Control
- Controlling a stage
- Create the PRINCE2 Communication Management Strategy
- Creating a PRINCE2 Plan
- Design and appoint the Project Management Team
- Execute a PRINCE2 Work Package
- Give Ad-hoc direction in a PRINCE2 project
- Hand over products and evaluate a PRINCE2 project
- Managing A Stage Boundary
- Managing Product Delivery process
- PRINCE2 - Authorise Project Closure
- PRINCE2 - Directing a Project PRocess
- PRINCE2 Configuration Management and Change Control
- PRINCE2 Controls and Tolerance
- PRINCE2 Estimating Techniques
- PRINCE2 Management Stages
- PRINCE2 Plans
- PRINCE2 Principles
- PRINCE2 Product-based Planning video
- PRINCE2 Product-based planning technique
- PRINCE2 Progress reporting
- PRINCE2 Quality Theme
- Plan The Next Stage or Exception Plan
- Plan the Initiation Stage in PRINCE2
- Prepare the PRINCE2 Quality Management Strategy
- Prepare the Risk Management Strategy
- Prepare the outline Business Case
- Product Based Planning
- Project Board and Project Manager PRINCE2 Controls
- Project Startup
- Quality Expectations and Acceptance Criteria
- Quality Management Strategy
- Quality review technique
- Report Highlights
- Reporting PRINCE2 Stage End
- Select the project approach and assemble the Project Brief
- Set up the PRINCE2 project controls
- Simple Study Aid
- Tailoring PRINCE2 Themes
- Take corrective action
- The Closing a Project Process
- The Controlling a Stage Process
- The Core Seven
- The Only PRINCE2 Sample Practitioner Exam Paper On The Internet!
- The PRINCE2 Business Case
- The PRINCE2 Change Theme
- The PRINCE2 Initiating a project process
- The PRINCE2 Process Sequence
- The PRINCE2 Processes
- The PRINCE2 Quality Review Technique
- The PRINCE2 Risk Management procedure
- The PRINCE2 Themes
- The Prince2 Process Sequence
- The risk management procedure
- prepare for planned or premature closure
- The PRINCE2 Article Library
- 38 Speedy Power Keys For Your PRINCE2 Project Health Check.
- Carrying out a PRINCE2 Quality Check
- The Product Description
- The plans theme and product based planning
- Creating a PRINCE2 Product Description
- PRINCE2 - Keeping Your Project On track - Part 2
- PRINCE2 Article Database
- PRINCE2 – Keeping Your Project On Track – PART 1
- Tailoring PRINCE2 for a feasibility study.
- Tailoring PRINCE2 with Agile (DSDM Atern)
- The Benefits Review Plan
- The PRINCE2 Risk Theme – Uncertainty Mastered!
- The PRINCE2 Work Package
- The Secrets Of tailoring PRINCE2
- The Use and Content of the Issue Register and Issue Report
- Applying earned value calculations to PRINCE2.
- PRINCE2 Foundation and Practitioner Exam Tips
- Using Project Sc ale In A PRINCE2 Project
- Creating a PRINCE2 Exception Report
- Agile verses PRINCE2 - a new species in evolution
- PART TWO of my Configuration Management In PRINCE2 Video
- PRINCE2 Quality
- Real-World PRINCE2 Planning
- Reviewing the progress on a PRINCE2 project
- Risk management
- Things You Might Not Know About PRINCE2
- The PRINCE2 Project Board and Governance
Select the project approach and assemble the Project Brief
PRINCE2 In Bite-Sized Chunks.
Select the project approach and assemble the Project Brief.
A big mistake that project managers can sometimes make is to rush headlong into planning, only to find that the plan does not use the best approach to develop and deliver the end product. This can be very inefficient and frustrating. It is therefore best to first consider how the work of the project is going to be approached.
The first consideration may be whether or not the solution can be provided in-house or contracted out to third parties. This may not be all or nothing, but the organisation needs to consider its knowledge skills and experience, not to mention confidence, in its ability to create some all of the projects products.Another consideration is the design approach taken. For example the solution may consist of a modification to an existing product, or should it be a brand new design?
Understanding the manner in which the work is to be carried out will point to the use of customer or supplier standards, practices and guidelines.
The chosen project approach will be used as an input to create the strategy documents contained within the project and initiation documentation. For example, using leading edge technology will increase project risk, and how all this is to be managed will be laid out in the Risk Management Strategy document.
PRINCE2 recommends that a structured approach is taken to answering the above questions leading up to the creation of the Project Brief.
In deciding upon the chosen project approach, the preferred solution should be the one that the project’s product can deliver and one for which the outline business case remains viable, desirable and achievable.
The Lessons Log should be reviewed and previous or similar projects reviewed related to the project approach. Another question that should be answered is “are there any relevant corporate or programme strategies, including standards or practices, that need to be applied?”
The customer and supplier roles must have heavy involvement in deciding the best project approach to ensure a feasible and achievable solution is determined. Other considerations are the operational environment and constraints into which this solution must fit.
The Project Brief now needs to be assembled, and this includes confirming the objectives and desired outcomes, the project scope and exclusions, and any constraints or assumptions. The project management team structure and role descriptions should be reviewed and updated if necessary.
The Daily Log will be used to record any new issues or risks.
For more information CLICK HERE



