Allan Kelly from Allan Kelly Associates
The latest instalment of my online User Stories tutorial is now available online, User Stories by Example: Refactoring.
It takes as its starting point some existing stories and reworks them to convey their message more clearly. In the process I discuss:
The use of time-boxed spikes.
The naming of team members in user stories, e.g. “As a developer I want …” – and why this isn’t a good idea.
Rewriting user stories and breaking them down into more smaller stories. (More on this in the next tutorial.)
Why more smaller stories is better than a fewer larger stories.
How acceptance criteria can be used to split stories into smaller pieces.
and a brief look at dealing with dependencies.
Videos are intersperced with exercises and quizzes. My guess is this tutorial will take two to three hours to complete – which can be all in one go or split over days or weeks to suit yourself. As with the earlier tutorials I work through real life user stories to illustrate and draw lessons.
This is the third tutorial, it joins User Stories by Example part 1 Starting with Stories and part 2 Acceptance Criteria. The next module will look at splitting stories in more detail.
The tutorial this carries the introductory price of $49. In time this price will probably rise and I’ll introduce a combined option to buy all the courses in one go.
Please e-mail me with your comments and suggestions.
The post User Stories by Example part 3 (Refactoring) appeared first on Allan Kelly Associates.