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

    A very important topic was recently raised at Habré - meeting project deadlines. As a metaphor, the author, Michael Wolf, uses the metaphor of travel and predicting the time of arrival, but does not give practical advice on completing projects on time. To reveal the tips in a more understandable way, I will insert some presentations and slidecasts in the post.
    Let me give you a number of specific recommendations that will be useful for most projects:
    • Properly handle change requests
    • Trim unnecessary functionality
    • Manage risk
    • Use agile methodologies
    • Learn to manage Death March projects

    Properly handle change requests


    If you are implementing a project according to PMBoK, clearly use the processes associated with change requests. If you use agile methodologies, then recount the project completion deadlines each iteration:
    Presentation at http://www.slideshare.net/Cartmendum/hitting-moving-target is not available.

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

    Trim unnecessary functionality


    A very important factor in the success of a project is the prioritization of functionality and the development of, first and foremost, 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 on time, you need to consciously manage risks. Risk management can be heavy-handed: a vivid example was published by the Darkus habraiser in his post . I find closer lightweight approaches:


    Use agile methodologies


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

    Flexible methodologies (in particular Scrum) allow you to effectively manage the project content and, on the basis of feedback, get more complete satisfaction of the project customer and meeting project deadlines: the customer can understand that he does not need some functionality or is of a non-priority nature.

    Learn to manage Death March projects


    There are projects that are actually doomed to failure in advance, so they were called Death March projects by the apt expression of Edward Jordan. Their management differs from standard projects, therefore, this specificity must be known and taken into account:


    PS


    In the comments, I suggest that the residents of Habrava share their tips on meeting deadlines.

    Also popular now: