Kirill Kaplin
Director
Reading time: ~ 8 min
Sep 30, 2022
Kirill Kaplin·Director·Reading time: ~ 8 min·Sep 30, 2022
PM pain or why task estimates matter
Development is not always simple or predictable. We often work through negative scenarios, assess risks, draw Gantt charts, plan, perform other rituals, and sacrifice to the gods of development to get a finish date and a safety buffer.
When plans diverge from reality
Things do not always go as planned: the human factor on the team plays a trick, the client’s mood shifts and half the concept changes, or autumn simply arrives outside the window. A scope of such factors can affect deadlines and the plan.
At the head of a development team there are usually “they.” “They” are PMs — the people who constantly bother developers with their rituals: dailies, time tracking, remaining hours on tasks, sprint progress. Every developer has faced the moment when “they” ask: “So how’s it going? When will it be done?”
During those questions developers roll their eyes to read information from the back of their head, while thinking: “Again?! Why do they need this?” If you understand what is required and give it upfront, the whole process runs smoother. So we decided to share the view of our Lead PM, Sveta Shishkova, on task estimates and time tracking.
How to understand a PM — a direct guide
Why?! Why does a PM ask the same question? There are several important facts:
- In everyday work, a manager needs estimates for a defined pool of tasks to track budget and timeline during development and react quickly to related risks.
- Everyone knows PMs love to dream (that everything will ship bug-free and on time) and to plan. Besides project plans, there is overall planning of developer allocation across projects to understand workload. Overload means expanding the team; underload means finding useful work.
- Setting priorities for the next stage. Estimates per task matter because they can define the order of work. PMs often use “value vs complexity.” For example, run brainstorms with the client and team and rate tasks on business value and implementation difficulty — often on a three-point scale: high, medium, low. Then prioritize: very valuable and very fast first, then very valuable and moderately fast, and so on. Low-value, very hard tasks sit in a perpetual backlog picked from very slowly — or never.
- Project estimation at presales. Sales often push PMs, who then push the team. At this stage estimates are rough because requirements are rarely clear and nobody knows exactly what to build. Those estimates drive which tasks stay or go, what is deferred, how work is split into phases, and the approximate budget and timeline — plus planning resources, team members, Gantt charts, and similar work.
How does this help a developer?
We covered why “they” need it. But do developers need it themselves? Imagine your manager went on vacation — maybe forever. You work quietly, nobody asks “How’s it going?”, you even start to miss them, and a day, two, a week pass. Nobody asks for estimates; life is good. Should you still estimate for yourself?
A few arguments in favor:
- Decomposition and estimation are a developer’s air and water. The brain is expensive to run; thinking is hard and painful, so people naturally think as little as possible. Decomposition and clear task wording help. If you draft an execution plan, decomposition is roughly half done. Title the steps and leave notes so you remember what you scribbled yesterday. Skip that and a task that looked hard but was never decomposed or described well will shift shape during development, turn into a scary scribble you avoid looking at, and eventually trigger impostor syndrome. Decomposition and estimates mean fewer headaches and fewer sighing (often swearing) PMs.
- Self-control. Plan your day. If the PM is on vacation, do it yourself — for your own sake. If you fall off the plan, stop and think. You can check whether your expectation (the estimate) matches reality or the original plan no longer fits. Estimates help you analyze work and decide when something goes wrong.
- Unpredictability and feeling lost. Without estimates you do not grasp task complexity or plan work well. All you can say is task order — often by eeny-meeny-miny-moe at the monitor with eyes closed. You do not know when to relax or when to tighten up. That breeds stress and burnout. Do you need that?
Now that we agree estimates matter for everyone, let’s move on.
The purpose of an estimate
If a task is new and you have never “touched” it before, guessing how long it takes is pointless. You can point at the sky and run rituals, but you will not get a reliable estimate until the task is done. It sounds paradoxical, but there is truth in it.
Here is what matters: an estimate is not guessing duration. An estimate is an agreement between the client and the executor on the scope and way of doing the work.
Inside our company we often set internal rules for tasks. They organize how developers work and how delivery moves on the project — and keep the PM from jumping out the window when reporting to the client.
Before taking a task or putting it in a sprint, it must have an estimate. At sprint planning, hold a team meeting, discuss sprint tasks, and review estimates to plan a healthy load — one where developers do not curse the PM while picturing them in hell.
After work starts and the estimated time is used up, the estimate can change — but only after informing the PM and explaining why (ideally while staying white and fluffy and innocent). Then agree on next steps; extra hours are usually approved with the client and the task is finished.
After the sprint, run a retrospective, compare planned vs actual hours, and define how to avoid repeats.
These rules prevent developers from exceeding estimates without the PM knowing — so reporting and hour reconciliation have no surprises, no furious PM, no wide-eyed developer.
Conclusions
A PM is not a circus act who bothers everyone with strange gestures, questions, and estimates for no reason. I hope it is clearer now why they do it.
When everyone understands responsibilities and roles, you get idyll, love, a dream team, sunshine, and a rainbow. When every team member sees that their estimates affect everything on the project, planning and iterations become enjoyable, the PM compliments your beautiful straight hands, and the client pays millions for your work.