![]() ![]() This could be a visual annotation (figure) on the Card, or a reference to, for example, a use case and email exchange. The Conversation segment provides additional explanations relating to the user story. An actual (physical) Card (often a post-it note) with a user story on it. In short, just like with planning poker, also risk poker, besides assigning story points and risk points respectively, gains added value from conversation! Story cardįor this Wiki we have used the Ron Jeffries 3 C’s approach ( Card, Conversation, Confirmation) in order to create a story card. Nonetheless, risk poker, just like planning poker, requires a ‘whole team’ approach, which means that all team members will gain insight into, as well as achieving better understanding of, all the ‘ins’ and ‘outs’ of the various different testing tasks. The cause thereto is mostly to blame to the varying insights of the poker players in respect to the test efforts required thereto! A solution in order to achieve better understanding in respect to these test efforts as well as ascertaining a more unambiguous size estimation of a user story is achievable through playing risk poker (more specifically: ascertaining the story risk) before even starting with planning poker. Major differences are often ascertained in respect to story points assigned by different participants. ![]() Planning Poker is often used for agile approaches, such as scrum, in order to prepare an estimate relating to the size of the backlog items (for user stories for example). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |