Accidental complication: another reason why estimates don’t work

Accidental complication Another reason why estimations can’t work goes by the name of accidental complication. J.B. Rainsberger introduced this concept at Oredev 2013 . The gist of the argument is this: every feature or functionality added to an existing project has two cost elements (what you want to estimate): Essential complication or g(e): How hard …

All the Conferences and talks about #NoEstimates in 2015

Are you talking about #NoEstimates at a local or global conference during 2015? Email me at Vasco.Duarte@oikosofy.com. I’ll collect all the #NoEstimates talks and conferences that include the topic right here!   Agilia 2015, Brno, Czech Republic Speaker: Henri Karhatsu Topic: #NoEstimates – Going Beyond Estimates Date: March 23rd, 2015 Agile India 2015, Bangalore, India …

5 No Estimates Decision-Making Strategies

One of the questions that I and other #NoEstimates proponents hear quite often is: How can we make decisions on what projects we should do next, without considering the estimated time it takes to deliver a set of functionality? Although this is a valid question, I know there are many alternatives to the assumptions implicit …

Lean Change Management: A Truly Agile Change Management approach

“I’ve been working in this company for a long time, we’ve tried everything. We’ve tried involving the teams, we’ve tried training senior management, but nothing sticks! We say we want to be agile, but…” Many people in organizations that try to adopt agile will have said this at some point. Not every company fails to …

The Release Paradox: releasing less often makes your teams slower and decreases quality

Herman is a typical agile coach. He works with teams to help them learn how to deliver high-quality software quickly. Many teams want to focus on design, architecture, or (sometimes) even on business value. But they are usually not in a hurry to release quickly. Recently Herman conveyed a story to me that illustrates how …