user stories
Stories are about why not what or how
Quite popular is the “As a, I want, So that” story format. While I have seen teams do well with this format, I think it can be radically improved with a minor change. I prefer to see “So that, as a, I want” story format. My reasoning is quite simple; the emphasis is incorrect in […]
Read More
Requirements are dead. Long live requirements.
This blog post is about how to balance working with user stories in environments that are looking for something more traditional as far as requirements specifications are concerned.
Read More
User Stories are Temporary
It’s obvious, but warrants mention: What we do in the future is likely to be different from what we’re doing today. The implications for user stories should be obvious: User stories are temporary. Saving them for posterity doesn’t serve the primary purpose of user stories, and doing anything that makes them less temporary can turn […]
Read More
Writing User Stories for Web Applications
This post introduces user stories as the substitute of formal requirements documents in an agile environment.
Read More
User Stories are a Reminder to Collaborate
User stories are not a highly documented series of requirements but rather a reminder to collaborate about the topic of the user story—in other words, in agile development (good agile at least), the documentation is secondary to the collaboration. Source: “New to User Stories?“, William F. Nazzaro and Charles Suscheck, ScrumAlliance.org
Read More