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.
11/3/2015 by Randy Wilk
In transforming my organization from Waterfall to Agile, one of my biggest challenges was moving from function-based teams to cross-functional, feature-based teams. I thought I would share my story for others looking to do the same.
11/3/2015 by Bhargav Ram Vedula
This article discusses some of the metrics that I have come across recently that are anti-Agile patterns. I would like to highlight them and elicit your comments and suggestions.
11/2/2015 by Simas Torgovickis
Does everyone on your team have the same definition for sprint success? Because individual definitions can vary, it's worth coming up with a standard for your team.
10/30/2015 by Kenneth Adams
Transitioning to Scrum is a paradigm shift, and not necessarily an easy one. This article discusses some lessons learned through pain and triumph and tries to boil them down to a few do's and don'ts.
10/29/2015 by Remya Agrasala
At a training session, I realized with a shock that I was not doing my team justice as a ScrumMaster -- our retrospectives were boring. Here are some ways we found to make them more interesting.
10/28/2015 by Alan Zucker
Peter Drucker is known as the father of modern management. Did he presage Agile in the 1950s?
10/27/2015 by Santosh Shaastry
We've all experienced the danger of the Daily Scrum devolving into a status meeting. Here's one way our team has found to prevent that from happening.
10/23/2015 by K Pawan Kumar
Agile and DevOps go hand in hand, but are there any specific considerations to ensure a successful collaboration between development and Agile operations?
10/22/2015 by Poornaselvan Kittu Jeevanandam
Contracts have deep consequences for every enterprise's budget. When writing a contract, what units can we use that easily extrapolate to ROI?
10/20/2015 by Leonel Zapien Lopez
What I have experienced is that there is a very thin line between changing requirements versus lack of proper definition of stories and acceptance criteria that can lead to scope creep, even in an Agile environment.