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.
8/3/2011 by Krystian Kaczor
Most of the issues with gathering requirements in agile software development and agile testing derive from issues with User Stories. Somehow expressing requirements in such a simple form causes a lot of trouble to agile teams. Of course art of writing good User Stories is the most difficult for new teams starting with a new agile project or these, which freshly transformed development methods to agile software development methodologies. Mistakes made at that point lead to wrong Test Cases, wrong understanding of requirements, and the worst of all wrong implementation which can be direct cause of rejecting the deliverables of the iteration. Lets take a look at the five most common mistakes people make writing User Stories.
8/3/2011 by James Coplien
In the past, the Scrum Guide consistently used the word "priority" for the Product Backlog or noted that the Product Backlog was “prioritized.” While the Product Backlog must be ordered, prioritization is only one technique — and rarely a good one at that. The new Scrum Guide instead uses the term ordered for the Product Backlog. This reflects long-held understanding by many leaders in the Scrum community. Let’s clarify the reason for the change.——
8/3/2011 by Ilan Goldstein CST PMP ACP
Congratulations! You’ve finally convinced the team that relative story point estimation is a great way to move forward and you’re now ready to jump into your first planning poker session. So where do you start? What’s a 1-point story? What’s a 3-point story? What’s a 13-point story? Your team is looking to you and this process is almost as new to you as it is to them.
7/6/2011 by Leopoldo Simini
“Scrum is all about delighting customers and delivering value to stakeholders.”
I have read this kind of statement since my first day working with Scrum in 2007. Even more, I’ve had the privilege of taking part on Scrum teams th...
7/6/2011 by Alan Cyment
I have heard, read, and had nightmares starring the same old question time and again: “Am I doing Scrum or not?” Generally speaking, coaches, trainers and old-timers have a very blunt and clear answer for that: “If you are follow...
7/6/2011 by Timothy Korson
Dancing with Pigs 
There are many ways to choreograph the activities within a sprint, but all of them involve intricate, dance like, interactions among testers , product owners, other team members and stakeholders. Becoming good at agile de...
7/6/2011 by Rafael Sabbagh
In the photos: (1) Chet Hendrickson and Ron Jeffries addressed the attendants during lunch; (2) Open Space session; (3) The Scrum Trainers Michael James and Nigel Baker.
Scrum Global Gathering: Seattle 2011 was held from 16 to 1...
7/1/2011 by Lisa Hoover
Submit your presentation proposal now!
6/1/2011 by Bachan Anand
The daily stand-up is a 15-minute meeting for Scrum teams. It provides an opportunity to touch base on progress toward daily commitments and sprint goals. The ScrumMaster, product owner, and all team members participate in this daily meeting. To k...
6/1/2011 by Paul Dupuy
The short short story: How long does it have to be?
Scrum teams often use user stories for backlog items. Unfortunately, one of the most important aspects of a story—its extremely short length—has been subtly transformed over time, an...