A Lingua Franca between the Three (or more) Amigos

There were a couple dozen people who showed up at the Fool, last night, for my presentation on A ”Lingua Franca” to Ensure You Get the Right System.  I’d like to thank them all for coming and for such lively participation.

These are exciting times.  The tools of acceptance testing and behavior-driven development are progressing beyond the domain of the techies.  They are entering the realm where they can help the Whole Team.

Using these tools, or even better ones to come, the Three Amigos, Developer, Tester, and Business (and User Experience expert, and Manual Writer, and …), can invent their own shared language, specific to the system under development, to talk about what the system is supposed to do.  The acid test: that the Business representative feels comfortable reading the examples written in these terms and definitively say, “Yes, that’s what I mean” or not.

After the presentation, Uncle Bob Martin showed me the Given When Then capabilities he’s added to Fitnesse since I last looked at it last fall.  Other tools mentioned included Cucumber, SpecFlow, JBehave, easyb, GivWenZen, Morelia Viridis, StoryQ, and StorEvil.  I’m sure there’s more to come.  And, as we use these tools more and more, I’m sure that we’ll develop patterns beyond Given When Then and language specification tools beyond regular expressions.

Just remember, it’s not the technology that’s important.  It’s the communication between the Three (plus) Amigos.

Post to Twitter Post to Plurk Post to Yahoo Buzz Post to Delicious Post to Digg Post to Facebook Post to MySpace Post to Ping.fm Post to Reddit Post to StumbleUpon

Comments (7) to “A Lingua Franca between the Three (or more) Amigos”

  1. […] long term results, but I’ve had some success using automatable examples as a tool to enhance the conversation between the customer, the tester, and the developer.  Not to replace the conversation, or to send one person off to write tests, but to add precision […]

  2. […] to be in on the discussion (User Experience? Ops?) to talks about it.  (I call this a meeting of the Three Amigos.)  What is the one obvious thing that needs to be done? (Hint: it’s not “login.” […]

  3. […] the PO gets together with dev team members, she should strongly consider making sure that the three amigos are […]

  4. […] All of those actions or activities are perfectly fine. But I’d like to reframe your value proposition around driving collaboration in what Ken Pugh defines as the Triad and George Dinwiddie defines as the 3 Amigos. […]

  5. […] to be in on the discussion (User Experience? Ops?) to talks about it. (I call this a meeting of the Three Amigos.) What is the one obvious thing that needs to be done? (Hint: it’s not “login.” […]

  6. For more information on The Three Amigos, you might check out my Better Software article, “The Three Amigos — All For One – One For All” (available on Sticky Minds) and AgileConnection article, “The Three Amigos Strategy of Developing User Stories.” (links updated 2016)

  7. […] on an agile team, I was interested in this idea of a lightweight way to collaborate better on three amigos meetings for planning work. However, as much as I love testing every day at VersionOne, I wanted to try a […]

Post a Comment
*Required (Never published)