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

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

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
    Stories
    To Do
    Work In P…

Webinar: Collaboration at Scale: Defining Done, Ready, and NO.

I was invited to participate in a Scrum Alliance Webinar.  Maybe you would like to listen to us in a discussion of techniques to collaborate at scale (remotely and with many people).  The topic is one that I've got some experience in discussions - yet I never seem to get to done...
Collaboration at Scale: Defining Done and Ready and NO for Distributed Teams
With Joel Bancroft-Connors, Agile Organizational Coach; David A. Koontz, Agile Transition Guide; and Luke Hohmann, CEO and Founder of Conteneo, Inc.


14 February 2018 11 a.m. ET (USA).




The Scrum Guide is pretty clear on the criticality of the definition of Done: "When a Product Backlog item or an Increment is described as "Done," everyone must understand what "Done" means. However, the Scrum Guide ALSO says that the definition of Done can "vary significantly per Scrum Team." This leads us to examine when and how the definition of Done should vary, how distributed teams should cr…

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…

A FAILURE to Communicate

I was working with a failing team some time ago.  I use "failing" to describe the outcome of the team - not the people on the team.  Are you OK with that description?



An issue arrose in the stand up - a team member that was to verify the quality of a procedure did so and reported that there were a few records that didn't match expectation in the data set.  Upon inquire the number of records not matching was over 2000.  Most people acknowledged immediately the exaggeration - I could tell by the laughter.  After about 10 minutes of discussing the details of the problem - it appeared the team had a handle on the specific situation.

I stopped the discussion and inquired if they could name the impediment.  One team member did a great job of describing the impediment as a _communication gap_.  Wonderful - I could work with that - the problem had a name and it didn't include anyones Proper Name.

"If the problem has a first name; we are going to have a problem."

I&#…