Group items tagged

As a … I want… so that…” is a new-fangled user story format. The original XP user story format had no rules, so you could simply highlight any phrase in a use case and call it a user story. Personally, I feel sorry for anyone who has to write “As a… I want… so that…” for 200 user stories. Kind of like being kept after school and having to write “I will not write silly user stories in class” 100 times

A use case pretty much by definition contains multiple stories. A use case is a collection of scenarios related to the primary actor’s goal – some scenarios show the actor interacting with the system and the system interacting with other systems so that they succeed with the goal, some show failure. That’s all in the nature of a use case. see Structuring use cases with goals (discussion: Re: Structuring use cases with goals) from 1995. A use case written for this will occupy between half a page for a shortish one to 2 pages for a long one. A user story is a nickname for a single scenario – it contains neither the information content of the scenario nor failure or alternate paths. A user story typically occupies 1/2 to one sentence no matter its size.

(p.s. Agile was supposed to reduce bureaucracy and overhead, not add to it. :) Alistair

This course will teach you the very basics and foundation of BDD along with examples & workflow

You will learn and witness how BDD starts in an Organization along with a BDD Workshop

What are the different phases of BDD, BDD in Sprints and Agile Teams, BDD Roles and Responsibilities

TDD34-8£60,000-6,064 (6.48%)1,470

BDD109-29£60,000+3.44%2,823 (3.02%)607

User Experience43+8£55,000-5,279 (5.65%)1,045

Gherkin

test automation

The Big BDD Picture: The main goals of BDD are collaboration and automation

Unlike actors, personas are not roles which people play

Personas are different because they describe an archetypical instance of an actor.  In a use case model we would have a Customer actor, yet with personas we would instead describe several different types of customers to help bring the idea to life.

first introduced by Alan Cooper

indicating the priority of stories, as well as their relation to each other and the larger goals of the users

SPIder is een Nederlands netwerk van IT-professionals waarin kennis en ervaringen gedeeld worden op het gebied van software­ontwikkelmethodieken, processen en modellen, (software)­procesverbetering (SPI), kwaliteit, kwaliteitsboring (QA), ontwerp en test, metrieken en invoeringstrategieën

examined the effectiveness of use cases;

two fundamental observations

Trends

Low Cost, Low Maintenance

Niche Specialisation