Operatorused thewrongfixturePaulcomplainsaboutsomethingPE gives youa unit thatdoesn't workProductEngineeropens acontainmentfor limitsPaulwants tocleansomethingSarah finds atest issue butit's actually adatasheetissuePE wantsATE tocharacterizethe unitsRahuldoesn'tbelieve it's acomponentissueComponentEngineeringwants acustom testprogramLisa needsall units fora "verylate" orderIt took morethan 6 e-mailsto resolve asimpleproblemIt's atimingissueEduardawalks intoour area andsays, "Knockknock"Heatherexpeditesan ECOThe unitsaremanuallyapprovedUnitshave tobe testedupstairsOutlookgoesdownQ&Rneeds toclear aflagTom asksaboutupgradingTestStandNPI needshelp withinductanceChris asks,"Did you puta scope onit?"A newoperatorneeds to beadded to thedatabaseThe unitspass onretestHong sendsan e-mailending with"Pleaseadvise."Operatorused thewrongfixturePaulcomplainsaboutsomethingPE gives youa unit thatdoesn't workProductEngineeropens acontainmentfor limitsPaulwants tocleansomethingSarah finds atest issue butit's actually adatasheetissuePE wantsATE tocharacterizethe unitsRahuldoesn'tbelieve it's acomponentissueComponentEngineeringwants acustom testprogramLisa needsall units fora "verylate" orderIt took morethan 6 e-mailsto resolve asimpleproblemIt's atimingissueEduardawalks intoour area andsays, "Knockknock"Heatherexpeditesan ECOThe unitsaremanuallyapprovedUnitshave tobe testedupstairsOutlookgoesdownQ&Rneeds toclear aflagTom asksaboutupgradingTestStandNPI needshelp withinductanceChris asks,"Did you puta scope onit?"A newoperatorneeds to beadded to thedatabaseThe unitspass onretestHong sendsan e-mailending with"Pleaseadvise."

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