PE wantsATE tocharacterizethe unitsSarah finds atest issue butit's actually adatasheetissueIt's atimingissueThe unitsaremanuallyapprovedPE gives youa unit thatdoesn't workComponentEngineeringwants acustom testprogramHong sendsan e-mailending with"Pleaseadvise."Rahuldoesn'tbelieve it's acomponentissueOutlookgoesdownA newoperatorneeds to beadded to thedatabaseChris asks,"Did you puta scope onit?"Heatherexpeditesan ECOEduardawalks intoour area andsays, "Knockknock"Paulwants tocleansomethingQ&Rneeds toclear aflagProductEngineeropens acontainmentfor limitsIt took morethan 6 e-mailsto resolve asimpleproblemThe unitspass onretestPaulcomplainsaboutsomethingLisa needsall units fora "verylate" orderOperatorused thewrongfixtureTom asksaboutupgradingTestStandUnitshave tobe testedupstairsNPI needshelp withinductancePE wantsATE tocharacterizethe unitsSarah finds atest issue butit's actually adatasheetissueIt's atimingissueThe unitsaremanuallyapprovedPE gives youa unit thatdoesn't workComponentEngineeringwants acustom testprogramHong sendsan e-mailending with"Pleaseadvise."Rahuldoesn'tbelieve it's acomponentissueOutlookgoesdownA newoperatorneeds to beadded to thedatabaseChris asks,"Did you puta scope onit?"Heatherexpeditesan ECOEduardawalks intoour area andsays, "Knockknock"Paulwants tocleansomethingQ&Rneeds toclear aflagProductEngineeropens acontainmentfor limitsIt took morethan 6 e-mailsto resolve asimpleproblemThe unitspass onretestPaulcomplainsaboutsomethingLisa needsall units fora "verylate" orderOperatorused thewrongfixtureTom asksaboutupgradingTestStandUnitshave tobe testedupstairsNPI needshelp withinductance

Test Engineering 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. PE wants ATE to characterize the units
  2. Sarah finds a test issue but it's actually a datasheet issue
  3. It's a timing issue
  4. The units are manually approved
  5. PE gives you a unit that doesn't work
  6. Component Engineering wants a custom test program
  7. Hong sends an e-mail ending with "Please advise."
  8. Rahul doesn't believe it's a component issue
  9. Outlook goes down
  10. A new operator needs to be added to the database
  11. Chris asks, "Did you put a scope on it?"
  12. Heather expedites an ECO
  13. Eduarda walks into our area and says, "Knock knock"
  14. Paul wants to clean something
  15. Q&R needs to clear a flag
  16. Product Engineer opens a containment for limits
  17. It took more than 6 e-mails to resolve a simple problem
  18. The units pass on retest
  19. Paul complains about something
  20. Lisa needs all units for a "very late" order
  21. Operator used the wrong fixture
  22. Tom asks about upgrading TestStand
  23. Units have to be tested upstairs
  24. NPI needs help with inductance