DSUHigh TeamcooperationChallengingWorkEnvironmentStaleUserStoryBusinessExpectationsAre ClearClarityin RallyStoriesBacklogRefinementTeamAlignment?RecognitionTrainAlignment?EffectiveEstimationIterationPlanningOpennessto newIdeasOvercommittingCompromise ofquality due toimposeddeadlines,scope, orresourcesInjections/UnplannedWorkTo littlemeetingsSolutionsimposed by anon-engineer/architectCulture ofLearning isengrained toour programClearSprintGoalsTomuchWIPPairedProgrammingPRWatcherDeploymentshappeninglate in theSprintWhat is aDefinition ofDone /AcceptanceCriteriaDSUHigh TeamcooperationChallengingWorkEnvironmentStaleUserStoryBusinessExpectationsAre ClearClarityin RallyStoriesBacklogRefinementTeamAlignment?RecognitionTrainAlignment?EffectiveEstimationIterationPlanningOpennessto newIdeasOvercommittingCompromise ofquality due toimposeddeadlines,scope, orresourcesInjections/UnplannedWorkTo littlemeetingsSolutionsimposed by anon-engineer/architectCulture ofLearning isengrained toour programClearSprintGoalsTomuchWIPPairedProgrammingPRWatcherDeploymentshappeninglate in theSprintWhat is aDefinition ofDone /AcceptanceCriteria

Rally Retro - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
  1. DSU
  2. High Team cooperation
  3. Challenging Work Environment
  4. Stale User Story
  5. Business Expectations Are Clear
  6. Clarity in Rally Stories
  7. Backlog Refinement
  8. Team Alignment?
  9. Recognition
  10. Train Alignment?
  11. Effective Estimation
  12. Iteration Planning
  13. Openness to new Ideas
  14. Overcommitting
  15. Compromise of quality due to imposed deadlines, scope, or resources
  16. Injections/ Unplanned Work
  17. To little meetings
  18. Solutions imposed by a non-engineer/architect
  19. Culture of Learning is engrained to our program
  20. Clear Sprint Goals
  21. To much WIP
  22. Paired Programming
  23. PR Watcher
  24. Deployments happening late in the Sprint
  25. What is a Definition of Done / Acceptance Criteria