User Story Patterns
The Business Stakeholders are Responsible for Creating the Simple Yet Effective Software Feature Request Description. The Architect team is responsible for transforming the Business User Story into a Behavior Driven Design Feature Request.
The Agile User Story
The Agile User Story pattern defines the User, Feature and the Benefit of the desired feature.
The Development Acceptance criteria is driven by the “So that” statement of the Agile User Story Pattern.
The Behavior Driven Development SpecFlow Feature Story
The SpecFlow Feature pattern is similar to the User Story just format order id different.
The Development Acceptance criteria is driven by the “In order to” statement of the Agile User Story Pattern.
The following two tabs change content below.
I am a Principal Architect at Liquid Hub in the Philadelphia area specializing in Agile Practices as a Certified Scrum Master (CSM). I use Test Driven Development (TDD) and Acceptance Test Driven Development (ATDD) with Behavior Driven Development (BDD) as my bridge to Agile User Stories Acceptance Criteria in a Domain Driven Design (DDD) implementing true RESTful services
Latest posts by Brad Huett (see all)
- DevOps: A Bridge to Your DevOps Culture - March 25, 2016
- Embracing Test Driven Development (TDD) - March 25, 2016
- DevOps: Delivering Agile Projects - March 25, 2016