《User Stories Applied》的笔记-第75页
- 章节名：guidelines for good stories
- 页码：第75页 2016-04-02 15:59:43
- start with goal stories - slice the cake- write closed storiesa far better approach is to write the replacement stories such that each provides some level of end to end functionality- put constraints om cards- size the story to the horizon focus on one and expand , then expand another (trawl stories required as below) - role modeling via brain storm an initial set of user roles, organize the initial set, consolidate roles, refine the roles.) - gather stories via techs as user interviews, questionnaires, observations, story-writing workshopsa closed story is one that finishes with the achievement of a meaningful goal and that allows the user to feel she has accomplished sthconcerns for #11 & 13#11: The customer indicates the customer user proxy like BA or actual customer? very seldom the real customer will help to write the story ? also, if they wrote, then the key concern is how to ensure the understanding between customer & BA is correct, so product owner can pass this correct to devs?#13: agree of not mention feature abstractly. the thing is that we can use number and make this still concrete for talking about; and this makes thinks easy to maintain or track on several places - like story & jira & action list etc,Summaries: 1. To identify stories, start by considering the goals of each user role in using the system 2. When splitting a story, try to come up with stories that cut through all layers of the applications; 3. Try to write stories that are of a size where the user feels justified in taking a coffee break after completing the story 4. Augment stories with other requirememts gathering or documenting techniques as necesar for the project's domain and environments 5. create constraint cards and either tape them to a shared wall or write tests to ensure the constraints are not violated 6. Write smaller stories for functionality the team will implement soon, and write broad, high-level stories for functionality further into the future 7. Keep the user interface out of the stories for as long as possible 8. When practical, include the user role when writing the story 9. Write stories in active voice. 10. Write stories for a single user 11. Have the customer rather the developer write the story 12. Keep user stories short, and dont forget their purpose as reminders to hold conversations 13. dont number story cards
襄对本书的所有笔记 · · · · · ·
summary: - estimating stories in story points, which are relative estimates of the compl...
说明 · · · · · ·