I had to do Bell U Learning I had to play Alvaro's AWESOME games 70/30 split is better than 60/40 I have had to break down stories wrt acceptance criteria I had to invite on a need-to-be there basis I had to create fork-off logo! I have timedout on WebEx I want a new MVP process- MVP1- MVP2-RC No story will move into development unless it is clear & has a TO-DO list Add weights to TO-DOs I had to establish a team agreement 1 day = 2 points over 1 day = 4 points 60/40 split is better than 70/30 Add PO to ticket I have had to break down tickets into TODOs I had to work on one story at a time I have frozen on slack I have had to guestimated weight of ticket Setup meetings in advance I have had to qualify unplanned work Minimize dependencies within tickets sprint Develop a plan to monitor applications in prod I have had to implement code review Take only 50% of points available I have anticipated roadblocks during planning I have had to limit meeting times Code monitoring plan Break down stories when they cross allocated time 1 day = 4 points over 1 day = 2 points I had to do Bell U Learning I had to play Alvaro's AWESOME games 70/30 split is better than 60/40 I have had to break down stories wrt acceptance criteria I had to invite on a need-to-be there basis I had to create fork-off logo! I have timedout on WebEx I want a new MVP process- MVP1- MVP2-RC No story will move into development unless it is clear & has a TO-DO list Add weights to TO-DOs I had to establish a team agreement 1 day = 2 points over 1 day = 4 points 60/40 split is better than 70/30 Add PO to ticket I have had to break down tickets into TODOs I had to work on one story at a time I have frozen on slack I have had to guestimated weight of ticket Setup meetings in advance I have had to qualify unplanned work Minimize dependencies within tickets sprint Develop a plan to monitor applications in prod I have had to implement code review Take only 50% of points available I have anticipated roadblocks during planning I have had to limit meeting times Code monitoring plan Break down stories when they cross allocated time 1 day = 4 points over 1 day = 2 points
(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.
I had to do Bell U Learning
I had to play Alvaro's AWESOME games
70/30 split is better than 60/40
I have had to break down stories wrt acceptance criteria
I had to invite on a need-to-be there basis
I had to create fork-off logo!
I have timedout on WebEx
I want a new MVP process-MVP1-MVP2-RC
No story will move into development unless it is clear & has a TO-DO list
Add weights to TO-DOs
I had to establish a team agreement
1 day = 2 points over 1 day = 4 points
60/40 split is better than 70/30
Add PO to ticket
I have had to break down tickets into TODOs
I had to work on one story at a time
I have frozen on slack
I have had to guestimated weight of ticket
Setup meetings in advance
I have had to qualify unplanned work
Minimize dependencies within tickets sprint
Develop a plan to monitor applications in prod
I have had to implement code review
Take only 50% of points available
I have anticipated roadblocks during planning
I have had to limit meeting times
Code monitoring plan
Break down stories when they cross allocated time
1 day = 4 points over 1 day = 2 points