K21 @ XP conf 2018 - Retro Poker
1 like530 views
This document describes a presentation on improving retrospective meetings using Retro Poker. It includes examples of scenarios teams may face and activities that can be used in a retrospective to engage team members and facilitate discussion. Sample scenarios involve senior developers who dislike meetings, a new senior developer underperforming, a lost intern, and an absent manager. The document promotes using Retro Poker cards to help teams inspect their process, identify improvements, and make plans to work better together. Sketches also demonstrate using a whiteboard for visualization during retrospectives.
K21 @ XP conf 2018 - Retro Poker
- 2. XP CONF 2018 Retro Poker
- 4. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
- 6. Inspect how the last Sprint went with regards to people, relationships, process, and tools; Identify and order the major items that went well and potential improvements; and, Create a plan for implementing improvements to the way the Scrum Team does its work. Scrum Guide, about the Retrospective
- 7. Inspect how the last Sprint went with regards to people, relationships, process, and tools; Identify and order the major items that went well and potential improvements; and, Create a plan for implementing improvements to the way the Scrum Team does its work. Reality about the Retrospective
- 9. #FAIL
- 10. 1 hour of retrospective per week for a 6 people team totals 312 hours a year
- 11. Life is too short to spend time on useless retrospective sessions!
- 12. SCENARIO Senior deveopers that hate meetings New Senior developer not performing as expected A lost dev intern Absent Manager
- 15. STEP 1: READ THE SCENARIO - People involved and their personality - Historical data - Perceived feelings - ... Senior deveopers that hate meetings New Senior developer not performing as expected A lost dev intern Absent Manager
- 16. STEP 2: FIND ENGAGED PEOPLE TO COLLABORATE or
- 17. STEP 3: DISCUSS BRIEFLY THE SCENARIO AND CHOOSE THE SESSION YOU WOULD APPLY TO THAT CONTEXT
- 18. STEP 4: PLAY YOUR CARDS AND DISCUSS THE RESULTS - REPEAT AS MANY TIMES AS NECESSARY -
- 19. STEP 5: SELECT THE ACTIVITY http://knowledge21.com/blog
- 20. STEP 5: OR CREATE YOUR OWN! :D
- 21. THE PAIR COLLABORATION FORMULA by Knowledge21 the sum of two individuals equals one brain times two plus the collaboration between them squared by Rodrigo de Toledo and Daniel Teixeira (in memorian)
- 27. SCENARIO 2 MOBILE TEAM IOS Developer Backend Developers Command and Control Manager Android Developer Overloaded lonely tester
- 28. SCENARIO 3 OPS TEAM All Senior Developers There is something strange on the relationship between them. New Manager
- 30. by @julibetancur at #30daysofagilesketch others opinion and point of view keep it as simple as you can to expose what you think to create and evolve retro poker is about communication allowing collaboration XP VALUES APPLIED
- 32. BRAZIL - USA - EUROPE www.knowledge21.com