WHY USER STORIES? Traditional Requirements Gathering: – Complex / time-consuming – Perfecting – Reluctant to change – once written – “heavy”

WHY USER STORIES? Agile User stories: – Simple, convenient – understandable – Focus on the needs of the user – Agile – “Lightweight” shifts focus from writing to conversations – Aligns to Product Vision – Breaks development into increments

WHAT? Agile User stories – Agreement between customer and developer – Format for expressing desired business value for features and functions (PBI’s) – As a I want to so that – As a I would like so that I can

CARD CONVERSATION CONFIRM 3 X 5 CARD – Small for a reason - concise – Placeholder for detailed discussions Conversations – Product Owner and developer – Ongoing Confirmation – Acceptance Criteria – Clarifies desired behavior – Understand what to build and test – Confirms Done!

PRODUCT VISION We are building BeagleTreats.com Caters to beagles with a constant need for treats All treats are taste tasted and approved by the BeagleTreats consumer representative group – represented by a Product Owner

CARD BS-#1: As a needy beagle treat consumer I want quick and easy checkout for my owner so that he/she has more time to spend with me

CONVERSATIONS Development team and Product Owner meet to develop Confirmation criteria (Acceptance Criteria)

CONFIRMATION/ACCEPTANCE Quick Order button on product page that populates “shopping cart” Large “Check Out” button on Shopping cart page. “Check Out” page pre-populated with user shipping address from user account PayPal option on “Check Out” page

AGILE DEV PROCESS SPRINT PLANNING – Review and prioritize stories/backlog DAILY STANDUP – Team status, re-plan, impediments SPRINT REVIEW – DevOps Review with Product Owner – Product Owner Acceptance