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

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.

In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.

Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    To Do
    Work In P…

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: 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, …

What belongs on the Task Board?

I wonder about these questions a lot - what types of task belong on the task board?  Does every task have to belong to a Story?  Are some tasks just too small?  Are some tasks too obvious?  Obviously some task are too larger, but when should it be decomposed?  How will we know a task is too large?

I answer these questions with a question.  What about a task board motivates us to get work done?  The answer is: T.A.S.K.S. to DONE!

Inherent in the acronym TASKS is the point of all tasks, to get to done.  That is the measure of if the task is the right size.  Does it motivate us to get the work done?  (see notes on Dan Pink's book: Drive - The surprising Truth about what motivates us) If we are forgetting to do some class of task then putting it on the board will help us remember.  If we think some small task is being done by someone else, then putting it on the board will validate that someone else is actually doing it.  If a task is obvious, then putting it on the board will take vi…

A T-Shaped 21st Century Knowledge Worker

Knowledge workers in the 21st Century must have many areas of deep knowledge, while also be capable of collaboration across multiple other domains with dissimilar T-shaped individuals.  This description of a person is a metaphor.  Compare it to the shape of the "I" in the classic saying there is no "I" in Team.

I first read about Scott Ambler's term "Generalizing Specialist" - but it's so hard to remember the proper order of the words... get it backwards and it has an inverted meaning... T-Shaped is easier to remember. 
A generalizing specialist is someone who:
Has one or more technical specialties (e.g. Java programming, Project Management, Database Administration, ...). Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new skills in both their existing specialties as well as in other areas, including both technical and domain areas.  General…

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.


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…