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.
1/27/2015 by Mike McLaughlin
Why aren't self-organizing teams allowed to self-organize?
1/26/2015 by Anjuan Simmons
While I generally use a soft touch when helping teams transition from Waterfall development to practicing Scrum, I sometimes have to aggressively help a development team embrace the basics of Scrum. . . .
1/26/2015 by Rajeev Kumar Gupta
There is a lot of scope for any Scrum team to experiment with its activities. One such experiment can be peer feedback.
1/23/2015 by Samuel Nadarajan
I asked my project manager about areas where I could improve on the job, and I was surprised at his answer . . .
1/23/2015 by Anand Vyas
The retrospective is one of the most important ceremonies that the Scrum team performs. It is the very essence of Scrum, allowing us to "inspect and adapt." However, I often feel that new teams are lost in the retrospective. . . .
1/22/2015 by Manali Gupta
Prioritizing the backlog is very important -- but the question is why it is important and how it helps in making a quality deliverable for customers.
1/22/2015 by Vijay Bandaru
Ever since I started working in Agile, I have been observing my wife's way of working and how she manages our kids' dynamic expectations. I keep seeing ways to correlate her methods to Agile.
1/21/2015 by Niranjan Nerlige V
The role of the product owner is very important in Agile product development, especially in Scrum. Here I would like to give my perspective of the role of the product owner, based on my coaching and teaching Scrum to teams.
1/21/2015 by Meghana Niranjan Parwate
Retrospectives play a very important role, as they are that specifically planned time when the team talks about the feed-forward mechanism, looking at areas of improvements for forthcoming sprints.
1/20/2015 by Hiroshi Hiromoto Nako
A team that commits to an action plan and then executes it could be continuously improving. However, such teams have mentioned to me that they feel that they don't improve or that their retrospectives aren't helping. What's going on?