Agile2013

RT @aclairefication: Code stewards for architecturally critical areas. (When a team is not all equal in skills.) #Agile2013

— Simon Brown (@simonbrown)2013-08-05 15:26:36

"Code stewards for architecturally critical areas" ~agreed, but was introduced by @rebeccawb with a sarcastic tone of mistrust... #Agile2013

— Gary Pedretti (@GaryPedretti)2013-08-05 15:26:21

RT @jasonlittle: "Prediction is not possible when it comes to dynamic and complex change" #agile2013

— Carl Schrammel (@carlschrammel)2013-08-05 15:26:19

RT @RPR_Elon: Based on my outsider interpretation of tweet stream, waiting for Agile and Kanban gangs to throw down #Agile2013

— Sharon Robson (@SMRobson)2013-08-05 15:26:17

Talk by @garethbowles at #agile2013 tools team works with700 engineers in Dev, test, ops

— Vinayak Joglekar (@vinayakj)2013-08-05 15:26:01

RT @cyetain: Failure provides information -@RisingLinda #agile2013 http://t.co/qrQRLsqhMi

— Katie Walley-Wiegert (@o0KitKat0o)2013-08-05 15:26:00

RT @DocOnDev: "Multi-tasking is linked to madness." - @agilescout #Agile2013

— Tim Ottinger (@tottinge)2013-08-05 15:25:54

So true for #highered learning objectives too MT @JennBertram: Writing reqs in 1st not 3rd person is powerful shift in viewpoint. #Agile2013

— Rebecca Pope-Ruark (@RPR_Elon)2013-08-05 15:25:48

Coordinating work? Team size, location matters. Deliberately split but know the system as a whole. #Agile2013

— Claire Moss (@aclairefication)2013-08-05 15:25:47

Telling stories to extract archetypes of the agile community w @PapaChrisMatts and @lunivore - very cool... #agile2013 w @lesliejdotnet

— Jake Calabrese (@jcalabrese)2013-08-05 15:25:45