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.
9/3/2013 by Matt Gilliland
Scrum and other Agile frameworks don't have an explicit method for highlighting and handling certain types of risks. . . . For instance, risks around dependencies on other projects, features, stories, decisions, teams, etc., plus market risk, are difficult to account for.
9/3/2013 by Glen Wang
The Agile Manifesto says that the best architectures, requirements, and designs emerge from self-organizing teams. The Scrum Guide says that self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. But how about letting the team self-organize to reward itself?
9/2/2013 by Francesco Attanasio
Sooner or later comes a time to coach people one-on-one. . . . In my experience as a ScrumMaster, when it happened for the first time, I wasn't ready.
8/30/2013 by Ashish Mahajan
Yellow or dry leaves on a tree have more to do with its root than its color; they're an indication of the need to water the roots. For a tree to flourish, to bear green leaves and fruit, it's the root that needs to be watered. . . . Here are some of the things that, I believe, are watering the Tree of Product Development so that it will bear the fruits of success.
8/29/2013 by Jorge Hernán Abad Londoño
A continuación comparto mi lista de verificación al momento de revisar una historia de usuario. Luego de hacer la CCC (Card, Confirmation, Conversation), definitivamente el más criterio más importante que uso es cumplir INVEST. . . .
8/29/2013 by Brock Argue
I spent the better part of a recent Sunday afternoon (when I should have been watching golf) in my backyard, pulling weeds out of my gardens. How does this happen, I wondered?
8/28/2013 by Knut Kvarme
There is a common perception that the co-located team is better positioned to ensure good communication and deliver more efficiently than distributed teams. But . . . it is interesting to note that while there are some clear challenges with having a distributed team, there can also be some advantages.
8/28/2013 by Andrea Gigante
We know that a prioritized backlog helps us understand what to do next, but sometimes it's difficult to grasp where we are and where we should go -- especially if we just dive into a big project that's been started, with hundreds of stories and/or issues already created. To solve these situations, I have found it very useful to manage the road map and backlog with the help of a story map.
8/27/2013 by Gopal vadrevu
The following "Introduction to Scrum" is my open presentation on the basics of Scrum for beginners. . . .
8/27/2013 by Catia Oliveira
Nowadays lots of people wonder why they should build a backlog and why it should be on a real board rather than an electronic one. Here are some thoughts I would like to share with you, and I would like to have your opinions on this matter. . . .