Skip to main content

Hurry! Fetch the 2×4 stretcher.

The mythical 2×4 stretcher analogy.

When I was in high school I worked with the school maintenance crew. This was in the late 1970s when schools were growing and therefore tearing down old buildings to construct new modern building on the site. Given that construction of the new building would take several years the problem of where to house classrooms durning the destruction/construction years was typically solved by building classrooms in the gym and auditorium. The first summer I worked with the crew we were constructing one of these temporary classrooms in a gym. I was the gopher for Ike, and old codger who was always up to something. One fellow was measuring and calling out dimensions and Ike and I were cutting 2×4s to length, as fast as we could go. I would hold the 2×4 on the saw horses and Ike would measure, mark, and cut, then I would run the piece over to a pair that would nail it in place. We were all working fast, a well functioning team. When Ike, exclaimed, “$#!T, I cut it too short, Koontz run get the 2×4 stretcher in the back tool box of my truck – hurry! You’ll know it when you see it.” So, off I run to find the stretcher. I pull out every tool in the truck’s toolbox, but the stretcher wasn’t there. So back in to tell Ike and he said “maybe I was using it at home and didn’t put it back, go get Jim’s, hurry! So out to Jim’s truck to rummage through his toolbox I went like a flash.

Well if you have every been played for the fool by a master craftsman such as Ike, you know that he can keep it up all day long, as long as you are hooked and on the string he is intense and serious, and has another place to look. After I finally wised up and “spit out the hook”, the whole crew fell on the floor laughing for 20 minutes. I joined in after about 15 minutes, of being mad and extremely embarrassed. That was the first of many exploits that Ike would lead us on that summer. He worked hard and played hard, all at the same time!

I don’t know of any 2×4 stretcher stories in the software industry, but everyone that has been the young apprentice on a construction site has been asked to go fetch the stretcher. So why are there no good fish tales in software? Well for one reason a 2×4 stretcher is possible in software – it is called a refactoring, for example: Extract Interface. Software is soft and malleable, the rest of the world is not. Therefore a 2×4 stretcher is funny on a construction site, but a real possibility in software.

This doesn’t mean we cannot have fun, however! Why I remember just starting out and having an upper-classmate help me with a sorting algorithm, he took my punch cards and dropped them on the floor.

Post a Comment

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

What is your Engagement Model?

What must an Agile Transformation initiative have to be reasonably assured of success?

We "change agents" or Agilist, or Organizational Development peeps, or Trouble Makers, or Agile Coaches have been at this for nearly two decades now... one would think we have some idea of the prerequisites for one of these Transformations to actually occur.  Wonder if eight Agile Coaches in a group could come up with ONE list of necessary and sufficient conditions - an interesting experiment.  Will that list contain an "engagement model"?  I venture to assert that it will not.  When asked very few Agile Coaches, thought leaders, and change agents mention much about employee engagement in their plans, models, and "frameworks".  Stop and ask yourselves ... why?

Now good Organizational Development peeps know this is crucial, so I purposely omitted them from that list to query.

One, central very important aspect of your Agile Transformation will be your Engagement model.  

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Refactoring_FirstExample.zip Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.


Metrics for a Scrum Team (examples)

What metrics do you collect to analyze your scrum team?

We live in a world of data and information.  Some people have a mindset that numbers will diagnose all problems – “just show me the data.”  Therefore many directors and senior managers wish to see some list of metrics that should indicate the productivity and efficiency of the Scrum team.  I personally believe this is something that can be felt, that human intuition is much better in this decision realm than the data that can be collected.  However, one would have to actually spend time and carefully observe the team in action to get this powerful connection to the energy in a high-performing team space.  Few leaders are willing to take this time, they delegate this information synthesis task to managers via the typical report/dashboard request.  Therefore we are asked to collect data, to condense this data into information, all while ignoring the intangible obvious signals (read Honest Signals by Sandy Pentland of MIT).
What if …