Strategy Survival Guide

More documents

Recommendations

Info

Strategy Survival Guide Version 2.1 Prime Minister’s Strategy Unit home | strategy development | strategy skills | site index Strategy Skills > Managing the Project Developing the plan > in practice Involving team members in the development of the work plan and discussions of roles and responsibilities will help to build a good team working environment and to gain commitment. Team members can also offer new experience and insights. Holding an initial team away-day provides a good opportunity for this discussion. However, delays in recruitment may mean that this is not possible. In order to ensure buy-in and commitment to the project, the project plan should be cleared with the sponsor, key stakeholders and, if the project has one, the Steering Group. The project plan may take the following structure: Example Project Plan • Define the background to and drivers of the project • Define the problem that the project is to address and key questions to be answered • Set out initial analysis of available evidence. This should: • Identify key trends and issues • Identify key drivers of change • Identify work underway in related areas, both domestically and internationally • Set out thinking on possible ways ahead and methodology. • Identify the project time scales and key milestones • Define the individual work phases that will be required for delivery, the key milestones and outputs from each work phase. This plan should set out the activities required to achieve these outputs, and identify who will be responsible for delivery and by when • Identify the skills needed to take the work forward and the team working arrangements • Identify the potential risks to the successful delivery of the project • Determine the political sensitivity and feasibility of the issue • Identify the key stakeholders • Determine whether and how the project is to be communicated within relevant departments and externally, and set out the reasoning for this • Identify initial thoughts on potential implementation • Identify the assumptions you will be making regarding the project budget • Identify the project governance arrangements: sponsor minister and whether you will be having a project steering board and/or advisory group • Identify project evaluation arrangements and success indicators. The project plan should not be a static document to be placed on a shelf and ignored once the project is up and running. It should be a live document that is regularly revisited and revised. Strategy Survival Guide – Strategy Skills Page 64
References For more detailed information of all aspects of programme and project management, see the Office of Government Commerce website, which provides information on the principles and concepts of programme and project management and provides a helpful summary of the key stages and management activities required for delivering successful outcomes. The site also covers programme and project management techniques in detail, including: • OGC's successful delivery toolkit, which describes proven good practice for procurement, programmes, projects, risk and service management. • An introduction to the PRINCE2 Project Management Methodology. • OGC’s 22 Questions - From "what is our vision?" through to "what's the plan?" 22 Questions to help you consider your project. • Programme and Project Documentation - description of the contents of some of the commonly used documentation for planning, managing, monitoring and controlling progress on programmes and projects. Developing the plan In Practice: Joint SU & HO Police Reform Project The project management plan was developed jointly by the Strategy Unit and Home Office teams over the first few weeks of the project. The plan provided the means by which the work was integrated and co-ordinated. Several early pieces of work have informed the project plan: • a project proposal note and agreed terms of reference for the project; • development of issue trees to help identify key issues and logical structures for the workstreams; • initial data gathering to draw together the dominant evidence on different crime areas and the effectiveness of the police response. Based on the above and the Strategy Unit’s project plan template, the SU team undertook a first cut for discussion with the Home Office. Several iterations were then discussed at team meetings, covering in particular the ground rules on project governance as well as the analytical approach. The basic structure developed for the plan covers: Contents Purpose, project aims and scope Issues overview and proposed methodology Issues, workstreams and related work Governance arrangements Stakeholder analysis, risk analysis and success Implementation Annexes Issues trees Detailed analysis of workstreams Team member biographies The Strategy Unit maintained responsibility for pulling drafts together, but sought specific input from the Home Office in several areas given their policy expertise and the need to draw on the ongoing programme of work in the Home Office on options for police reform. (So, for example, the Home Office led on the detail of key stakeholders, and how and when to engage with them.) Separate brainstorms (including senior management from both sides) were held to flesh out the work programme and activity approach – linking this to the issue trees, work phasing, overall timelines, and agreeing the detail of workstream splits, activity and outputs. A high-level work programme was then drafted for inclusion in the project plan. The draft project plan was then put to the project steering group and relevant Ministers for comment. Strategy Survival Guide – Strategy Skills Page 65
Page 1:
Strategy Strategy Survival Survival
Page 4 and 5:
Strategy Survival Guide Version 2.1
Page 6 and 7:
Building an Evidence Base 113 Data
Page 8 and 9:
A Framework for Strategic Direction
Page 10 and 11:
These four components need to be co
Page 12 and 13:
Page 14 and 15:
Page 16 and 17: Strategy Survival Guide Version 2.1
Page 50 and 51: Recruiting a team In Practice: SU G
Page 52 and 53: • Commitment to a common purpose
Page 54 and 55: Away-days A project away-day is ano
Page 56 and 57: WHY ...are you telling me this? SO
Page 60 and 61: Try to put into practice the princi
Page 62 and 63: Encouraging creativity In Practice:
Page 64 and 65: There are clear differences between
Page 80 and 81: Identifying key stakeholders and th
Page 82 and 83: Engaging with stakeholders Having i
Page 86 and 87: • What channels do we know don’
Page 90 and 91: Preparing the Story Once you have a
Page 94 and 95: development process include brainst
Page 100 and 101: Reinforcing Loops A + Balancing Loo
Page 102 and 103: Structuring the thinking - Systems
Page 104 and 105: Opportunities • Where are the goo
Page 108 and 109: Structuring the thinking - PESTLE I
Page 110 and 111: Revolution This is creativity at it
Page 112 and 113: For example, Sub-problem: My collea
Page 114 and 115: Structuring the thinking - Creativi
Page 116 and 117:
Page 118 and 119:
in The Magenta Book) are rigorous m
Page 120 and 121:
Page 122 and 123:
• Avoid asking the same question
Page 124 and 125:
Expectations can be shaped by a num
Page 126 and 127:
Collecting data - Surveys In Practi
Page 128 and 129:
Page 130 and 131:
Collecting data - Interviews & focu
Page 132 and 133:
Step One: Define the problem explic
Page 134 and 135:
• Are the units correct? Step Sev
Page 136 and 137:
Analysing data - Modelling In Pract
Page 138 and 139:
Page 140 and 141:
The Five Forces Framework can be us
Page 142 and 143:
References Structure, Conduct, Perf
Page 144 and 145:
Page 146 and 147:
Symbols • What language and jargo
Page 148 and 149:
Page 150 and 151:
• Put a contact name, telephone n
Page 152 and 153:
Learning from others - Internationa
Page 154 and 155:
4. Functional Benchmarking or Gener
Page 156 and 157:
Page 158 and 159:
Strengths • Quantitative forecast
Page 160 and 161:
Page 162 and 163:
3. Bring drivers together into a vi
Page 164 and 165:
Scenario development In Practice 1:
Page 166 and 167:
Scenarios used in the Strategy Unit
Page 168 and 169:
groups at random. In other words, t
Page 170 and 171:
Page 172 and 173:
events. There are a number of diffe
Page 174 and 175:
Multi-criteria analysis In Practice
Page 176 and 177:
Page 178 and 179:
Cost-benefit & cost-effectiveness a
Page 180 and 181:
Page 182 and 183:
For further material, see the Ratio
Page 184 and 185:
Page 186 and 187:
Compelling vision for action - the
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Designing an implementation plan In
Page 194 and 195:
Creating Public Value http://www.nu
Page 196 and 197:
National Statistics http://www.stat
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Driver trees 97 Econometric modelli
Page 206 and 207:
management 17, 20, 27, 34, 45 outpu
Page 208:
Strategy Unit, Admiralty Arch, The
show all

Strategy Survival Guide

Create successful ePaper yourself

Delete template?

Save as template?