2013/08/07: Agile 2013 Day 3

by Gene Kim on

#agile2013

Up: "Learning To See," Rob Benefield, CTO, Evolve Beyond

http://leandevops.com

  • Benefield: "Large batch sizes kill; how do we prevent fires and reduce flammable fuel; how do we reduce expedites?"
  • Benefield: "Created role of queue master, prioritizing flows/work from many Dev teams" (so often Ops can be bottlenecks)
  • Benefield: "Queue master: examines incoming wk, ensures things look right: also has unscheduled queue, clarification q"
  • Benefield: "Queue master: looks for bottlenecks, clarifies, also takes on work sometimes"
  • Benefield: "Queue master: ensures all work is in the flow & is visible; ensures correct prioritization
  • Benefield: "1 week long iterations (at most); Queue Master role should rotate at regular intervals (great idea!)"
  • Benefield: "Retrospectives: review queues, go through blocked tasks, review flow problems, archive/done
  • Benefield: "Planning: Handover the Queue Master hat; choose which Improvement Items to action; review key upcoming activities
  • Benefield: "In Ops: there's Info Sherpas & Fire Wardens; John Boyd notion of Intuitiveness to create 'org twitch' like fighter pilots
  • Benefield: "Fire Wardens: spot arsonists (haha!) & fire hazards; Info Sherpas: ensures info flows, go to Dev standups, etc"
  • Benefield: "DevOps & Service Engineering: spans Continuous Delivery, Workflow & Svc Transparency, Elastic Svc Arch"
  • Benefield: "Metrics that matter: total cost of ownership, people intensity, risk"
  • Benefield: "Information radiators: production metrics, repos (who's checking in, are they happening on time, only one person?)
  • Benefield: "Proactively find single person risk,
  • Benefield: "Look at build trends, test trends: 'Uh, why are all the builds failing 2 days before we ship?"
  • Benefield: "We found that when we put production metrics and incident data in public places, people really cared"
  • Benefield: "Automation (or autonomation): improve flow & transparency: reduce people intensity, instrument and find defects early"
  • Benefield: "Tale: billing service: nightly batch job; had failing jobs; 4-6 months later, irate customers called; lots of stuff that they didn't buy
  • Benefield: "CRM team had created a change, and didn't validate for special characters; threw exception; fixes left db in corrupt records;
  • Benefield: "Gemba: learning to see: walk the Gemba: visualize the flow; instrument and let info go free; get intuitive; continually improve
  • Benefield: "In Ops, it's more difficult to plan like Dev can; so you can't load the teams up; instead prioritize work

Steve Bell:

  • Jeff Sutherland/Steve Bell: "Scrum <> Toyota Production System cell"
  • @HalaSaleh1: RT @utahkay: Read "The Machine that Changed the World" to understand #Scrum @jeffsutherland with @LeanITCoach #Agile2013 http://t.co/T1m7aB
  • @HalaSaleh1: RT @utahkay: Read "The Machine that Changed the World" to understand #Scrum @jeffsutherland with @LeanITCoach #Agile2013 http://t.co/T1m7aB
  • RT ??: claim by @jeffsutherland that creation of x-functional team on a toyota assembly line was first implementation of scrum #stretch #agile2013
  • RT ??: Toyota thought leaders never use the word "Lean." @jeffsutherland with @LeanITCoach at #Agile2013

