participatedin team-buildingactivitiesNominatedmyself in thesprintdelegationboard for scrumactivitesexplored anew domainor featurearea.Nominatedmyself in thesprintdeploymentactivityworked extrato ensure wemet a sprintgoal.As a EpicOwner, didregularhealthcheck.proactivelycommunicatedblockers.completedall storiesassignedto me.Free!participatedin sprintplanning.celebratedateammate’ssuccess.proposeda creativesolution.worked ona criticalissue.participatedin cross-teamcollaboration.Helpedidentify rootcauses forrecurringissues.Utilized toolsorautomationto improveworkflow.worked onreducingsilos withinthe team.reviewedcode andprovidedconstructivefeedback.helpedanotherteammember.Due date andAcceptancecriteria addedbefore startingstory/iesFocused onimprovingcodereadability ormaintainability.Effectivelymanagedtime acrossmultipletasks.resolvedablocker.spilledmystory/iesimproveddocumentationfor the team.sharedknowledge withthe teamthrough a demoor session.I regularlycheck onblackduckissues forresolutionproposed aprocessimprovementfor the team.improved mytechnicalskills orlearned newthing.I regularlycheck ongreen CIhealth.workedwellwithoutTSM.proactivelyworked oncustomerissues.activelylistenedduringdiscussionsand meetingspair-programmedwith ateammate.forced meto work oncustomerissues.Worked onNFRrequirements,likeperformance,security.participatedin team-buildingactivitiesNominatedmyself in thesprintdelegationboard for scrumactivitesexplored anew domainor featurearea.Nominatedmyself in thesprintdeploymentactivityworked extrato ensure wemet a sprintgoal.As a EpicOwner, didregularhealthcheck.proactivelycommunicatedblockers.completedall storiesassignedto me.Free!participatedin sprintplanning.celebratedateammate’ssuccess.proposeda creativesolution.worked ona criticalissue.participatedin cross-teamcollaboration.Helpedidentify rootcauses forrecurringissues.Utilized toolsorautomationto improveworkflow.worked onreducingsilos withinthe team.reviewedcode andprovidedconstructivefeedback.helpedanotherteammember.Due date andAcceptancecriteria addedbefore startingstory/iesFocused onimprovingcodereadability ormaintainability.Effectivelymanagedtime acrossmultipletasks.resolvedablocker.spilledmystory/iesimproveddocumentationfor the team.sharedknowledge withthe teamthrough a demoor session.I regularlycheck onblackduckissues forresolutionproposed aprocessimprovementfor the team.improved mytechnicalskills orlearned newthing.I regularlycheck ongreen CIhealth.workedwellwithoutTSM.proactivelyworked oncustomerissues.activelylistenedduringdiscussionsand meetingspair-programmedwith ateammate.forced meto work oncustomerissues.Worked onNFRrequirements,likeperformance,security.

Sprint 173 Retrospection - PLUTO - 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
26
27
28
29
30
31
32
33
34
35
36
  1. participated in team-building activities
  2. Nominated myself in the sprint delegation board for scrum activites
  3. explored a new domain or feature area.
  4. Nominated myself in the sprint deployment activity
  5. worked extra to ensure we met a sprint goal.
  6. As a Epic Owner, did regular health check.
  7. proactively communicated blockers.
  8. completed all stories assigned to me.
  9. Free!
  10. participated in sprint planning.
  11. celebrated a teammate’s success.
  12. proposed a creative solution.
  13. worked on a critical issue.
  14. participated in cross-team collaboration.
  15. Helped identify root causes for recurring issues.
  16. Utilized tools or automation to improve workflow.
  17. worked on reducing silos within the team.
  18. reviewed code and provided constructive feedback.
  19. helped another team member.
  20. Due date and Acceptance criteria added before starting story/ies
  21. Focused on improving code readability or maintainability.
  22. Effectively managed time across multiple tasks.
  23. resolved a blocker.
  24. spilled my story/ies
  25. improved documentation for the team.
  26. shared knowledge with the team through a demo or session.
  27. I regularly check on blackduck issues for resolution
  28. proposed a process improvement for the team.
  29. improved my technical skills or learned new thing.
  30. I regularly check on green CI health.
  31. worked well without TSM.
  32. proactively worked on customer issues.
  33. actively listened during discussions and meetings
  34. pair-programmed with a teammate.
  35. forced me to work on customer issues.
  36. Worked on NFR requirements, like performance, security.