Three bad examples of user stories:

“As a developer, I want to integrate with other system in an IntegrationEnvironment, So that I can test the Integration”

“As a project team, we want to setup SharePoint, So that we can share documents”

“As a developer we want TFS as a build server, so that we can build code automatically”

I experienced lots of projects where we had those and those are a huge problem! They go in the same direction as the smell of having a “Sprint 0”

Read More

From “Gilb’s Mythodology Column: User Stories: A Skeptical View by Tom and Kai Gilb”, an article from the AgileRecord. 
Full PDF download here: http://www.gilb.com/tiki-download_file.php?fileId=461

Read More

From “Gilb’s Mythodology Column: User Stories: A Skeptical View by Tom and Kai Gilb”, an article from the AgileRecord. 
Full PDF download here: http://www.gilb.com/tiki-download_file.php?fileId=461

Read More

In my daily life as a team member I see the backlog not being ready as the biggest problem in all projects…

Nice blog post about User Story Basics from Charles Bradley.

What is a User Story?
http://scrumcrazy.wordpress.com/2012/05/03/user-story-basics-what-is-a-user-story/

And remember the 3 ‘C’s: Card, Conversation and Confirmation

Ron Jeffrey on Essential XP: Card, Conversation, Confirmation
http://xprogramming.com/articles/expcardconversationconfirmation/

The XP Circle of Life helps keep projects alive. A key aspect of this cycle is the Acceptance Test. Acceptance Tests are critical to communication among team members, especially between customer and programmer.