Up: "Agile Quality Assurance: A Long Painful Tale Of How We Get Better", Tommy Norman, Fahed Sider

  • "7:1 Dev/QA ratio; we were always at least one sprint behind" (crowd moans in pain)
  • Norman: "We hired another QA. Yay. Then we hired 3 more Devs. Boo." (haha)
  • Norman: "Poor QA person trying to get arms around code; Devs generating more bugs, writing code on double secret probation"
  • Norman: "Communication anti-pattern: Dev creating quickly new features ("let's make it two screens!"); QA 2 @GaryPedretti: RT @quicola: Something we don't have a problem scaling is misunderstanding #Agile2013 #communicationkatas
  • wks later: "WTF?"
  • Norman: "HW lab anti-pattern: Dev had better machines, never in sync w/each other; data and environments never made it to
  • Norman: "Problem: prod owner nvr around, refused to learn TFS; feature spec like buying present for wife ('not what I wanted')
  • Norman: "Business said 'we want MVP', didn't invite QA
  • Norman: "Started putting defects into backlog, treating it like all other work; if your bug amount is larger than product amount, it's difficult"
  • Norman: "We moved from platforms to value streams; if no FoxPro work that week, then instead of moving that person, trained him from other platforms"
  • Norman: "Fought utilization issues: put all platform expertise on value stream; If no FoxPro work this week, they learned C#"
  • Norman: "Harder argument: teaching C# programmers FoxPro: teaching dead language, ummarketable skill tough sell" Hahaha
  • Norman: "Everyone started sitting together; QA and Dev started collaboating, QA as 1st class citizen"
  • Norman: "Asked to be interim QA manager for a couple of months; had to say yes; I'm not a QA guy, so all I could do was do retrospective and ask 'what do you need'"
  • Norman: "Served as interim QA mgr; knew nothing about QA, so all I could do was retrospectives & ask 'whaddya need?'
  • Norman: "QA kept asking for automation. Kept saying, 'no, all we have is crap tests. Can't automate crap tests"
  • Norman: "Prob: bad test cases; Soln: create w/Dev/QA happy path, alternataive path, negative, technical path; long process"
  • Norman: "Made everyone responsible for tests; refactored old tests; slowed down; boss kept asking "have we automated yet?" "no"
  • Norman: "Put all tests into Excel, & confirm whether we could we actually import somewhere else eventually " (love it)
  • Norman: "Boss kept asking 'have we automated yet?'; kept having to say, 'no.'
  • Norman: "Dev: 'I want to make this into 2 screens'; Me: "whoa there, cowboy. let's write the tests together"
  • Norman: "Test lab: we got field people to train us to build cabinet doors, wiring runs, build labs; send me all your broken stuff, and now every team to build test lab; made it so much easier to deploy to in 1 hour, so we could test during the sprint"
  • Norman: "Dev: 'bang bang bang on Feature A'; What is QA doing? 'work from previous sprint!'; constant task switching for Dev"; 'Uh oh. Then code freeze"
  • Norman: "Man, those tricky Devs! They're still writing code during our code freeze! Who's doing regression testing" (hahah)
  • Norman: "New cadence: jointly write test plan for Feature A, write feature, then Dev finish writing tests! Only then do Feature B; never did full regression; no way we could do all the manual testing; we did targeted regression and exploratory testing
  • Norman: "Boss: what! you're going slower!
  • Norman: "QA led, crafted the test case; mentoring Dev on how to write tests
  • Norman: "In old days, Dev did demos, jury rigging crap to make it look good; Now QA does our demos, then Prod Owner" (nice!)
  • Norman: "We're still not good enuf to not do Hardening sprint; Dev mgr would call ppl, 'I saw you checkin new code; bad Dev" :)
  • Norman: "We worked on creating realistic data, so we could actually see whether we weren't killing people" (haha. pharma data)
  • Norman: "Best full regression; we scrubbed production data; and we had to test scenarios"
  • Norman: "It took 1 guy a week to create our test data; immediately flagged the need to automate this"
  • @SMRobson: #agile2013 @tommynorman Other people doing QA estimates > Meaningless metrics (story points) = meaningless reporting
  • A totally marvelous story of "QA transformation" by @tommynorman; Although, I think it's really a story of biz transformation
  • Can someone repeat the @tommynorman story? Why did he punch the cube wall in anger?
  • .@tommynorman: "Eventually, last 5 sprints released to beta; reduced need of Hardening Sprint; Better distrib domain knowledge
  • .@tommynorman: "Fast deploys allowed better ability to react to change; enabled fast feedback loops w/customers
  • .@tommynorman: "we had to seriously review our requirement for 10 y of backwards compatibility, which was ki@jcreamer898: RT @reverentgeek: Thanks @tommynorman for my Comfortably Scrum shirt! #agile2013 http://t.co/CIJO6IUyWP
  • lling us w/tests
  • .@tommynorman: "We shipped 1.0! Yay! Then waterfall came back in 1.1. Prod owners got on planes again. @SMRobson: #agile2013 @tommynorman results of hardening sprint=regression coverage, better domain knowledge (whole team), better change ability,
  • Boo."
  • @SMRobson: #agile2013 @tommynorman results of hardening sprint=regression coverage, better domain knowledge (whole team), better change ability,
  • .@tommynorman: "Oh, this is heartbreaking. Teams were dissolved/ moved; POs went back on planes; backlog got screwed up"
  • .@tommynorman: "Dev started architecting, blocking out QA; QA siloed themselves; Defn of 'Done' grew to 11 criteria" (argh)
  • OMG. @tommynorman is cracking us up, taking us on rollercoaster Hero's Journey of QA. Hilarious talk..
  • .@tommynorman: "Shrunk # of platforms, forced people assignments; restructured entire company to scrum; core team leads hv managers; scrum team
  • .@tommynorman: "Where do you find good Product Owners? PMs? BAs? Easy. Productville. Find good POs"
  • .@tommynorman: "New org: Team leads' job is to make people the best Dev/QA person I can be. We started looking like Spotify!
  • .@tommynorman: "We got 2 full time coaches; we trained everybody, got better tools, better metrics, hired more QA, converting Dev to QA, everything has to release ready at end of sprint, and cannot ship untested code
  • .@tommynorman: "Mtg: our values say, 'we only ship things we've tested & feel good abt.' 'we can't!' 'then do less." (yes!)
  • .@tommynorman: "We trained everyone on MS Test Manager, & gave qtrly bonuses to Devs who wrote Happy Path tests"
  • .@tommynorman: "In the end, Mgmt, POs, Dev and QA so much better off; we knew the product better, fewer bugs, so much better than we were; code more solid than ever, increments faster, beta program expanded, short feedback loops
  • .@tommynorman: "Boss said, 'you made biggest contribution to transformation of this company
  • .@tommynorman: "Lessons: Have courage to say 'no' & 'Don't accept 'no' from anyone'; Contradiction? No. Value vs. mechanism

