ResourcesdisappearImport/exportis wrongDatachangesafterrefreshFindanothergantt bugRewritebigmethodprogramcrashesrandomlyGroupbyissues+/- 1issueParentcalculationis wrongInfiniteloopPlaceholderis brokenTabnavigationis brokenAutosched notworkingrightWorkstreamentitysummary iswrongInfiniteloopWormreappearsCopypasteissuesgantt tasknot founderrorPerformanceissuesSomethingunrelatedbreaksNobodyunderstandshowconstraintsworkMilestonesare brokenWBSbreaksnobodyunderstandshow criticalpath worksResourcesdisappearImport/exportis wrongDatachangesafterrefreshFindanothergantt bugRewritebigmethodprogramcrashesrandomlyGroupbyissues+/- 1issueParentcalculationis wrongInfiniteloopPlaceholderis brokenTabnavigationis brokenAutosched notworkingrightWorkstreamentitysummary iswrongInfiniteloopWormreappearsCopypasteissuesgantt tasknot founderrorPerformanceissuesSomethingunrelatedbreaksNobodyunderstandshowconstraintsworkMilestonesare brokenWBSbreaksnobodyunderstandshow criticalpath works

Scheduling Engine Bingo - 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
  1. Resources disappear
  2. Import/export is wrong
  3. Data changes after refresh
  4. Find another gantt bug
  5. Rewrite big method
  6. program crashes randomly
  7. Group by issues
  8. +/- 1 issue
  9. Parent calculation is wrong
  10. Infinite loop
  11. Placeholder is broken
  12. Tab navigation is broken
  13. Auto sched not working right
  14. Workstream entity summary is wrong
  15. Infinite loop
  16. Worm reappears
  17. Copy paste issues
  18. gantt task not found error
  19. Performance issues
  20. Something unrelated breaks
  21. Nobody understands how constraints work
  22. Milestones are broken
  23. WBS breaks
  24. nobody understands how critical path works