User stories and decomposing requirements
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

User stories and decomposing requirements

on

  • 462 views

 

Statistics

Views

Total Views
462
Views on SlideShare
462
Embed Views
0

Actions

Likes
1
Downloads
5
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

User stories and decomposing requirements Presentation Transcript

  • 1. USER STORIES & DECOMPOSING REQUIREMENTS
  • 2. WHAT IS A USER STORY? • A REGULAR STORY IS ABOUT SOME PERSONS, THEY ARE IN A SITUATION, SOMETHING HAPPENS THAT IS INTERESTING, THEN THERE IS AN OUTCOME AND AN END • SOMETIMES THERE IS A MORAL OR SOME RATIONALE FOR IT ALL • USER STORIES ARE STORIES ABOUT A USER OF OUR PRODUCT. THERE IS A SITUATION, THE USERS DOES SOMETHING AND THE PRODUCT RESPONDS GIVING THE USER SOME RESULT (HOPEFULLY OF SOME VALUE)
  • 3. WHAT IS A USER STORY? • A USER’S NEED • A PLANNING ITEM • A REQUIREMENT • A (CHUNK OF) PRODUCT DESCRIPTION • A COMMUNICATION TOOL • A DISCUSSION OPENER
  • 4. USER STORY FORMATS FOCUS ON THE BUSINESS GOAL •TITLE •IN ORDER TO <BUSINESS GOAL> •AS <A ROLE> •I WANT <FUNCTIONALITY>
  • 5. USER STORY FORMATS FOCUS ON THE ROLE •TITLE •AS <A ROLE> •IN ORDER TO <BUSINESS GOAL> •I WANT <FUNCTIONALITY>
  • 6. WHY USER STORIES? • USER STORIES PROMOTE TRANSPARENCY BEING INTUITIVELY UNDERSTANDABLE FOR ALL INVOLVED (USUALLY ALSO FOR STAKEHOLDERS) • HELP FOCUS ON THE USER AND VALUABLE BUSINESS OUTCOMES • HELP START DISCUSSIONS – BUT ALSO HELP CAPTURE THEIR OUTCOMES
  • 7. ACCEPTANCE CRITERIA FORMAT •GIVEN <STARTING CONDITIONS> •WHEN <EVENT> •THEN <RESULT> CAN ALSO BE USED TO DESCRIBE REQUIREMENTS, ESPECIALLY FOR SYSTEMS WITHOUT HUMAN USERS.
  • 8. TYPES OF LARGE STORIES • COMPOUND STORIES - USUALLY MADE UP OF SEVERAL SMALLER STORIES • COMPLEX STORIES - USUALLY INHERENTLY LARGE STORIES, OFTEN BECAUSE THERE IS SOME UNCERTAINTY ABOUT WHAT NEEDS TO BE DONE.
  • 9. BREAKING DOWN USER STORIES • CRUD – CREATE, READ, UPDATE, DELETE • ACCEPTANCE CRITERIA – SEPARATELY POSITIVE SCENARIO, NEGATIVE SCENARIO, EXCEPTIONS ETC. • DECISION TREES – CONSIDER, THEN IMPLEMENT BRANCHES • WORKFLOW STEPS – WORKFLOW SEQUENCE ONE BY ONE • NONE, ONE, MANY – CONSIDER SEPARATELY SIZES • EXTERNAL (INCREMENTAL) QUALITY – GRADUALLY IMPROVE UI, PERFORMANCE ETC. • “SPIKES” – TIME-BOXED EXPLORATION
  • 10. SOURCES • “GROWING AGILE” – BLOG POST ABOUT BREAKING DOWN REQUIREMENTS • HTTP://GROWINGAGILE.CO.ZA/2012/12/BREAKING-DOWN-USER- STORIES/ • “PATTERNS FOR SPLITTING USER STORIES” – RICHARD LAWRENCE • HTTP://WWW.RICHARDLAWRENCE.INFO/2009/10/28/PATTERNS- FOR-SPLITTING-USER-STORIES/ • “USER STORIES APPLIED” – MIKE COHN, 2004 ISBN 978-0321205681
  • 11. WWW.CODESPRINTERS.COM THANK YOU