Clik here to view.
ScrumMaster Tales – Waiting Too Long to Create Acceptance Criteria
The recent Backlog Refinement session helped split the upcoming User Stories. The team was able to get from a very large Story: “As a first time book buyer I want to read a trustworthy review before I...
View ArticleClik here to view.
ScrumMaster Tales: The Team Collaborate on Acceptance Criteria
Image Credit: robinsonma http://www.sxc.hu/photo/917101 The team has just completed Sprint Planning, committing to four stories: As a first time book buyer I would like to read a review so I can see if...
View ArticleClik here to view.
ScrumMaster Tales: Technical User Stories or The Team Try to Pull a Fast One...
While working on the FedEx 2-day shipment story Martin discovers some very crufty code in the Foobar class. He doesn’t need to work in the class to complete the story, nor can he see it causing any...
View ArticleClik here to view.
Learning Story Mapping Through Exercises
Attendees in Kitchener Waterloo – collaborating on building their Story Maps. Story Mapping is a simple tool to help you visualize your Product Backlog. The traditional Product Backlog in Scrum is a...
View ArticleClik here to view.
Don’t Gamble on User Stories Alone, Specify by Example
Traditional requirements approaches don’t work, but user stories are not enough. So, what does work? Testable examples (i.e. ATDD and BDD) aka Specification By Example. Testable examples, sometimes...
View ArticleClik here to view.
Story Splitting – a Play – “Spike Sherman”
User Stories are a common tool used by Agile Teams to capture the spirit of a requirement without too much detail. Sometimes User Stories are too large for the team to complete safely in one Sprint. In...
View ArticleClik here to view.
Lifecycle of a User Story
User Stories are often used as a lightweight form of Agile requirement. Their goal is to replace heavy weight-specification documents with “a Card, a Conversation and a Confirmation”. When people...
View ArticleClik here to view.
ScrumMaster Tales – Product Backlog Refinement in Action
The ScrumMaster Tales is a series of stories about ScrumMaster John who attended one of my courses. He is the ScrumMaster for the WorldsSmallestOnlineBookstore. Learning from past mistakes, Product...
View ArticleClik here to view.
ScrumMaster Tales – The Trouble with Sprint Burndowns
It’s six Sprints after the “Overtime/Disastrous Release”, which set the team back by several months. During the current Sprint Planning, the Team committed to completing the following nine User...
View ArticleClik here to view.
Definition of Done vs. User Stories vs. Acceptance Criteria
Definition of “Done” The ScrumGuide says that: “When a Product Backlog item or an Increment is described as ‘Done’, everyone must understand what ‘Done’ means.” I can promise you, that sentence and the...
View Article
