Agile2013

I made @bcarlso a shirt and he’s owning it! #Agile2013 http://t.co/UK1uEPkWTd

— Tim Gifford (@timgifford)2013-08-05 15:37:08

Great question "are you unwilling to be influenced because you feel you are not being heard" @mspayd @lyssaadkins #agile2013

— Boost New Media (@boostnewmedia)2013-08-05 15:37:04

Surely by definition if you can accurately predict what is going to happen next you are not dealing with a complex problem. #agile2013

— cgosimon (@cgosimon)2013-08-05 15:36:53

RT @SMRobson: The ability to state a prediction is quite separate from the ability to actually predict #agile2013

— Johanna Rothman (@johannarothman)2013-08-05 15:36:47

Talk by @garethbowles at #agile2013 Jenkins build jobs using groovy based DSL , loop to build different branches, code is configuration

— Vinayak Joglekar (@vinayakj)2013-08-05 15:36:42

+1 brilliant @cgosimon The ability to state a prediction is quite separate from the ability to actually predict #agile2013

— Erik Weber (@Erikjweber)2013-08-05 15:36:29

What's larger, EPIC or THEME? @mikewcohn doesn't know ;) #agile2013

— ScientiaTech (@ScientiaTechLA)2013-08-05 15:36:17

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

— pedrowaty (@pedrowaty)2013-08-05 15:36:17

Hmmm... RT @tjaxe: You'd have to be at the @mikewcohn session to know how an Epic is like a chick flick. #Agile2013 great stuff!

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

Deposits into "positivity": Appreciations, Acknowledgments, More Inquiry & Less Advocacy. - @lyssaadkins #agile2013

— Nayan Hajratwala (@nhajratw)2013-08-05 15:36:12