Agile2013

RT @rebeccawb: 2 of my IEEE SW Design Columns that seem relevant post #Agile2013: http://t.co/7wjH3wYN2c & http://t.co/vTCwvBBQwU strategy …

— ComputerSociety (@ComputerSociety)2013-08-13 15:40:24

@AgileSteveSmith @joshuajames we had a tough slot coinciding with @cyetain @jeffpatton so not many people but very good feedback #Agile2013

— Özlem (@OzzieYuce)2013-08-13 15:36:12

RT @ProjectsAtWork: Our #Agile2013 chat w/@donaldegray on #Leadership within Self-Organizing Teams: http://t.co/SnPtn1OBxq

— estherderby (@estherderby)2013-08-13 15:24:42

@OzzieYuce @joshuajames How did the #agile2013 presentation go, guys?

— Steve Smith (@AgileSteveSmith)2013-08-13 15:14:25

Take away #3 #Agile2013 - Devs - Join in on the ideation and design process. But leave the developer hat at the door. @Billois

— Tracey Axelrod (@tjaxe)2013-08-13 15:04:27

RT @jboogie: Good stuff: Experimenting in the Enterprise Agile 2013 Conference by @davidjbland on @slideshare #agile #agile2013 http://t.co…

— Ash Maurya (@ashmaurya)2013-08-13 14:53:39

Take away #2 #Agile2013 - Technical (non-product owner value) stories do NOT have to follow the User Story "As A..." format. @Billois

— Tracey Axelrod (@tjaxe)2013-08-13 14:52:52

Good stuff: Experimenting in the Enterprise Agile 2013 Conference by @davidjbland on @slideshare #agile #agile2013 http://t.co/rA6rj8WZXy

— Jeff Gothelf (@jboogie)2013-08-13 14:51:58

Take away #1 #Agile2013 - It's ok to pull from multiple backlogs but need to look at ONE person for decisions @Billois

— Tracey Axelrod (@tjaxe)2013-08-13 14:50:50

.@Billois My top 3 take aways from #Agile2013 follow

— Tracey Axelrod (@tjaxe)2013-08-13 14:50:01