Sometimes we just need a quick estimation on something, without asking everyone to use their laptops to login to a website, or passing out estimation cards to everyone. For this, we can use the simple “flying fingers” technique. We read the story, discuss it briefly, then each builder hides one hand with their estimation done in “number of fingers” to represent the size. Someone counts down 3, 2, 1, “Go”, and everyone reveals at once. ...
User stories are reminders of features, not full specifications. Avoid recording every detail up front because details change. We’ll capture the details later, when they matter. When a story reads like a contract, it stops being a conversation. When it reads like a reminder, it invites one. Follow the acronym “INVEST” as a quick check. I.NDEPENDENT N.EGOTIABLE V.ALUABLE E.STIMATABLE S.MALL T.ESTABLE TESTABLE Each story needs to be able to have one or more tests that can prove that the story is done. ...
User stories are reminders of features, not full specifications. Avoid recording every detail up front because details change. We’ll capture the details later, when they matter. When a story reads like a contract, it stops being a conversation. When it reads like a reminder, it invites one. Follow the acronym “INVEST” as a quick check. I.NDEPENDENT N.EGOTIABLE V.ALUABLE E.STIMATABLE S.MALL T.ESTABLE SMALL A story should be doable by one or two builders within a single iteration so no single story can dominate the team. ...
User stories are reminders of features, not full specifications. Avoid recording every detail up front because details change. We’ll capture the details later, when they matter. When a story reads like a contract, it stops being a conversation. When it reads like a reminder, it invites one. Follow the acronym “INVEST” as a quick check. I.NDEPENDENT N.EGOTIABLE V.ALUABLE E.STIMATABLE S.MALL T.ESTABLE ESTIMATABLE Stories must be concrete enough to estimate. Vague demands like “The system must be fast” are not estimable, they lack scope, measurable criteria, and acceptance tests. ...
User stories are reminders of features, not full specifications. Avoid recording every detail up front because details change. We’ll capture the details later, when they matter. When a story reads like a contract, it stops being a conversation. When it reads like a reminder, it invites one. Follow the acronym “INVEST” as a quick check. I.NDEPENDENT N.EGOTIABLE V.ALUABLE E.STIMATABLE S.MALL T.ESTABLE VALUABLE User story’s first job is to be valuable to the business. ...