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.

      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…

      Requirements Traceability in Agile Software Development

      One of the grim proving grounds for the would-be agile business analyst (henceforth "WBABA")  is the "traceability conversation."  Eventually, you will have to have one.  You may have seen one already.  If you haven't, you may want to half-avert your eyes as you read further.  It gets a little brutal.  But if you close them all the way, you can't read.
      WBABA: in summary, we complete analysis on each story card, and then we support the developers as they build it that same iteration!Corporate Standards Guy:  but how do you do traceability in agile?  You have to have traceability.  It's broadly recognized as an important factor in building rigorous software systems. These software systems permeate our society and we must entrust them with lives of everyday people on a daily basis. [The last two sentences are an actual quotation from the Center of Excellence for Software Traceability website!] WBABA: [cowed silence]Corporate Standards …