Pages

Thursday, December 5, 2013

Agile Team Practices with Scrum

User Story recipe:

As a  I want  so that 

  • As a <traveller> I want to <reserve> a hotel room. so that <I have a place to stay
  • As a <vacation planner> I want to <see picture of Hotel> a hotel room. so that <I have better decision

**) Use Role not user

**) Each user story will create more questions and more requirements, in this case we can create a work item, and list all the new requirements under the user story, or simply create more user stories

**) Detail sub stories may be the best



Testing requirements in a user story formula:

Given [and more context],
When
Then [and other outcomes]

For example

Given I am a premium member 
When I canceled under 24 hours
Then I incurred no penalty 


Given I am non-a premium member 
When I canceled under 24 hours
Then I pay 50%

Given I am site member 
When I canceled my reservation
Then I will receive a confirmation email


**) Now per each main user story or work item, it will be good to have a title like
(User cancels reservation)

**) we can name the validation, or test requirements (Given, when that) as scenarios

**) All scenarios can be turned to an automatic tests


Story Card:

Story Title:
Story Description:As a  I want  so that 

Success Criteria
  • Given [and more context],
    When 
    Then [and other outcomes]
  • Given [and more context],
    When 
    Then [and other outcomes]
  • Given [and more context],
    When 
    Then [and other outcomes]


----------------------------





No comments:

Post a Comment