PNSQC

Asking questions /can/ help everyone understand, but the questions need to be properly contextualized and relevant #pnsqc @petewalen

— umckinney (@umckinney)2012-10-09 20:16:17

Done with my #PNSQC talk "Are We Failing at UI Automation?" Thanks to all who attended. I'll have slides posted soon!

— Jim Holmes (@aJimHolmes)2012-10-09 20:10:43

I like the terms used in this presentation: Product Owner = Customer Whisperer, Developer = Code Artist, Manager = Servant Leader. #pnsqc

— Michael (Doc) Norton (@DocOnDev)2012-10-09 20:07:27

A report that doesn't get read is not a report. It is a #wasteoftime #pnsqc

— umckinney (@umckinney)2012-10-09 20:04:14

RT @EdBrothers: How to kill success: Ignore a failed user experience because it meets tech design. #pnsqc /cc @petewalen

— Ian E. Savage (@iesavage)2012-10-09 19:59:50

/amazing/ site visit at geoloqi in Portland during #pnsqc Next: Turorial day, then: Royal Caribbean, then: #STPCON

— mheusser (@mheusser)2012-10-09 19:54:35

The agreement of alignment between the system and the system users defines if the system "works" #pnsqc /cc @petewalen

— Ed Brothers (@EdBrothers)2012-10-09 19:50:54

@DocOnDev interesting. Wish I was there, but glad I'm in @petewalen session. #pnsqc

— umckinney (@umckinney)2012-10-09 19:47:41

The restaurant in @hotel50 in Portland is outstanding. #pnsqc

— Dale Emery (@dhemery)2012-10-09 19:39:58

How to kill success: Ignore a failed user experience because it meets tech design. #pnsqc /cc @petewalen

— Ed Brothers (@EdBrothers)2012-10-09 19:26:43