Up: "How DevOps Changed Everything", Karthik Gaekwad, @iteration1

  • .@iteration1: "In the beginning at NI, we were waterfalls; issues: communication ("I told you this already, you're wasting 2-3 months of my time")
  • .@iteration1: "Problem: 'That's not my job, especially testing'; Time to deliver: 'we built it 6 months ago, but now customers aren't asking for it' or 'I can't do that right now'
  • .@iteration1: "New product: Partslist: you can collaborate, tag, hardware and software parts for their systems; Product Team instead of the Traditional Org
  • .@iteration1: "Immediate benefits: Feedback loops tighter, built things that customers wanted; trust between business and IT; better products being delivered at a faster pace, and then spread to all the other teams"
  • .@iteration1: "Results: people actually loved their job! But it's difficult for Ops, b/c it takes months to provision servers
  • .@iteration1: "Deployment dude: "Moar deploys? Argh! I just got done with last set that sucked."
  • .@iteration1: "Our team saw the seminal Allspaw/Hammond presentation, and said, 'we've gotta do that'
  • .@iteration1: "Management memo, 'Go build me some cloud stuff' -- instead of 6 weeks server provision process would take minutes
  • .@iteration1: "My fave devops defn: 'get rid of the devs, get rid of the ops; just find me ppl who solve probs. Alison Chekin"
  • .@iteration1: "Haha. We called our team 'Agile DevOps Cloud Team' -- very buzzword friendly!"
  • .@iteration1: "Goal: build cloud authentication prototype; our 1st sprint sucked; didn't hit sprint goal: wall of confusion
  • wall of confusion: REST svc vs stability
  • .@iteration1: "Result of 1st failed sprint: we built platform architecture first, application later; framed system goals
  • .@iteration1: "We agreed that db lived here, front end lived here, jar files, etc. we called this the System Model
  • .@iteration1: "Model driven automation: championed by ops: define how we deploy it;
  • .@iteration1: "Programmable Infrastructure Environment: version controlled infrastructure: from Perforce to deploy"
  • .@iteration1: "Outcomes: Ops learned java, version control; Dev learned w/production environments"
  • .@iteration1: "Devs used Windows, oft scared of Linux; would often check into verrsion control, and let someone else do the Linux fixes
  • .@iteration1: "For you Ops in #DevOps, you need to learn to code. #notscary #justaskadev" (Lovely, bro.)
  • .@iteration1: "Let your deployment automation (puppet/chef/etc) make your chg mgmt easy"
  • .@iteration1: "Tools philosophy: needed to work in cloud; facilitate collab; charts & graphs; everyone wants to use
  • .@iteration1: "Monitoring=cloudkick; I always thot monitoring was Ops thing (cpu); started adding code telemetry; now #datadog
  • .@iteration1: "We need to teach Dev how to monitor their code & they will love the [monitoring] tools; Ex: #newrelic" (yes!)
  • .@iteration1: "Biggest fan of monitoring? Mgmt! Answered q's like "how many users signed up?"; went from emails to real time
  • .@iteration1: "Hint: Since management pays us, I think it helps to keep them happy." (Haha. Karthik is hilarious)
  • .@iteration1: "CloudAustin July did monitoring meeetup: look for the video"
  • .@iteration1: "Releasing something 4 chgs is much less risky than one with 40K changes"
  • .@iteration1: "Do you have free time? Write more tests!"
  • @testobsessed: "Stuff breaks all the time. It's OK. Be cool. Just fix the problem at hand." -- @iteration1
  • .@iteration1: "One cannot deploy continuously without continuous testing"
  • .@iteration1: "Don't do this: 1. make manual chgs in Dev; 2. add puppet/chef script; 3. Deploy"
  • .@iteration1: "DevOps 301: we added security into #devops; added security audits as part of our sprints"
  • .@iteration1: "At Mentor Graphics, now we do @gauntlt security tests as part of every checkin; added infosec to DevOps team
  • .@iteration1: "we didn't have budget for infosec person, so we created a cross-functional team; reviewed architecture
  • .@iteration1: "Team expanded: added Malaysian team resp for day/day ops; rotated austin/malaysian times; record scrum standups and put into dropbox; 'ok to call' philosophy (Malaysians didn't know was it ok to call before 8am or after 5pm? 'it's okay to call anytime, and we'll call you later
  • .@iteration1: "Campfire chat (history is so useful); Ownership of new feature (like adding splunk to Windows)
  • .@iteration1: "The embedded DevOps model works (ie, devops team, where ppl are loaned out; I was loaned out to help new mobile team)
  • .@iteration1: "Retrospective: we built stable products on time that customers wanted; superior collaboration

