Operatorused thewrongfixturePE gives youa unit thatdoesn't workIt's atimingissueRahuldoesn'tbelieve it's acomponentissueChris asks,"Did you puta scope onit?"Lisa needsall units fora "verylate" orderPaulcomplainsaboutsomethingProductEngineeropens acontainmentfor limitsQ&Rneeds toclear aflagHeatherexpeditesan ECOTom asksaboutupgradingTestStandPE wantsATE tocharacterizethe unitsHong sendsan e-mailending with"Pleaseadvise."The unitspass onretestPaulwants tocleansomethingA newoperatorneeds to beadded to thedatabaseOutlookgoesdownThe unitsaremanuallyapprovedComponentEngineeringwants acustom testprogramIt took morethan 6 e-mailsto resolve asimpleproblemSarah finds atest issue butit's actually adatasheetissueUnitshave tobe testedupstairsNPI needshelp withinductanceEduardawalks intoour area andsays, "Knockknock"Operatorused thewrongfixturePE gives youa unit thatdoesn't workIt's atimingissueRahuldoesn'tbelieve it's acomponentissueChris asks,"Did you puta scope onit?"Lisa needsall units fora "verylate" orderPaulcomplainsaboutsomethingProductEngineeropens acontainmentfor limitsQ&Rneeds toclear aflagHeatherexpeditesan ECOTom asksaboutupgradingTestStandPE wantsATE tocharacterizethe unitsHong sendsan e-mailending with"Pleaseadvise."The unitspass onretestPaulwants tocleansomethingA newoperatorneeds to beadded to thedatabaseOutlookgoesdownThe unitsaremanuallyapprovedComponentEngineeringwants acustom testprogramIt took morethan 6 e-mailsto resolve asimpleproblemSarah finds atest issue butit's actually adatasheetissueUnitshave tobe testedupstairsNPI needshelp withinductanceEduardawalks intoour area andsays, "Knockknock"

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