technical... user stories?!
TRANSCRIPT
Technical… User Stories?!
Kasia Mrowca
www.mrowcakasia.eu [email protected]
Let’s start!
Technical requirements
Part of the product
Technical requirements
Part of the product Product
Technical requirements
Sins
Problem 1: Dependency
Source: http://geek-and-poke.com/
Problem 2: Road map
Problem 2: Road map commitment
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 TOURIST I WANT TO GET TICKET PRICES
FROM DIFFERENT AIRLINES SO THAT I CAN COMPARE THE PRICES
Problem 4: acceptance criteria
Improve?
Does format matter?
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
Sequence diagram
WHY?
WHAT? WHO?
WHO?
Business Users Developers
Testers
Data Analysts
What is next?
Source: http://geek-and-poke.com/
Make a list of items!
Metrics
Keep the items that improve the situation!
∞ ÷ 2 ≈ ∞
Query response time
Current
2s
Response loading on page
Max number of rows
0,5s
5
After Refactoring
40-60% less
20% more
30% less
Compare metrics
Should we use User Stories?
Integration Data mapping
Dictionaries Frequency
Collisions
Event based vs. scheduled
Failure strategy … other
Sample
Fit it!
Fit it!
… make own type of item that reflects your needs … don’t be afraid to use fields in tool in creative way … make own template of description (DoR) … add your metrics & ways to measure ... remember that items have to be independent!
Fit it!
… make own type of item that reflects your needs … don’t be afraid to use fields in tool in creative way … make own template of description (DoR) … add your metrics & ways to measure ... remember that items have to be independent!
Fit it!
… make own type of item that reflects your needs … don’t be afraid to use fields in tool in creative way … make own template of description (DoR) … add your metrics & ways to measure ... remember that items have to be independent!
Fit it!
… make own type of item that reflects your needs … don’t be afraid to use fields in tool in creative way … make own template of description (DoR) … add your metrics & ways to measure ... remember that items have to be independent!
Fit it!
… make own type of item that reflects your needs … don’t be afraid to use fields in tool in creative way … make own template of description (DoR) … add your metrics & ways to measure ... remember that items have to be independent!
Query response t
ime
Current
2s
Response loading
on page
Max number of row
s
0,5s
5
After Refactoring
40-60% less
20% more 30% less
Wrap up
WHY?
WHAT? WHO?
Remember!
Agile is about adapting
User Stories
are not the only way you can write requirements!
Try new ways of writing down requirements
