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.
6/5/2015 by Ankush Sabharwal
Here are the core XP practices that I believe are most important to pursue, along with sound knowledge of Scrum.
6/4/2015 by Garren Heye
When a company begins its transformation to Scrum, the biggest challenge is the cultural shift required. You can do many things to make this cultural shift smoother, but here is one extremely effective strategy.
6/4/2015 by Shalu Tyagi
At InterGlobe Technologies (IGT), we've come a long way since embarking on our journey of Agile implementation -- and we've learned the following critical lessons during our transition.
6/4/2015 by Dharmendra .
Adoption of Agile creates a major challenge in a typical R&D (research and development) environment. I offer the following recommendations help establish the right mind-set for an R&D team.
6/3/2015 by Sandip Saha
As ScrumMasters, we've all faced the challenge of trying to conduct effective sprint retrospectives in Agile. It's not easy to probe team members and help them share their concerns openly. So what can you do?
6/3/2015 by Nigel Thurlow
One of the challenges coaches find with Scrum teams is their lack of discipline in observing the required meetings and schedules. I am sharing a simple and visual way to help with this, one my teams love and use.
6/3/2015 by Ebin Poovathany
Let us take a closer look at software projects and the Definition of Done (DoD). A common understanding within the team is necessary, but is it sufficient?
6/2/2015 by Daniel Arrais
Neste artigo irei contar um pouco sobre minha experiência utilizando o planning poker e seus ganhos.
A burn-down chart represents work left to do versus time available. It helps clarify whether the project is at risk. But I believe you don't need a chart to tell you these things.
6/2/2015 by Krishnaswamy Babu
An argument against emergent design is the possibility that it can lead to poor designs. An intelligent product owner can take charge and prevent these poor designs -- but how does he or she do it?