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