Sat.Mar 30, 2019

article thumbnail

Burn-down chart: an analogy

Musings on Project Management

It seems that there is always confusion the first time someone rolls up on an agile methods burn down chart: What are we burning? How much is there to burn? How long does it take? What is the starting point? When does it end?

Agile 186
article thumbnail

The Humble, The Hungry, The Smart: Beyond “The Five Dysfunctions of a Team”

Scrum.org

Building (and hiring) a great team takes time and effort. Patrick Lencioni’s “ The Five Dysfunctions of a Team ” became a staple reading in an Agile community these days. And for a good reason. Agile ways of working are all about teamwork. A self-organizing and cross-functional team is in the heart of the Scrum framework. In the book, the author cites the following 5 dysfunctions: Lack of Trust due to invulnerability. fear of conflict to preserve artificial harmony. lack of commitment leading to

article thumbnail

What's Missing from the Agile Software Development Paradigm

Herding Cats

Agile software development is framed by a manifesto , a set of 12 principles, several methods. These are all focused on developing software, delivering that software to those paying the developers. There is a fundamental critical success factor missing from this paradigm. The customer is accountable for knowing what Done Looks Like (in Unity of measure meaningful to their domain).