04.05.2014 Views

Strategy Survival Guide

Strategy Survival Guide

Strategy Survival Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Strategy</strong> <strong>Survival</strong> <strong>Guide</strong> Version 2.1<br />

Prime Minister’s <strong>Strategy</strong> Unit<br />

home | strategy development | strategy skills | site index<br />

<strong>Strategy</strong> Development > Justification & Set Up > Tasks<br />

Planing the project<br />

Having gained commitment to the project and its scope from stakeholders, it is important that the project is<br />

planned in detail. An accurate, well-maintained and frequently referenced project plan is essential to<br />

managing the project successfully.<br />

Although taking time to plan is crucial to the success of the project, planning is often neglected or rushed in<br />

the haste to get onto the more interesting analysis phase of the project, especially when stakeholders or<br />

ministers are keen for project results. However, planning is the whole basis of project management<br />

philosophy and it is vital to do it well. Team leaders should expect to spend as much as 30% of their time<br />

project planning.<br />

Taking a step back to develop a project plan before diving into the detail has a number of benefits:<br />

• it helps forge a common vision across the team<br />

• it provides coherency between different strands of the project<br />

• it helps to think through tasks and anticipate potential roadblocks<br />

• it highlights trade-offs on issues of time, budget, breadth and depth of analysis<br />

• it helps anticipate long lead-time activities<br />

• it helps manage key stakeholder expectations of what is in and out of the scope for the project, what<br />

the team is doing, and whether the project is on track<br />

• it provides an 'anchor’ when difficulties develop.<br />

The plan should go into significant depth on the project's rationale and approach, including how the work will<br />

be structured, what the key milestones will be, and how the main risks will be mitigated or minimised. In<br />

addition the plan should set out the intended approach for managing stakeholders and communications,<br />

and define the project governance structure.<br />

Finally, the extent to which the project will be in the public domain should be agreed. The sensitive nature of<br />

some projects may mean that it is not appropriate to announce them publicly.<br />

Useful links:<br />

> developing the plan<br />

> structuring the work<br />

> setting milestones<br />

> managing risks<br />

> defining accountability<br />

> managing stakeholders and communications<br />

<strong>Strategy</strong> <strong>Survival</strong> <strong>Guide</strong> – <strong>Strategy</strong> Development<br />

Page 17

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!