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.
10/9/2015 by Amir Nasiri
At some point, all project managers think about this question once they've been introduced to Agile methods such as Scrum.
10/8/2015 by Sathya Narayana Kaliprasad
Coaching can be as much learning as teaching. Over time I've discovered specific types of team members who need specific types of coaching, as well as how to use my experiences to help the team.
10/8/2015 by Ebin Poovathany
When it comes to software development, we tend to lose our common sense, and we get into the business of delivering half-baked cakes.
10/7/2015 by Samantha Webb
When we started out on our Scrum journey, sprint planning was always painful. We soon learned that the key to good sprint planning was in a good product backlog refinement process, which I share here.
10/6/2015 by Poornaselvan Kittu Jeevanandam
Organizations adopting Scrum have business analysts, business systems analysts, systems analysts, and architects, among many other titles. Who among these is best suited for a delivery team's product owner role?
10/6/2015 by Bajrang Bahadur
When I worked for several years as a traditional project manager, I used to think I knew how to manage a project. I thought controlling everything was the best way to manage it. . . .
10/5/2015 by Upesh Amin
As a software engineer with a martial arts background, I see many parallels between Scrum and the martial arts style that I practice.
10/5/2015 by Suman Bhowmick
A retrospective is one of the core events of Agile practices. But for most teams, retrospectives are not as effective as they should be. Here are the five major symptoms of ineffective or dysfunctional retrospectives.
10/2/2015 by Kirthika Sankar
Why should we have retrospective meetings after every sprint or iteration? I have observed that some project teams skip the retrospective process, thinking that they save time by doing so. However, this only creates adverse effects.
10/2/2015 by Andreas Aubell
In a feature-driven environment, one in which "good enough" is good enough, I find that sometimes we don't look at our product and ask, "Does it really stand out from the crowd?"