Estimating complexity vs time ….

Estimating complexity vs time… it cannot be done one without the other. First i will write why we should estimate complexity and then a very short point ’cause in the end…’. At least this might feel like it for some of us…

Why should we estimate complexity in scrum

1. Focus on Problem Solving: Complexity estimation shifts the focus from estimating the time it takes to complete a task to understanding the complexity of the problem itself. This encourages teams to analyze and break down complex tasks into smaller, manageable pieces. Kaizen like. Problem-solving mindset rather than simply focusing on time constraints.
2. Improved Accuracy: Complexity-based estimation often leads to more accurate estimates compared to time-based estimation. By considering factors such as dependencies, uncertainties, and technical challenges, teams can provide estimates that better reflect the actual effort required to complete a task.
3. Flexibility and Adaptability: Complexity-based estimates allow for greater flexibility and adaptability in planning and prioritization. Instead of being constrained by fixed time estimates, teams adjusts their plans based on the complexity of tasks and the changes during the project.
4. Better Risk Management: Focus on complexity can identify risks and uncertainties early in the project lifecycle. This encourages the deep understanding and gathering detailed information about the tasks, re-prioritization of tasks.
5. Encourages Collaboration and Communication: Complexity estimation encourages collaboration and communication within the team. Team is more likely to engage in discussions about technical aspects, share knowledge, collective expertise.
6. Facilitates Continuous Improvement: Complexity-based estimation aligns with the principles of empirical process control in Scrum. Emphasizes transparency, inspection, and adaptation. By regularly reviewing and refining estimates based on actual outcomes and feedback. Teams can continuously improve their estimation accuracy and project planning processes.

Overall, estimating complexity versus time in Scrum promotes a deeper understanding of project requirements, enhances collaboration and communication within the team, and enables more accurate planning and risk management, ultimately contributing to the success of the project.

Why estimating anything doesn`t really work

I totally agree that splitting the task in smaller steps is the best thing we can do. Smaller, the better, like chocolate. It is more fun to eat more small pieces then one big bite.

Estimation is the main thing to help us complete every sprint on 0 (of anything) debt. Everything should be done.

BUT

We always have a deadline… The sprint. No matter what and how we estimate it is always something we should achieve in 2 weeks. The question is can we do more ? Then we have another deadling of making everything work because the product owner or someone else requets it and there was a deadline set for us, with or without our detailed knowledge about it.

It always seem easy at the begining but then somehow we get lost and confused ? Maybe we are missing tasks. Missing scenarios, some unexpeccted delay…

Some not conclusive final thought…

In the end it works great on paper and without time pressure, so we can really get it step by step with a fine grained plan. Other then that there is always a trade off …