Skip to main content

Snapshots of the ThoughtWorks NA Away Day

I spent the weekend with most of my North American ThoughtWorks colleagues at an event called the "North American Away Day."  It was a pretty overwhelming experience, overall, but here were some highlights for me:
  • Filming a ThoughtWorks "It Gets Better" video with LGBT friends and allies in a beautiful gully outside the St. Charles, Illinois, venue.  Rajiv Mathew kindly shot the video--he is amazing. (photo courtesy of Chris Stevenson).

  • Meeting Christopher Atkins again, and finding out about his blog.  Check out this beautiful Tufte-quality graph depicting the value of agile methods. 

  • Hearing Amy Goodman of Democracy Now! speak--she is the most amazing speaker I have ever experienced.  If you're sitting around feeling depressed and worried that we don't have any independent press any more, she's way ahead of you, and thank God for that.
  • Finding out about OpenMRS, an organization creating a software platform to be used to track medical records (rather than some old Access database) -- it is used all over the world!
  • Seeing colleagues recreate the "Yes Dance" Youtube video during the (3+ hour!) talent show on Saturday night.  I'm pretty sure we all spent the weekend "Yessing too hard."  (Pretty sure that a whole week of this would kill me!) (Photo stolen from Ethan Teng)
    • Wearing a false mustache and dancing onstage for the talent show with collegues at ThoughtWorks Studios (sincerely hoping that photos of this do NOT surface--but it's significant consolation to know that the mustache will protect my identity)
    ThoughtWorks is an amazing company, and not just because the people are brilliant software development practitioners.  What a privilege to work here.

      Comments

      1. Is this the type of picture you hope won't surface? https://picasaweb.google.com/104043489601304192916/TWAwayDay2011?authkey=Gv1sRgCNWR1oL-0_m9Yw#5614657801908002194

        ReplyDelete

      Post a Comment

      Popular posts from this blog

      A Corporate Agile 10-point Checklist

      I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today.  Some of these might even apply to you if you're in a smaller place.  So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else.

      Here's what you should think about:

      1.Your staffing pattern.  A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios.  So as you provision the project, check to see whether you can arrange this staffing pattern.  If not, you will encounter risks because of missing people.  Concretely it means that:
      a.You need your user experience people (if applicable) and your analysts at the beginning of the project, as always, b…

      The Agile Business Case

      Many agile teams have never seen a business case, ever, and they may even be proud of it.

      Our mantra is that we deliver "business value," not just "software," quicker, better, and faster, but if so, we certainly don't spend a lot of time reporting on value delivery, and in fact we may be scornful about "analysis paralysis."  As software developers, we consider ourselves to be doing quite well if we can deliver the software every two weeks (or continuously).  And this is particularly if we've enabled this frequent high-quality delivery through automated testing and automated build-and-release techniques.  We've reduced business risk by making results visible more often, and allowing the business to change direction more frequently.  We assert that along the way of course we're also delivering value.  But how would we prove it?

      I've recently posited that we shouldn't even think of doing agile projects without capturing and recording s…

      How To Write A One-Page Proposal to an Executive

      One day you may need to communicate with an executive. Pro tip 1:  executives do not have time for you to dim the lights and show them forty slides with charts composed of animated dancing leprechauns and flashing arrows that emerge from the void in a checkerboard pattern. Pro tip 2:   Guys, and gals with deep voices, executives also don't need you to use your "Radio Announcer Voice."

      As a rule, what executives want is simple: one printed page. No matter what it is, it should be one page. And it should be printed, not emailed.  You should plan to hand it to the executive, and then you should be quiet when they read it and wait for their questions.  It's harder than it sounds.
       So how do you do it?  Here are the steps:
      Write the deck that expresses your proposal in as many slides as it takes.  Use imaginative animation and blinking letters if you must.Remove your title slide.Insert a new slide at the front of the deck with "Appendix" written on it in big …