Appetites

by Feb 10, 2023

I’m reading about Shape Up. The agile methodology of Basecamp.

They have a unique way of thinking about estimates. They call it Appetite.

A stakeholder is asking for an estimation for an idea. The first thing you do is make a design to do the estimation.

An Appetite flips this concept. The stakeholder gives the time budget for an idea.

This means we don’t need to create a design beforehand. We do this when we implement the idea.

Because we have a time budget, we have a creative constraint on the design process. This is true agile: “Fixed time, variable scope”.

The only reason the stakeholder wants an estimate is to decide if the time is worth spending on the idea.

By setting the time up-front, the stakeholder is giving a clear sign of what the idea is worth to him.

Appetites: Interesting concept!

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

SpecFlow: Great concept, flawed execution.

SpecFlow: Great concept, flawed execution. SpecFlow, a BDD framework designed to make writing scenarios a breeze for requirement analysts. The problem: It falls short of its promise. ❌ The reality? Analysts rarely, if ever, write the specs themselves. Instead,...

read more

What if…? Production has a Staging slot.

What if...? Production has a Staging slot. Staging or QA environment needs to be the same or as close to production as it can be. Preferably, you want to restore a recent backup 💾 from Production as Staging and then deploy your changes 🔄. Kudos 👏 if you've fully...

read more

UUID v7 coming in .NET 9

UUID v7 coming in .NET 9 For those that didn't know, you can create Guids in different ways (algorithms). System.Guid supports UUID v4 out-of-the-box, the most used version. UUID v7 is now added, which creates Guids based on the current time. This means Guids can be...

read more