Downloaded 14 times
Uploaded byKatarzyna Mrowca
Technical... User Stories?!
The document discusses various technical requirements and challenges in product development, focusing on user stories, acceptance criteria, and the importance of metrics. It emphasizes the need for adaptability in agile practices and encourages exploring alternative methods for documenting requirements. Key topics include dependency management, integration strategies, and performance optimization.
More Related Content
Similar to Technical... User Stories?!
![[Workshop] The incremental steps towards dynamic and embedded content deliver...](https://cdn.slidesharecdn.com/ss_thumbnails/2013-10-nozurbina-tekom-incremental-workshop-v2-131112075109-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![[QE 2015] Katarzyna Mrowca - Refaktoring historyjek](https://cdn.slidesharecdn.com/ss_thumbnails/3k-150603090257-lva1-app6892-thumbnail.jpg?width=640&height=640&fit=bounds)
![[ACE'14] The art of saying no](https://cdn.slidesharecdn.com/ss_thumbnails/ace-140619130630-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Technical... User Stories?!
- 1.
- 3.
- 5.
- 7.
- 8. Part of theproduct Technical requirements
- 9. Part of theproduct Product Technical requirements
- 10.
- 11.
- 12.
- 13.
- 14. Problem 2: Roadmap commitment
- 15. Problem 3: UserStories
- 16. Problem 3: UserStories quality
- 17. AS A USER<WHO> I WANT <WHAT> SO THAT <WHY>
- 18. AS A SYSTEMUSER I WANT TO LOG IN TO BE LOGGED IN
- 19. AS A TOURISTI WANT TO GET TICKET PRICES FROM DIFFERENT AIRLINES SO THAT I CAN COMPARE THE PRICES
- 20.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30. … and whatdo you need to know?
- 31.
- 32. IntegrationData mapping Dictionaries Frequency Collisions Event based vs.scheduled Failure strategy … other
- 33.
- 34.
- 35.
- 36.
- 37.
- 38. Make a listof items!
- 39.
- 43. Keep the itemsthat improve the situation!
- 44. ∞ ÷ 2≈ ∞
- 45. Query response time Current 2s Responseloading on page Max number of rows 0,5s 5 After Refactoring 40-60% less 20% more 30% less Compare metrics
- 46. Should we useUser Stories?
- 47. IntegrationData mapping Dictionaries Frequency Collisions Event based vs.scheduled Failure strategy … other
- 48.
- 49.
- 50. Fit it! … makeown 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!
- 51. Fit it! … makeown 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!
- 52. Fit it! … makeown 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!
- 53. Fit it! … makeown 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!
- 54. Fit it! … makeown 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!
- 55. Query response time Current 2s Responseloading on page of rows 0,5s 5 After Refactoring 40-60% less 20% more 30% less Wrap up WHY? WHAT? WHO?
- 56.
- 57. Agile is aboutadapting
- 58. User Stories are notthe only way you can write requirements!
- 59. Try new waysof writing down requirements
- 61.