Up: "Enterprise Agility: Practical Demystification", Jean Tabaka, Hendrik Esser (@jeantabaka)

  • @AdamYuret: @Jeantabaka plugging lots of great flow thinking with @estherderby here in Delta D at #agile2013. I am so glad to see @DReinertsen's work.
  • @JennBertram: Help teams make better decisions by increasing overlap of contextual knowledge & daily task knowledge. #agile2013 http://t.co/HqkS65d8jQ
  • @ojuncu: 1st, they get in the way of valuable conversation “@dkgunther: "Job descriptions get in the way of collaboration" -Esther Derby #agile2013
  • I always love hearing @jeantabaka talk about trust
  • @ReleaseTEAMInc: RT @RallySoftware: "We measure our performance, not our people." @HendrikEsser #Agile2013
  • Interesting: "On trust: there's a difference between transparency and intimacy" (1st is 'my mother used to slap me')"
  • Diagram from @estherderby on trust & system patterns: "makes 'blame' and 'deserve' go away"
    https://pbs.twimg.com/media/BRF0RVBCYAAjcU4.jpg
  • @andrewmfuqua: "Everything with me is a competition!" ~@jeantabaka
  • @andrewmfuqua: "Everything with me is a competition!" ~@jeantabaka
  • @agiledawg: @estherderby "Hierarchy tends to imply that there is a difference in power and privilege" #agile2013 #enterpriseagility
  • .@estherderby: "One company decided against ESOP stock options; instead chose to give out stock and annual profit sharing
  • @hhiroshi: Wise words from @estherderby about transition "Start from where you are"

