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.
12/15/2014 by JITENDRA SINGH GOSAIN
If a team has one bad iteration or sprint there is no need to panic; the team can use the retrospective meeting to see what needs to be changed, corrected, and improved in the next sprint.
12/12/2014 by Indhu KP
Do we really handle retrospectives in the way we are supposed to? . . . Retrospectives run the risk of becoming repetitive and boring, especially when (in the case of weekly sprints) they are conducted week after week.
12/12/2014 by Somashree Bhattacharya
Stand-ups happen, burn-down charts are in place -- and suddenly, toward the end of the sprint, things start falling apart. No matter how many times you meet or try to resolve issues, the comeback is never 100 percent. You have failed your sprint.
12/11/2014 by Deepak Joshi
I would like to start with the old saying, "Don't reinvent the wheel." And really, it is an important message!
12/11/2014 by Vaishak Raitha
In terms of the service industry, while we collaborate with multiple customers, we learn to adapt and implement processes that can bring cohesiveness to teams. In many scenarios, however, we face challenges in understanding the current processes already in place for a customer.
12/10/2014 by Bhargav Ram Vedula
I am sure you all agree that rewarding an individual or a team is a great step across any platform. With my experience in Agile, I am presenting a case on how deeply we are linked to Agile in our organization and how we assess individuals and reward teams.
12/9/2014 by Krishna Sagar B V
When it comes to personal improvement, we impulsively and subconsciously follow the process to change and to improve; but when it comes to teams, we struggle to put it all together. . . . It takes a good ScrumMaster and a collaborative team to conduct effective retrospectives.
12/9/2014 by Randy Roosekrans
In the six years that I have worked as a ScrumMaster, I've often been asked if my role is truly essential, and why it should be considered an independent role within the Scrum team. "Why can't the dev manager also perform as the ScrumMaster? Or one of the developers? Or a QA tech?"
12/8/2014 by Ebin Poovathany
I read this quote again today: "First they ignore you, then they laugh at you, then they fight you, then you win." . . . This statement has impacted me very deeply.
12/8/2014 by Bobby Mathew
With the advent of Agile/Scrum methods in project execution, many of the . . . key skills that a project manager was singularly proud of have gradually become less crucial.