Business User Story

What are Agile User Stories?

User Stories and their Acceptance Test Driven Development (ATDD) acceptance tests specify development requirements. They are written as things that the Software Under Development (SUD) is required to accomplish for the Business Stakeholders. 

The User Story follows an established format to express the desires of a specific Business Case. User Stories must be written by the Client’s Business Stakeholders, as they have the most knowledge about the request. The User Story is the Client’s definition of success for the development of the Business Case requirements. 

A User Story is a Simple Statement of a Design Requirement instead of a Large Requirement Document  

The story communicates to the team the “WHAT” and does not specifically address anything about the “HOW”. The “HOW” is the responsibility of the development team. 

The real intention of a User Story is to provide the team with the ability respond quickly to user wants and needs. It creates less overhead in the face of rapidly changing real-world requirements or discovery of new requirements based upon the work in progress. It is not specifically a description of a feature in a program, but the underlying real world problem that the software component is designed to solve for the business user. 

The FizzBuzz Quiz User Story:

As a Development Manager

I want to have an Example of the Complete Best Practice Development Process using the FizzBuzz Quiz Test

So that my Developers have a Concrete Reference for the Acceptance Test Driven Development (ATDD) and Test Driven Development (TDD) development process using Behavior Driven Development (BDD)