Planning - common mistakes

Over the years, I have seen some classic planning mistakes, which I will briefly summarize here:

1. Planning exclusively based on estimates

In the IT industry, it is very common to ask how long a given task will take. I wrote more about this topic here [LINK]

We collect estimates, it turns out that the feature will take 100 hours, we will divide it into people and the number of sprints, and the plan is ready. Unfortunately, it is not that simple. First of all, we need to understand the strategy for implementing the given functionality and who will be doing it.

2. Wishful thinking

This is a classic trap that everyone falls into, regardless of experience. Only by being aware of the phenomenon can you do something about it.

 In short, we assume that something will go according to plan even though we know the risks or doubts.

3. Precise plans for unclear requirements

Sometimes we may be under pressure to present a plan for very general ideas. We must defend ourselves against this at all costs. Would you agree to give a deadline for building a house even though you don't know its exact plans?

4. Clinging to estimates instead of checking if something is ready

Someone has a task for 20 hours, they have logged 19 hours so it will be delivered soon, right?

Unfortunately, no. If we have good relationships with the team, we will get information that the given task will not be finished that quickly. However, not everyone in the team has the right maturity, experience, or sense of responsibility. Therefore, we must be open-minded and keep our finger on the pulse, especially for critical tasks.

5. Creating plans in a hurry

The plan you build is of great importance. It will affect the finances of the organization but also the team you work with. Creating strategic moves in a hurry is never advisable. It is then exceptionally easy to fall into the trap of wishful thinking.

6. Don't plan based on a sunny day scenario

We all want this scenario to come true, but it is rare in complex projects. I prefer to plan according to a rainy day scenario. If you do everything right, the plan will usually end somewhere between both of them. 

In addition to mistakes, it is worth knowing good practices, about which I wrote here: LINK

Some planning inspirations