The Cumulative Flow Diagram (CFD) provides typical information about status of your Scrum project: how much work is done, ongoing and in backlog, what is the pace of progress, etc. In this blog post, Pawel Brodzinski explains that you can also use the Cumulative Flow Diagram to detect the issues that a Scrum team might face.
Technical debt and legacy code are best dealt with in an agile way: continually and in small bites, focusing on the code being changed due to new requirements or defect fixing, reflecting feedback from the production.
Pair Programming is one of the eXtreme programming (XP) original practices. Continuously in surveys about Agile, it is one of the least used Agile practices. In this blog post, Dave Nicolette do an extensive survey of pair programming trying the question: “does pair programming work?”.
When your organization is thinking to adopt Scrum or is just beginning to use it, there are always questions that people will ask about how Scrum really works. As an independent Agile Coach, Roger Brown has collected 85 of them that he has arranged under major topics like people or technology.
This short (and humorous) video presents the 3 most common mistakes and 5 best-practices to improve your Scrum Sprint Retrospective meeting.
Metrics are an important tool when you want to manage something. It is very important to define what you want to measure as this will also impact your project team activity. In this blog post, Bob Boyd proposes 9 metrics for Scrum.
«Self-organizing team» may be the most overused, misunderstood, vague, and mis-leading phrase of the decade. What is a self-organizing team? How are self-organizing teams different from other teams? What makes self-organizing teams the key to unlocking creativity and agility? This talk explores the elements of success for self-organizing teams, and show why such teams are essential for meeting the demands of a fast-changing world.