What should I do to ensure that projects do not take 2-3 times longer than planned? Part 1

On Habré , a very important topic was recently raised - meeting deadlines for projects. As a metaphor, the author, Michael Wolf, uses the metaphor of travel and forecasting the timing of arrival, but does not provide practical advice on the completion of projects on time. To reveal the tips in a more understandable form, I will insert some presentations and slideshows into the post.
Let me give you a number of specific recommendations that will be useful for most projects:

• Properly handle requests for change requirements
• Trim excess functionality
• Manage risk
• Use flexible methodologies
• Learn to manage Death March projects.

Properly handle requests for change requirements

If you are implementing a project as per PMBoK, clearly use the processes associated with change requests. If you use flexible methodologies, then recalculate the timeline for the completion of the project each iteration:

If you use the Michael Wolf metaphor, the point at which you need to come periodically changes and you constantly have to change the direction of motion.

Trim excess functionality

A very important factor in the success of the project is the prioritization of functionality and the development is primarily the most important functionality that will bring more money and / or will be most useful to users. You also need functionality that will not be used - remove from the product. Look at Apple products, look at 37signals products, and you will understand what I'm talking about.

Manage risk

To complete the project in time it is necessary to consciously manage risks. Risk management can be ponderous in nature: Darkus habrayuzer published a vivid example in his post . More lightweight approaches are closer to me:

')

Use flexible methodologies

The modern flexible methodologies from a process point of view are based on an iterative approach that allows you to reduce risks and receive prompt feedback:

• " Scrum and XP: notes from the front line ." Henrik Knberg
• " Flexible development methodologies ". Wolfson Boris (arrogant samopiar)

Flexible methodologies (in particular, Scrum) make it possible to efficiently manage the project's content and, on the basis of feedback, obtain a more complete satisfaction with the project customer and meeting project deadlines: the customer can understand that he does not need some functionality or it is not a priority.

Learn to manage Death March projects.

There are projects that are actually doomed to failure in advance, therefore, according to Edward Yordan’s apt expression, they began to call Death March projects. Their management differs from standard projects, therefore this specificity should be known and taken into account:

PS

In the comments suggest habravchanam share their tips on meeting deadlines.