The author of this blog entry describes how user stories are insufficient for quality requirements (aka non-functional requirements) and Chris Sterling has this blog entry on how to use an “Abuse User Story” to describe the cost of not addressing quality attributes in a user story format.

This entry was posted on Wednesday, October 15th, 2008 at 10:02 pm and is filed under Agile, Collaboration, Developer, Planning, Product Owner, Scrum, User Stories, XP. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.