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/13/2016 by Gene Gendel
Causal loop diagrams provide a great way to graphically illustrate cause-and-effect relationships between various elements of an organizational ecosystem. I have found that they are highly useful in communicating ideas to my customers, particularly to senior leadership.
7/13/2016 by Ramesh Lakkaraju
In any product development, it is often perceived that documentation plays second fiddle to development in Agile. In fact, in today’s world, both these domains play a key role in the success of a product. So, what exactly is this type of documentation?
7/12/2016 by Alhad Akole
I graduated in industrial engineering way back in 1999. Looking at the underlying topics, methods, and principles that we learned, I see now that they were very much part of today's Agile way of working.
7/11/2016 by Alex DiPasquale
Any time we write code, there is a chance we will create a defect. Sometimes, when working a user story, we find a production defect. How my team handles production defects has evolved as we have matured in Agile.
7/11/2016 by Leza Zaman
Through mainstreaming, key principles of Agile and Scrum have become diffused. My recent encounter with a well-known agency provides a good case study of many of the problems I see when Scrum is introduced and implemented in a diffused or mutated state.
7/8/2016 by Sandip Saha
Agile is the backbone of a continuous delivery practice. What else does the team need, and why?
7/8/2016 by Anil Jaising
Every Scrum sprint should deliver a minimum viable product. But I often find that sprints go by and the deliverable is not tested or is not integrated.
7/7/2016 by Robin Hackshall
A skill that development team members should be able to display is that of being resourceful thinkers. A resourceful thinker has the characteristics described in this article.
7/7/2016 by Sandeep Mukkara
How will we ensure continuous flow of delivery with business value when our release cycle time is three weeks or more? It is only possible if our change process is continuous or automated.
7/6/2016 by Gilberto Urueta Sanroman
If your team is having problems and you want to bring Scrum back to life, maybe the best thing to do is to let it "die" first, and then bring it back to life by using a new name or metaphor.