Habitable Code

JULY 22, 2022

So there's this big discussion going on about #NoEstimates — and how estimating is wasteful, misleading etc — for what seems like forever. If you try it, please publish your experiences and link to them via the comments here. TL;DR: Don't guess the size of a user story; slice the story until it’s the size you want.

Coaching 52

Coaching Conference Programming Agile 52

Apiumhub

MARCH 30, 2021

I decided to write this article because I’ve seen several times that young developers that join companies tend to misunderstand or struggle with the concepts of story points and estimations, and also because I’ve met product teams that in my opinion do not invest the necessary time grooming their backlogs and splitting user stories.

Agile 72

Agile Examples Development System 72

Altexsoft

JUNE 8, 2023

Learn the skill of estimation from Frodo Even though there are fans of the #NoEstimates movement (which emerged because someone was sick of always blowing the deadlines), most teams still make estimations. And one of the popular approaches involves using story points to measure the amount of effort required to complete one user story.

Agile 59

Agile Weak Development Team Technical Review Software Review 59

InfoQ Culture Methods

NOVEMBER 1, 2019

Agile teams may need to deliver milestones expected at a certain time, so will need to forecast or risk being accused of being “Agile and late”. There are metrics that relate to the “Logical Six” potential sources of delay which are key to improve forecasting accuracy.

Metrics 41

Metrics Agile Report Project Management 41

Altexsoft

DECEMBER 29, 2021

In the same post, he laments that SPs are frequently misused and advises to focus on slicing tasks and continuously delivering value instead of making estimates, whether in SPs or not (you can check his or other articles on the #NoEstimates movement).

SCRUM 64

SCRUM Agile How To Software Review 64

James Shore

FEBRUARY 3, 2021

Another popular alternative is the #NoEstimates movement, which sidesteps estimation entirely. It’s better to bite the bullet, plan for a lower capacity, and use the resultant slack to increase the team’s actual, real-world ability to deliver. There are two approaches, and I’ve included both in this book.

Weak Development Team 75

Weak Development Team Software Review Technical Review Agile 75

Marcusoft

SEPTEMBER 22, 2018

It can be something simple as Trump or very very sensitive as #NoEstimates. She started with a very revealing thought experiment: Imagine that you have a debate with someone you don’t agree with. Now imagine that you use FACT to fence them to the ground. Your arguments are wastly better.

Agile 40

Agile Conference System Social 40

James Shore

AUGUST 19, 2020

Zispro asks, “Will #noestimates be in the book?” (laughs) UncleScientist: “My only snobby comment is to not cite Wikipedia.” jokingly) What? What’s wrong with citing Wikipedia? Don’t worry, we’re going to update it. Yes, yes it will. Right here (shows table of contents ) in the Accountability chapter. It’s currently pencilled in.

Agile 99

Agile Weak Development Team Development Team Review Development 99