12/6/2011 by Ross Hall
User Stories provide a powerful and succinct way of managing the individual requirements that a project is expected to deliver. The theory is that by taking an approach that centres on how a person might use a system in a particular way it wil...
12/6/2011 by Maria Matarelli
Endless business requirements, desired features, market pressures… There is always more work that needs done. Sometimes, it may feel like endless sprints where you thought you saw the finish line, but every time you round the track they...
9/29/2011 by Stefan Roock
Impediments can slow down or even halt the progress of an otherwise well-functioning Scrum team. Let's take a look at the most common challenges that crop up on teams and what steps you can take to resolve them.
If the impediment bac...
9/15/2011 by Pete Behrens
As many of you already know, I am the program lead for the Certified Scrum Coaching (CSC) Program with the Scrum Alliance. As the program lead, it is my responsibility to facilitate the review process, review teams, and review application. While a relatively new program founded in 2007, our numbers are growing each year with now almost 50 Certified Coaches. However, we believe our potential and need in the industry is 10x that number. This article provides some understanding of the CSC Program and guidance for those who wish to apply.
9/7/2011 by Gavin Austin,Mysti Berry
“Originally, the methodology did not include documentation, but many organizations have figured out how to use it...” From Alyssa Fox & Meredith Kramer—Mobile and Agile:The Floating Writer's Survival Kit
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...