Complementing User Stories
User stories are well established in agile software development processes, but they should not be seen as detailed requirements specifications. It is accepted that the end users do not know all the requirements at once. Therefore, user stories only give hints about the expectations of an end user. A computer supported strategy is proposed to […]
Read More
Visual Models for Software Requirements
Software requirements are often thought to be textual material that can take the form of free “system shall…” statements, user stories, or “give when then” of behavior driven development. This blog post explore the usage of visual models to capture software requirements. It explains that models are not requirements, but they help us find and […]
Read More
How to Split User Stories
George Dinwiddie proposes a list of material that should help you in the task of splitting user stories used to manage requirements in Agile approaches. In his own handout, he explains the difference between stories in the backlog that are often called features or epics and stories selected for development that should generally be small […]
Read More
Managing Agile Requirements
People often believe that Agile software development requires not documentation. Even if the Agile Manifesto values “Working Software over Comprehensive Documentation”, you should note the word “over” in this statement. The Manifesto is not recommending no documentation, but stating a preference for working software over documentation.
Read More
User Stories Acceptance Criteria
In Scrum user stories are the starting point of a conversation. This articles discusses the challenge for the Product Owner to provide acceptance criteria to help the Scrum team understand user stories. The author explains that acceptance criteria need not constitute an exhaustive list, but they should be sufficient to move forward. Acceptance criteria are […]
Read More
Using Use Cases or User Stories in Scrum
This blog post defines the concept of use cases and user stories and discusses how and when they should be used in an Agile software development project. User stories are different from use cases because they are centred on the result and the benefit of the thing you’re describing, whereas use cases are more granular. […]
Read More