Read about the experiences and ideas of Agile colleagues around the world, and share your own thoughts here. You can also visit
, which features blogs by experts in the fields of Scrum, Agile, and the broader business world.
4/19/2017 by Anurag Prakash
The burn-down has exploded in popularity as a tool for tracking the team's activities, but I have found quite a few misuses of burn-downs.
4/18/2017 by Mhd Mrhaf Halabi
Most organizations try an Agile transformation in the hope that they will become faster, able to do more with fewer resources, and increase quality. Although these things eventually happen, they don’t reflect the real picture of Agile.
4/18/2017 by Abhijit Jadhav
Our team uses a fun game based on a fictitional Craigslist purchase. We have found that it helps us gather information about the previous sprint and encourages involvement from all members.
4/13/2017 by Gurtej Pal Singh
Most organizations can benefit from DevOps practices if they are implemented wisely. Here are a few common patterns among organizations whose DevOps adoption practices improve their results.
4/12/2017 by Viktor Buzga
Did you ever find it difficult to explain the advantages of user stories over requirements and specifications documents? I did, until I found this daily-life example that makes sense to customers.
4/12/2017 by Ines Garcia
Here is how the Definition of Ready helps improve team velocity.
4/11/2017 by Erich Buhler
When I visit a company, I always try to measure a couple of variables as a good starting point for a change. It helps people secure some important alignment, make their ideas more mature, and keep goals clear.
4/10/2017 by Manjunatha Gopalakrishna
The sprint review is an often misunderstood ceremony. Here are some best practices for improving the way we manage our reviews.
4/7/2017 by Alexander Frumkin
Many clients ask me if they should bring a product owner to their daily stand-ups. My answer is no . . . and yes.
4/6/2017 by Humberto Cordioli
One of the smartest elements of the Agile/Scrum framework is the importance of the roles. It's important to realize what might be lost in the absence of this simple configuration of product owner, ScrumMaster, and development team.