When a project is estimated to take 12 months to deliver and it is needed in 3

By | 27/03/2016
deadlines

This article sets out a list of 5 steps that can help reduce the timescales of a project.

Step 1

Establish the confidence of the estimates. Are some high due to a lack of clarity of what is required or a high amount of contingency added. It may be possible to get lower estimates from challenging these.

Step 2

Identify what is known about the scope and requirements and establish what can be de-scoped if anything.

A key question to help determine priority is if the solution didn’t deliver this requirement then would it make the project not worth having.

Go through the requirements with the most cost and time associated with them and establish whether this is in line with the what the business expect and whether it still adds the value required compared to the cost.

Explore the possibility of phasing. It may be that not all functionality is required in 3 months and some functionality can be in a later phase after this date.

Step 3

Agree acceptance criteria. This is to ascertain whether the solution proposed is more than required by the business. This may be a workshop needed between the business stakeholders and IT stakeholders so that different options can be discussed which meet the acceptance criteria. Business requirements can be met by more than one solution. A cheaper faster solution may meet the same acceptance criteria.

Step 4

Establish if there are any manual workarounds can be used in the short term if there is a gap.

Step 5

Establish whether the project is suitable for an Agile approach. There are 2 main approaches that could be suitable for consideration.

  1. Can the project be broken down into smaller chunks so that more people can work on it and have parallel working. Use cases is one technique that could be used to achieve this.
  1. If the project has high stakeholder buy in then daily scrum meetings with key business and IT stakeholders can be held to ensure the project is kept on track and to resolve any blockers quickly. User stories and story boards are useful techniques for getting agreements of how the solution must work and getting joint understanding and consensus

 

 

Thoughts? Questions? Please share in the comments.

 

 

Author: Helen Winter

An Management Consultant responsible for structuring programmes, success criteria, mobilisation, management of scope, budget, timely delivery, benefits realisation and stakeholder satisfaction. Helen has led on large transformation programmes to execute delivery along with strategic business outcomes. Helen is also a global business author with publisher Kogan Page where her first book “The Business Analysis Handbook” was a finalist for 2 major industry awards. One was for contribution to project management literature with PMI and the other was the Specialist book category for the business books awards. She is an active member of the APM programme management group. She is currently involved in a focus group sharing examples of good programme management practice and is an established speaker for project management forums. In her free time, she loves sharing her knowledge on her blog BusinessBullet.co.uk which is followed by over 5000 visitors a month.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.