Splitting yourUser Story庖丁解牛用户故事AliHP Agile Consultant Services© Copyright 2011 Hewlett-Packard Development Company, L.P.T...
姓名: 郑立 (Ali)- HP                       敏捷服务培训经验:5年                       认证:MBA,CSM,CSP,PMP,ITIL                       Agi...
上海惠普敏捷咨询团队
Objectives Project Headaches! Why need Spilt? How to Split? • Arrange them • Split Them
Note:
Project    Headaches !Think different!6   HP Restricted | Date or Rev. #
We Built Lots of Stuff we Don’t Use One of the biggest costs of traditional development is  overproduction of features • ...
Things are happeningaround us!
The Status of Software Project    Value                        Estimation                 Requirement                  Def...
Why Need Spilt ?10   HP Restricted | Date or Rev. #
Small is to improve the Utilizationfrom Dean Leffingwell, User Story Primer
Small is Evaluable
Small is to priorities            3                2      5             4    9         8     User Story A        User Stor...
Small is to priorities   2           3   4            5   8         9        High           Medium           Low
How to Split? 庖丁解牛法16   HP Restricted | Date or Rev. #
User Story Splitting Principle and PurposePrinciple                    Purpose   Cut off the                              ...
Arrange user stories
Find out the system backbone and joint
Themes - Joint Grouping of related items in the product backlog Themes act as placeholders for product functionality    ...
Take this for example Example: Payment • Story 1: Pay by Visa Credit Card • Story 2: Pay by MasterCard                   ...
Air tickets booking history list pageWe used to: (work follow)                       Code      Design                     ...
Splitting in right wayBooking Information View - Theme                                                    User            ...
Split User Stories        Is your Knife sharp enough now?
Cut off the skin               Role       type                   Relation                                  Data           ...
Break the joint                     C                     o                     m           Story A   m   Story B         ...
Split methods   Workflow Steps   Business Rule Variations   Major Effort/Key Mechanisms   Simple/Complex   Variations...
Simple/Complex When the team is discussing a story, and the story seems to be  getting larger and larger (“what about x? ...
Workflow Steps Split the story into steps a user takes to accomplish a  workflow and then implement the workflow in incre...
Improving performance or user experiencecharacteristics Sometimes, the initial implementation isnt all that hard, and  th...
Are you ready for Split?
Thank You                          Q&A©2009 HP Confidential
庖丁解牛用户故事 (Splitting Your User Story)
Upcoming SlideShare
Loading in...5
×

庖丁解牛用户故事 (Splitting Your User Story)

1,094

Published on

Product Track
From: 郑立

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,094
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
37
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

庖丁解牛用户故事 (Splitting Your User Story)

  1. 1. Splitting yourUser Story庖丁解牛用户故事AliHP Agile Consultant Services© Copyright 2011 Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice. HP Restricted
  2. 2. 姓名: 郑立 (Ali)- HP 敏捷服务培训经验:5年 认证:MBA,CSM,CSP,PMP,ITIL Agile coaching experience : 5 years Certification: MBA, CSM, CSP, PMP, ITIL Email: Aliama0288@gmail.com Tel: 13761850288 Weibo:http://weibo.com/ali0288惠普资深敏捷顾问,曾负责并参与惠普中国敏捷流程建设和开发。并不断对敏捷在惠普中的现状进行改进。有丰富的团队辅导经验和培训经验,辅导过多个团队进行敏捷式开发。参与各项敏捷大型活动,并乐与在社区相互分享经验,通过交流学习和提高敏捷在企业中的应用。Senior Agile Consultant at HP, used to response for the HP Agile processbuilding and deployment, and always focus on continuous improvement.He has rich experience on coaching and trainings, has coached many teamstransfer from traditional to agile.He is active in many agile events, likes to share the experience with others,and learn from each other, for the purpose of improve the practical inenterprise.
  3. 3. 上海惠普敏捷咨询团队
  4. 4. Objectives Project Headaches! Why need Spilt? How to Split? • Arrange them • Split Them
  5. 5. Note:
  6. 6. Project Headaches !Think different!6 HP Restricted | Date or Rev. #
  7. 7. We Built Lots of Stuff we Don’t Use One of the biggest costs of traditional development is overproduction of features • Must be designed, built and maintained • Doesn’t get used – provides no value Feature Usage Rarely or never Rarely used: 64% 19% Never 45% Sometimes 16% Often or always Often used: 20% 13% Always 7% Source: Jim Johnson of the Standish Group at XP2002
  8. 8. Things are happeningaround us!
  9. 9. The Status of Software Project Value Estimation Requirement Defect Change Employee
  10. 10. Why Need Spilt ?10 HP Restricted | Date or Rev. #
  11. 11. Small is to improve the Utilizationfrom Dean Leffingwell, User Story Primer
  12. 12. Small is Evaluable
  13. 13. Small is to priorities 3 2 5 4 9 8 User Story A User Story B
  14. 14. Small is to priorities 2 3 4 5 8 9 High Medium Low
  15. 15. How to Split? 庖丁解牛法16 HP Restricted | Date or Rev. #
  16. 16. User Story Splitting Principle and PurposePrinciple Purpose Cut off the non-value user stories Starts from most important user stories Priorities user stories Keep User story integrated Easier to implement and test
  17. 17. Arrange user stories
  18. 18. Find out the system backbone and joint
  19. 19. Themes - Joint Grouping of related items in the product backlog Themes act as placeholders for product functionality EPIC User THEME THEME Story User User User User User User Story Story Story Story Story Story
  20. 20. Take this for example Example: Payment • Story 1: Pay by Visa Credit Card • Story 2: Pay by MasterCard Story 1 Story 2 Story 3 • Story 3: Pay by China Union Pay Ways to resolve dependencies… Becomes… Story 4 1. Combine stories into one larger independent story (Story 4) 2. Split the stories differently (one credit card, additional credit cards) Story 5 Story 6
  21. 21. Air tickets booking history list pageWe used to: (work follow) Code Design Testing Documentation ImplementOr (architecture ) Database Business UI Design Design Logic
  22. 22. Splitting in right wayBooking Information View - Theme User Age, Passport Address, Company name Add more user Contact information Informati on Search Cancel Function User Booking Name and 1 book record Filter Function Enhance Performance List all book record
  23. 23. Split User Stories Is your Knife sharp enough now?
  24. 24. Cut off the skin Role type Relation Data ship Oper status ation
  25. 25. Break the joint C o m Story A m Story B o n
  26. 26. Split methods Workflow Steps Business Rule Variations Major Effort/Key Mechanisms Simple/Complex Variations in Data Alternative Interface Options Lifecycle of an Entity (CRUD) Improving performance or user experience characteristics
  27. 27. Simple/Complex When the team is discussing a story, and the story seems to be getting larger and larger (“what about x? - have you considered y?”), stop and ask “whats the simplest that can possibly work?” Capture that simple version as its own story, and then break out all the variations and complexities into their own stories. As a traveler, I can search for flights ...specifying a max number of stops between two destinations… ...including specifying specific airports ...using flexible dates ...specifying flight timesSource: Adapted from Dean Leffingwell, User Story Primer
  28. 28. Workflow Steps Split the story into steps a user takes to accomplish a workflow and then implement the workflow in incremental stages As an online shopper I want to ...I can select my shipping address checkout my shopping cart ...I can review and confirm my order ...I can select my payment method ...I can select my shipping methodSource: Adapted from Dean Leffingwell, User Story Primer
  29. 29. Improving performance or user experiencecharacteristics Sometimes, the initial implementation isnt all that hard, and the bulk of the effort relates to making it faster, more reliable, precise or scalable. However, the team can learn a lot from a simple, quick implementation which unlocks some value for the user community in the first place. In such cases, break the epic into successive stories that add improved user experience characteristics (or “-ilities”). As a traveler, I can search for flights ...showing a “searching” animation between two destinations… (slow) ...with results shown within 3 secondsSource: Adapted from Dean Leffingwell, User Story Primer
  30. 30. Are you ready for Split?
  31. 31. Thank You Q&A©2009 HP Confidential
  1. ¿Le ha llamado la atención una diapositiva en particular?

    Recortar diapositivas es una manera útil de recopilar información importante para consultarla más tarde.

×