Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
Technical…
User Stories?!
Kasia Mrowca
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?
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
IntegrationData 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
3...
Should we use User
Stories?
IntegrationData 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 ow...
Fit it!
… make own type of item that reflects your needs
… don’t be afraid to use fields in tool in creative way
… make ow...
Fit it!
… make own type of item that reflects your needs
… don’t be afraid to use fields in tool in creative way
… make ow...
Fit it!
… make own type of item that reflects your needs
… don’t be afraid to use fields in tool in creative way
… make ow...
Fit it!
… make own type of item that reflects your needs
… don’t be afraid to use fields in tool in creative way
… make ow...
Query response time
Current
2s
Response loading on page
of rows
0,5s
5
After Refactoring
40-60% less
20% more
30% less
Wra...
Remember!
Agile is about adapting
User Stories
are not the only way you
can write requirements!
Try new ways of writing
down requirements
questions
Technical... user stories?!
Technical... user stories?!
Technical... user stories?!
Technical... user stories?!
Technical... user stories?!
Technical... user stories?!
Prochain SlideShare
Chargement dans…5
×

Technical... user stories?!

789 vues

Publié le

Technical... user stories?!

Publié dans : Technologie
  • Soyez le premier à commenter

Technical... user stories?!

  1. 1. Technical… User Stories?! Kasia Mrowca
  2. 2. Let’s start!
  3. 3. Technical requirements
  4. 4. Part of the product Technical requirements
  5. 5. Part of the product Product Technical requirements
  6. 6. Sins
  7. 7. Problem 1: Dependency
  8. 8. Source: http://geek-and-poke.com/
  9. 9. Problem 2: Road map
  10. 10. Problem 2: Road map commitment
  11. 11. Problem 3: User Stories
  12. 12. Problem 3: User Stories quality
  13. 13. AS A USER <WHO> I WANT <WHAT> SO THAT <WHY>
  14. 14. AS A SYSTEM USER I WANT TO LOG IN TO BE LOGGED IN
  15. 15. AS A TOURIST I WANT TO GET TICKET PRICES FROM DIFFERENT AIRLINES SO THAT I CAN COMPARE THE PRICES
  16. 16. Problem 4: acceptance criteria
  17. 17. Improve?
  18. 18. WHY? WHAT? WHO?
  19. 19. WHY? WHAT? WHO?
  20. 20. WHY?Performance Security ‘Communication’ Maintenance Scalability Other non functional requirements…
  21. 21. Write it down!
  22. 22. WHY? WHAT? WHO?
  23. 23. WHAT?Refactoring Infrastructure Integration Bug fixing Spike
  24. 24. … and what do you need to know?
  25. 25. WHAT?Refactoring Infrastructure Integration Bug fixing Spike
  26. 26. IntegrationData mapping Dictionaries Frequency Collisions Event based vs. scheduled Failure strategy … other
  27. 27. Sequence diagram
  28. 28. WHY? WHAT? WHO?
  29. 29. WHO? Business Users Developers Testers Data Analysts
  30. 30. What is next?
  31. 31. Source: http://geek-and-poke.com/
  32. 32. Make a list of items!
  33. 33. Metrics
  34. 34. Keep the items that improve the situation!
  35. 35. ∞ ÷ 2 ≈ ∞
  36. 36. 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
  37. 37. Should we use User Stories?
  38. 38. IntegrationData mapping Dictionaries Frequency Collisions Event based vs. scheduled Failure strategy … other
  39. 39. Sample
  40. 40. Fit it!
  41. 41. 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!
  42. 42. 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!
  43. 43. 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!
  44. 44. 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!
  45. 45. 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!
  46. 46. Query response time Current 2s Response loading on page of rows 0,5s 5 After Refactoring 40-60% less 20% more 30% less Wrap up WHY? WHAT? WHO?
  47. 47. Remember!
  48. 48. Agile is about adapting
  49. 49. User Stories are not the only way you can write requirements!
  50. 50. Try new ways of writing down requirements
  51. 51. questions

×