Keep Your User Story Simple
Trying to express too much in a user story adds confusion and increases the amount of discussion needed for developers to understand what the story really means. The post Keep Your User Story Simple...
View ArticleA User Story Expresses What, Not How
Since the birth of the Information Technology (IT) profession (and presumably even before that), developers (or builders of any kind) have been asking the business community (their customers) to tell...
View ArticleFocus on Relevant User Stories
Effective user stories are simple, well-expressed sentences that state one thing that the business needs, not how IT should develop it, and are relevant to the project. This KnowledgeKnugget™ explains...
View ArticleAvoid Ambiguity in Your User Story
The major obstacle to effective communication is ambiguity, meaning using terms and phrases that different members of your target audience will interpret differently. If your project is using an Agile...
View ArticleNon-Functional Requirements Add Value to User Stories (Part 5)
This KnowledgeKnugget(tm) presents 8 examples of typical non-functional requirements that should be part of your user stories. The post Non-Functional Requirements Add Value to User Stories (Part 5)...
View Article
