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.
7/29/2015 by Kapil Goel
Agile software development is like building a new house or maintaining an existing house. With every unit of code we add to the system, we keep adding technical debt.
7/28/2015 by Arvind Kaul
Over the years I've often come across situations in which the team delivered a more complicated final product than necessary or desirable. Using Scrum, however, we uncover these misunderstandings much earlier -- and avoid them.
7/28/2015 by Santosh Shaastry
Ideally, technical debt must be as minimal as possible. The reality is that it increases linearly with the number of sprints completed. How are we to manage technical debt?
7/27/2015 by Sumit Sharma
The daily stand-up has several clear goals, and some common pitfalls as well.
7/27/2015 by Amit Agarwal
Several common traps can affect Scrum teams, and if they go unresolved they can affect the Scrum cycle, team morale and productivity, and product owner expectations. Here's how to tackle them.
7/24/2015 by Venkatesh Jagannathan
Although Agile's inner workings are complicated, we should realize and understand them cognitively instead of just following them blindly out of determination.
7/24/2015 by Arvind Kaul
Next time you're looking for a ScrumMaster, consider these two important qualities.
7/23/2015 by Eduardo Ribeiro
Agile adoption can be a real Twilight Zone for many people, holding them back from full adoption and creating anti-patterns that cause Agile to fail. Here are some ways I try to help in these situations.
7/23/2015 by Andy Deighton
Do we suffer from an overreliance on tools -- one that distracts us from an important concept in the Agile Manifesto?
7/22/2015 by Damien Corbishley
After adopting Scrum, we made massive improvements in our organization -- but the interface with our outsourcing partner was becoming fragile. Here's how we helped bridge the gap.