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.
10/1/2015 by Pedro Gustavo Torres
Consider what the KPIs of Agile teams should be. I believe you have a choice between two categories . . .
9/30/2015 by Sumant Raja
Any organization performs a colossal number of day-to-day activities, but not all of them translate into benefit. When thinking Agile, there is one important question every organization needs to ask.
9/29/2015 by Anu Smalley
After a recent training class, I realized that in conversations with ScrumMasters, they've talked about their coaching efforts with their development teams, but not about what they've done to support their product owner.
9/29/2015 by Jaap Dekkinga
When I coach clients, our usual concerns are about how to implement an Agile framework for large organizations.
9/28/2015 by Gurpreet Singh
It is often said that all successful people are good storytellers. I find this saying inspiring -- and useful in the context of many Agile processes.
9/28/2015 by Robert Weidner
A number of techniques have proven useful for creative problem solving in an Agile environment, and the best are lightweight tools, quick and easy to implement, bearing low cost and high value. Here are my six favorites.
9/25/2015 by Kapil Goel
Is your organization functioning with Agile like a rope or a chain? See how this metaphor works for understanding flexibility.
9/25/2015 by Pankaj Srivastava
Test-driven development (TDD) is an engineering practice that uses a test-first approach to software development. Here is how we've used it.
9/24/2015 by Adonis ElFakih
Organizations seeking to transform to Agile are faced with resistance from all sides, and it is not always apparent what is the best approach to engage in the transformation. I have been using a useful mechanism called Agile streams.
9/24/2015 by Enric Lizondo
How far do your Agile teams go with their habitual retrospectives? The Agile teams I work with fall into one of the several retrospective habits, most of which don't go very far in supporting continuous improvement.