I'll add "& discover your pains and do your first step"

Up: Forty Years Of Trying To Play Well With Others", Tom Lister

  • Interesting! True! Kent McDonald: "I've noticed more people wearing eyeglasses as the week progresses..."
  • Hypothesis: sustained #agile exposure causes myopia. Haha. :)
  • @UXAlison: RT @msilpala: It’s nice to see that #agile2013 has a higher percentage of women than the IT industry as a whole. Now let’s fix up that indu…
  • @andrewmfuqua: old-school structures crush collaboration, drive dysfunctionality. Apparent when assessed thru agile lens. 1/2
  • @andrewmfuqua: 2/2 That's why we go after structure 1st, to make collaboration and stuff possible.#agile2013
  • @astridclaessen: My top 3 topics choice for #agile2014 done here at #agile2013 http://t.co/okS9nK8Egp
  • @agilescout: @flowchainsensei I like it. You're exactly right.... which is why "culture" is such a complex system to understand and ascertain!

  • Lister: "As last talk, I already smell fried brains. So I'm just going to tell you some stories

  • Lister: "Showing video from Tom DeMarco, co-author of Peopleware"

  • Lister: "DeMarco: 'The problem of overbearing Process is now less of a problem than when we originally wrote the book. Congrats to all of you'"

  • Lister: "DeMarco: It feels better to build something great as part of a team vs. doing it yourself."

  • @aclairefication: Agile movement took aim at virulent and ruinous prescriptiveness. - virtual Tom DeMarco #Agile2013

  • @aclairefication: Partnership paradox: feels better to make things together than to have done it all yourself. - virtual Tom DeMarco #Agile2013

  • AGH! A GIANT LOBSTER!!!! RUN!!!!

  • Lister: "I'm 63 years old, been in this business for 25 years"

  • @vinayakj: Keynote by @timlister at #agile2013 if you don't get innate pleasure from writing code - it's time to move on

  • @scottwambler: If it isn't fun anymore it's time to move on otherwise you'll be one unhappy person. @TimLister101 at #Agile2013

  • @SMRobson: #agile2013 Tim Lister try to remember when you loved your job and did it for fun...what a great way to think!

  • @RealGeneKim: 1968: Lister: the CPU is the big suitcase. Wow. #agile2013 http://t.co/TA5FFgqrJd

  • @agiledawg: Tim Lister: "If you don't get innate pleasure from writing code, it's time to move on"

  • @ReleaseTEAMInc: RT @jcalabrese: OH "you killed that man with a kanban trident" #agile2013 #anchorman

  • @aclairefication: My first genius mentor - Tim Lister (first? Alrighty then) #Agile2013 http://t.co/JAtRp6XTza

  • @TheCharlesCain: RT @gerrykirk: Endorsed by agilists @mkilby @Bendre @toddcharron: Stop Doing Busywork, Start Doing Best Work. 90% off 4 #agile2013 http://t

  • @jeantabaka: RT @PrettyAgile: .@jeantabaka's reading list for Enterprise Agility and flow of value #agile2013 http://t.co/O3o1Xzkb06

  • Lister: "For forty years, software making has been in a state of continual renessaince"

  • @SMRobson: #agile2013 Tim Lister "it is very rewarding to be around people who are way ahead of you" and I can ask all the dumb questions :) love it!

  • Lister: "When my 29 yo boss' boss' boss left, it changed my life; I learned what it felt like when ur manager doesnt trust you

  • Lister: "Working for a bad manager who micromanaged started my workin project management & dynamics

  • @aremsan: When a good person is around they are nearly invisible. But when they leave- boy, is it visible!

  • @ojuncu: RT @JeffreyGoodReq: Tim Lister "It's good to spend time thinking about what you do, not just doing" #Agile2013

  • Lister: "No one lets me forget that one of my new employees quit after 3 hours" (haha)

  • Lister: "Quoting someone: 'I just know I'm a better manager when Joe DiMaggio is in center field"

  • Lister is proving that you're only as smart as the top 5 people you hang out with. An important lesson.

    https://pbs.twimg.com/media/BRGJDK9CEAAHRBL.jpg

  • @theagilist: Casey Stengel, "I just know I'm a better mgr w Joe Dimaggio in center field." @TimLister101 on the importance of teams. #Agile2013

  • @HalaSaleh1: For real, you guys are amazing. Even though I left #Agile2013 this afternoon, I feel like I'm right there just reading your tweets!

  • @aclairefication: I'm just a pain in the ass in the back of [Ed Yiurdon's] class - Tim Lister #Agile2013 (totally reminds me of my favorite DMath gal) <3

  • @magia3e: RT @PrettyAgile: In value stream flow we watch: customer, cadence, capacity, clogs, cost, collaboration @jeantabaka

  • Interestingly, here's @adrianco's proof point: him + other 50 Sun Distinguished Engrs from 2000. #devops

    https://pbs.twimg.com/media/BRGJ-HFCAAAamFJ.jpg

  • @aclairefication: You ever seen someone's code where it's the midday beautiful thing you've ever seen? - Tim Lister on paired programming early 70s #Agile2013

  • @PrettyAgile: Tim Lister credits @JerryWeinberg with being the first person to realise programmers were human!

  • Lister: "Henry Mills did work that NASA estimated at 30 man-years in merely 10 months; how? didn't make mistakes"

  • (@adrianco on "how do u become a Sun DE?" Ask 'how many DEs do u know? how many know u? how many ask u for help?" #devops

  • @drm3107: RT @scottwambler: Putting together a team may be the most important work for many projects. Tim Lister at #Agile2013

  • @aclairefication: RT @SMRobson: #agile2013 Tim Lister "my LinkedIn title is "stable boy" because I shovel the s%#^ for my team" loving the frankness and lear…

  • @scottwambler: How much better would the IT industry be if we were all familiar with the people Tim Lister talks about? #Agile2013

  • Lister: "When I learned phase gates was a lie; proof was 'testing' gate, whose only role is to send you back to prev phases

  • @aclairefication: I'll come back in 40 hours and you give me what you got. Why don't we always run our projects like this? - Tim Lister

  • @SMRobson: RT @aclairefication: Tim Lister recounts a story of intellectual conversations going until 2 am #Agile2013 (i know trading off sleep for id…

  • @ReleaseTEAMInc: RT @aclairefication: He had no filter between idea and mouth. - Tim Lister

  • @SMRobson: #agile2013 Tim Lister "life is not always in chronological order" +++ could not agree more!

  • Lister: "Lessons from doing arbitration work: projects never fail at the last minute; it festered fro the beginning"

  • @PrettyAgile: Tim Lister - phases never made much sense to me, the testing phase just seems to be there to throw you back into previous phases

  • @astridclaessen: "You must choose one or the other, you can't cut the baby in half" - Tim Lister on Arbitration

  • @SMRobson: #agile2013 Tim Lister "things go south soon on projects, not at the end. It's usually festering from the beginning" soooo true!

  • @edwindando: Great so see Boehm's spiral model at #agile2013. It was this model that planted seeds of agile in my mind in '97!!

  • @aclairefication: Legal cases are a pox in both their houses. Goes downhill fast. Takes 2, always emotional, magic finger. - Tim Lister arbitrator #Agile2013

  • @absoludicrous: At Keynote Tim lister shows boehm's spiral dev model. I remember when @xsgreene drew that for my benefit around a decade ago. #Agile2013

  • @jeffpatton: Testing is there to send you back into previous phases that you thought we're closed. via Tim Lister

  • @aremsan: I am totally going to use the magic finger.

  • @SMRobson: #agile2013 Tim Lister shares the power of the magic finger. It means "I know, I've noticed and I will remember". Takes the pressure off

  • Lister: "Telling story of death march project gallows humor. 'they want us to be done in December. which December?" (haha)@galbraithsimon: The power of the Magic Finger! Tim Lister's insight on preventing interruption at #Agile2013.

Misc

  • @nohz: "If your really good at this stuff, you will only be right 1/2 of the time." Marty Cagen @jeffpatton
  • Marty Kagan, right? RT @nohz: "If u'r really good at this stuff, you will only be right 1/2 of the time." Marty Cagen @jeffpatton
  • @lesliejdotnet: Empty retrospectives that send problems thru the "control cycle" = problem isn't really solved, it's just relieving anxiety. #Agile2013
  • @PrettyAgile: When you take choice away from your teams they don't feel responsibility #agile2013 #leadershipgift
  • @Erikjweber: @bcarlso "enterprise anthropology" idea is "factabulous"
  • Hahaha. RT @Erikjweber: @bcarlso "enterprise anthropology" idea is "factabulous"
  • @markwshead: "The success rate of waterfall is 14%. The success rate of agile is 42%" - Jeff Sutherland
  • "Still lots of bad Agile out there" RT @markwshead: "The success rate of waterfall is 14%. Agile is 42%" - Jeff Sutherland
  • Wonderful book! RT @utahkay: Read "The Machine that Changed the World" to understand #Scrum @jeffsutherland @LeanITCoach
  • RT @GaryPedretti: RT @quicola: Something we don't have a problem scaling is misunderstanding #Agile2013 #communicationkatas
  • @athought: "Holy crap! She really cares about her people!" Servant leadership and more vulnerability from @t_broderick #Agile2013
  • @utahkay: Don't try to educate clients about stuff they don't care about @cgosimon #Agile2013
  • @athought: Eloquent RT @utahkay: Agile is co-creation of value @cgosimon #Agile2013
  • RT @athought: Eloquent RT @utahkay: Agile is co-creation of value @cgosimon #Agile2013
  • @dominicad: Can your service hold up? Track scale across releases to see points of contention. @MaulanByron #devops #Agile2013
  • @hageyahhoo: Quality Assurance is very hot topic in this conference. Check it! http://t.co/20vQjraVw7 #Agile2013
  • @marcjohnson: RT @simonbrown: I’ve spoken to a bunch of people at #Agile2013 who missed my sketching talk yesterday; here’s a summary -> http://t.co/nysp
  • @aclairefication: Making and keeping promises, even small things, is good practice. Builds trust. - Conversation Katas #Agile2013
  • @davidmezag: RT @jasonlittle: "Conversation is the operating system of organizations"
  • @AlexArms: If you have code that you claim isn't testable, stop. Find a way to test it. Or, rewrite it so it is testable. #agile2013 #scrum
  • RT @AlexArms: If you have code that you claim isn't testable, stop. Find a way to test it. Or, rewrite it so it is testable.
  • @teropa: RT @PrettyAgile: .@jeantabaka's reading list for Enterprise Agility and flow of value #agile2013 http://t.co/O3o1Xzkb06 jj RT @JennBertram: Trying to idiot-proof an org through policies and procedures will almost always guarantee idiotic behavior.
  • @northwaysg: #Agile vs Fragile: Not a Death March. http://t.co/0mxz9tYKJK #AGILE2013 #testing
  • @techometry: RT @MCrank: #Kanbanaroo Time Lapse: http://t.co/lX48Bkb9ab via @youtube Great time lapse of last nights festivities @leanKit
  • .@jeantabaka: "Most notable observation in @Spotify preso was 'cadence'. Even at exec level, talked about weekly cadence
  • @BernadetteDario: RT @jasonlittle: New Post: Recovering from Failure, A Year Later. http://t.co/tdrGCbUWGp
  • RT @astridclaessen: "You must choose one or the other, you can't cut the baby in half" - Tim Lister on Arbitration Awesome. RT @galbraithsimon: The power of the Magic Finger! Tim Lister's insight on preventing interruption at #Agile2013. @ojuncu: The magic finger : points that you're aware of emotions and you'll take care of -Tim Lister #agile2013 #keynote RT @ojuncu: The magic finger : points that you're aware of emotions and you'll take care of -Tim Lister
  • Lister: "Writing is a great way to distill your thoughts. Do I really understand this and fully formed position?"
  • @BeyondReqs: Tim Lister: This conference is all about moving an idea out of one thick skull and into another.
  • @aclairefication: It's great to know that your colleagues have your back. - Tim Lister #Agile2013
  • @ReleaseTEAMInc: RT @RPR_Elon: Tim Lister encourages #agile2013 attendees to WRITE - best way to distill and consider your ideas #amen #myworld
  • Lister: "I've seen two evidence points of a bunch of raving egomaniacs agreeing on something [incl Agile Manifesto]. Amazing!"
  • @LeanKanbanU: .@djaa_dja's observations on how SAFe differs from #Kanban - the anti-SAFe for almost a decade already. http://t.co/0rfFsUSOpD
  • @msilpala: Tim Lister regales the #agile2013 with stories of all the software luminaries who crossed his career path.
  • @theagilist: "I don't believe there are best practices. I just want pretty good practices most of the time." #TimLister #Agile2013
  • @RPR_Elon: RT @aclairefication: Writing as a way to practice, peer review, exchange - Tim Lister #Agile2013 (I'm learning this now. Painful but so wor…
  • @ojuncu: RT @SMRobson: #agile2013 Tim Lister " there is no best practice just pretty good practice some of the time"
  • @ojuncu: Yes! “@holitza: Tim Lister "This conference is about moving an idea from one thick skull to another" some thicker than others... #agile2013
  • Lister: "There's a fine line between asshole and wiseass."
  • Lister: "If your work is not an innate pleasure, use your feet and leave; life is too short; make your own career"
  • Lister: "Notice that once you get good at something, you never do it again. That's life in software."
  • @jeantabaka: #agile2013 Red Gate employee guidance http://t.co/M7cdGgXHWX
  • "Don't be an asshole." Love it! RT @jeantabaka: #agile2013 Red Gate employee guidance http://t.co/M7cdGgXHWX
  • @hamids: @timlister Thanks for reminding us our work should be our "innate pleasure" :) Now back to the booth! http://t.co/cYW0ctR1sn
  • @theagilepirate: RT @marcjohnson: . @redgate getting huge praise for it's culture from Tim Lister in his #agile2013 keynote cc: @theagilepirate
  • RT @marcjohnson: . @redgate getting huge praise for it's culture from Tim Lister in his #agile2013 keynote cc: @theagilepirate
  • @ellengott: tim lister cited "don't be an asshole" rule at Red Gate. the roots? bob sutton: http://t.co/ddA3kEOuaT
  • @theagilepirate: RT @marcjohnson: . @redgate getting huge praise for it's culture from Tim Lister in his #agile2013 keynote cc: @theagilepirate
  • @SMRobson: #agile2013 Tim Lister a great story teller, a great life analyzer, and someone who has mastered the art of the retro. Look back and learn!
  • @aclairefication: Just as you get good at something you never do it again. WOOHOO! This is rejuvenation. - Tim Lister #Agile2013
  • RT @aclairefication: Lister: "Just as you get good at something you never do it again. WOOHOO! This is rejuvenation" #agile2013 #devops