user stories refactoring
TRANSCRIPT
Source: http://geek-and-poke.com/
User Stories Refactoring
www.mrowcakasia.eu [email protected]
Agenda
• Backlog items sins • Cure
Product Management sins
Problem 1: Road map
Problem 1: Road map commitment
Problem 2: Backlog
Problem 2: Backlog size
Problem 3: User Stories
Problem 3: User Stories quality
AS A USER <WHO> I WANT <WHAT> SO THAT <WHY>
AS A SYSTEM USER I WANT TO LOG IN TO BE LOGGED IN
AS A TRANSPORT PLANIST I WANT TO HAVE ALL PLANNING FUNCTIONALITY FROM
PREVIOUS SYSTEM TO EFFECTIVELY PLAN
AS A E-MAIL SENDER I WANT TO BE ABLE TO SEND EMAILS TO EFFECTIVELY
COMMUNICATE
AS A TOURIST I WANT TO GET TICKET PRICES
FROM DIFFERENT AIRLINES SO THAT I CAN COMPARE THE PRICES
Problem 4: tasks
Problem 4: tasks Meaningless?
What is the root cause of the problems?
Road map: vision ahead!
Product tree
categories (moduls)
features fur
ure
Method source: Innovation games
Love vs ROI
Love vs ROI
Love vs ROI
Metrics
∞ ÷ 2 ≈ ∞
User stories
WHY?
WHAT? WHO?
WHY?
WHAT? WHO?
WHY? Performance
Security ‘Communication’
Maintenance
Scalability
Other non functional requirements…
Write it down!
WHY?
WHAT? WHO?
WHAT? Refactoring
Infrastructure Integration
Bug fixing
Spike
… and what do you need to know?
WHAT? Refactoring
Infrastructure Integration
Bug fixing
Spike
Integration Data mapping
Dictionaries Frequency
Collisions
Event based vs. scheduled
Failure strategy … other
WHY?
WHAT? WHO?
WHO?
Business Users Developers
Testers
Data Analysts
Format?
Source: http://alanklement.blogspot.co.uk/2013/09/replacing-user-story-with-job-story.html
Source: http://alanklement.blogspot.co.uk/2013/09/replacing-user-story-with-job-story.html
Does format matter?
Feedback loop
Wrap up
Wrap up
Wrap up
Wrap up
Agile is about adapting
User Stories
are not the only way you can write requirements!
Try new ways of writing down requirements
questions
