- Use the estimation to capture the uncertainty
- small complexity ⇒ 1 day / 8 hours
- medium complexity ⇒ 3 days
- large ⇒ 5 days
- Any uncertainty probably will be multiplied consecutively: 1 day for low uncertainty, 2 days for medium uncertainty, 3 days for high uncertainty
- don’t blatantly change the estimation, for instance: initially, we’d set the estimation to medium, but later on, it was changed to large unless we have a justification and reasonable reason for this one (for ex: high cohesion with the other teams and the ‘bolanya’ not in ours)
- instead, we need to ensure that we work and aim for the expected estimation that we’d set before
- Large or epic tasks should be divided into smaller chunks
- applicable just for the: feature related tickets, not for the bugs (just followed the SLA that was pre-defined previously)
Caveats and confusion
- how do we define the criteria for the uncertainty?
- should we need a regular evaluation?
- What if, there’s complex bugs and engineers will put much effort into there? should