PNSQC

Keep the sizes relevant (aka t-shirt sizes). Simpler because it needs less information. #pnsqc

— Josh Meier (@moshjeier)2013-10-15 14:26:11

story starts middle, moves to the lft for higher priority, to the rt for lower priority. all stake, PO final call, open negotiations #pnsqc

— Josh Meier (@moshjeier)2013-10-15 14:25:11

RT @DianaOfPortland: "When I focus on quality, I gain speed." - Michael Mah #pnsqc #agile

— Manuel Paccagnella (@map_it)2013-10-15 14:24:41

RT @DianaOfPortland: That awkward time when everything is ready for the speaker to begin, but the schedule says a few more minutes. #pnsqc …

— Chris Lucian (@DeadlyApps)2013-10-15 14:23:44

Use an insertion sort to prioritize, other methods have issues, one person in charge, inefficient, all high priority, etc #pnsqc

— Josh Meier (@moshjeier)2013-10-15 14:23:33

Use position to add meaning, temp remove card to rmv from discussion, turn it upside down to indicate distress, use as talking stick #pnsqc

— Josh Meier (@moshjeier)2013-10-15 14:21:40

Low Tech PM Tip: Make story cards work overtime. Tracking ID, story size, initial priority, champion, special conditions. #pnsqc

— Josh Meier (@moshjeier)2013-10-15 14:20:48

RT @moshjeier: Low Tech PM Tip: Get out of the building (or box) and see how your software will be used in real world scenarios. #pnsqc

— Amith Pulla (@pamith)2013-10-15 14:19:28

RT @DianaOfPortland: "When I focus on quality, I gain speed." - Michael Mah #pnsqc #agile

— Joshua Kerievsky (@JoshuaKerievsky)2013-10-15 14:18:03

Low Tech PM Tip: Get out of the building (or box) and see how your software will be used in real world scenarios. #pnsqc

— Josh Meier (@moshjeier)2013-10-15 14:17:45