Skip to main content

Estimate to Decide: A Minimalist Playbook (Triggers, Not Calendars)

Ever participated in a backlog grooming or an estimation meeting that took forever? Ever worked on a project where leadership judges you for delivery only against your original estimates? Read on!

If so, you are not alone. This post has some ideas I have found to work most of the times. Have you applied any or all of these ideas before? What is your go to idea?

References: http://bit.ly/3HVbuE8 and LinkedIn post [By Alistair Cockburn]

Thesis: Estimation is unavoidable, but the win is making it cheap, decision-oriented, and revisited on signals (not on a calendar).

Here is an approach I have adopted repeatedly, with a reasonable amount of success.


1) Start with an appetite (timebox)

Decide what the work is worth before shaping it.

  • Example: “Two weeks max; scope flexes to fit.”

  • Effect: Shifts the conversation from perfect prediction to value and trade-offs.

2) Shrink variance by slicing

Smaller batches beat clever estimates.

  • Slice work into small increments (one week or less) with a clear and just-enough Done criteria.

  • Limit WIP so cycle times stabilize.

  • Visible outcome each slice → easier to steer.

3) Forecast quickly (no precision theater)

Use reference-class data or a rough throughput range; avoid point-level fantasy.

  • "We ship X points per two weeks" or “We ship ~3 to 5 slices per week” is enough to shape scope inside the appetite.

  • If discovery risk is high, reserve capacity for spikes up front.

4) Map assumptions

Identify what might fail, and decide what to test first, set expectations with dependency partners:

  • Map known dependencies and external approvals needed.

  • Identify failure modes - what if a dependency is delayed, or is poor quality?

  • Create fail-fast mitigations - incremental, small wins surface progress and issues early.

5) Re-estimate on triggers, not calendar

Define the few moments that must force a rethink. When a trigger fires: pause, resize, or reorder. No blame, just a new decision:

  • A new dependency or external approval appears.

  • Defect rate spikes or quality gates fail twice.

  • Rollovers repeat (same slice slips twice).

  • Major scope change, staff change, or >1 day blocked.

6) Operate in flight

Keep delivery light and boring:

  • Stale-signal review in standup: any trigger fired?

  • Adjust scope before the appetite breaks.

  • Celebrate “stopped early” when value capped out.

Tiny templates

Appetite Card

  • Timebox: ___ (e.g., 2 weeks)

  • Success looks like: ___

  • Must-have by week+1: ___

  • Nice-to-have if time remains: ___

Trigger Card
Re-estimate if any of the following happen:

  • New dependency or approval discovered

  • Defect spike / quality gate fails twice

  • Same slice rolls over twice

  • 1 day blocked, or major scope/staff change

  • _____

Goto metrics (to learn, not to punish)

Some examples

  • WIP and blocked time

  • Cycle time distribution (is it tightening?)

  • Hit rate vs appetite (did slices land on time?)

  • Trigger count per initiative (are risks front-loaded?)

  • Red/Yellow/Green to next milestone

  • Risks, Dependencies, Mitigations that need to stay on track

TL;DR

Estimate to decide. Reduce variance with slicing. Revisit on triggers, not the calendar.
That’s how estimation becomes a lightweight steering tool instead of precision theater.


Labels:

Comments

Post a Comment

Popular posts from this blog

14 Essential Software Engineering Concepts for Engineers and Managers

There are many terms and concepts that are important for an engineer to be familiar with, in order to effectively build software. This post includes some of those terms. I will continually add to or update this list. Agile. A flexible and iterative approach to software development that emphasizes collaboration, customer feedback, and adaptive planning. My experience and success with agile development was the inspiration behind starting this blog. DevOps. A set of practices and tools that improve efficiency, speed, and reliability of the product through automation and optimization of the software development and delivery process where operational efficiency is part of the development process. Continuous Integration and Continuous Delivery/Deployment (CI/CD). A set of practices and tools that result in faster and more frequent releases, through automation of building, testing, and deployment of software. A key part of CI/CD is to deliver software to production frequently and using tec...
Post a Comment
Read more

Forget Onboarding, do Alongboarding!

Alongboarding, an agile onboarding approach Alongboarding: We’re in it together! Organizations hire new people every day. A great first impression can make a tremendous difference in retaining employees. No one gets a second chance to make a great first impression, not even the best companies. An onboarding experience is an essential part of making that first impression on a new employee. Agile has been around for many years and has gained vast acceptance throughout the community. Yet, I find it disappointing that its tenets are not used well in most companies and most onboarding approaches follow a waterfall approach.  Alongboarding is an agile onboarding approach that applies agile tenets to onboarding new employees and makes the experience richer and more fulfilling. When I joined AppFolio as an agile coach, I experienced this approach during my onboarding. It felt like the team owned my success as much as I owned the team's success. It was a welcome change from some of m...
1 comment
Read more

Make onboarding fun with Onboarding Canvas!

The Onboarding Canvas is a tool that can be used for onboarding a new team member . We derived this tool from Spotify's adaptation of the Toyota Kata . I like this tool because no one can tell you precisely how your onboarding should be like in order for you to be effective at your new job. This is a tool for continuous reflection and adaptation. It puts the newcomer in the driver’s seat, makes the onboarding process agile through continuous collaboration with your team. Four quadrants The onboarding canvas has four quadrants: Now: It defines where the team is now, what is going on and how is the new team member adapting to the change? Definition of awesome: With the addition of the new team member, how would the team like itself to be? What would be awesome for the new team member? Next target: In order to move towards "Definition of awesome" what outcomes should be achieved in the next x weeks? Next steps: What are the immediate next steps for the team...
Post a Comment
Read more