Skip to main content

A Ball of Whacks

I broke out some of my toys in a training class the other day.  A brought out just a few at a time.  Its nice to keep a few surprises in the bag.  Toys add to the fun quotient.

One of the standard toys is a rubber chicken.  This is a fun item to have.  Most people are shocked that I have one and would actually bring it into the work place.  But after they get to play with it, the fear of having fun at work seems to dissipate.

I like the squishy rubber chicken - they come in all types of rubber, you can buy them online - but to get the kind that feel a bit icky (like cold chicken skin) you have to touch and feel them in a toy store.

The rubber chicken can be used for so many things in a training class or workshop.  A "talking token" - only if you have the chicken may you speak.  Or to transport the team forward in time, so that they can Remember the Future.  You've heard of the magic of  waving a dead chicken - right?

The chicken is fun - but the best toy is the Ball of Whacks - it looks simple.  Many people believe it to be some new form of Rubik's Cube - it's not!  They grab it and twist.  Crash all the pieces flip and spin and the ball breaks into pieces.  "Oh, that's not what I thought it was."

The ball is made up of 30 golden ratio rhombic pyramids. With internal rare earth magnets that stick the pyramids together, these design blocks form a perfect 30-sided rhombic triacontahedron an interesting shape.  But the design allows one to make even more interesting shapes.

It is a creative tool and can be used individually or in a group game.  At one client's site I kept it on my desk and every few weeks it would disappear and show up in a new configuration, stay that way for a week or so and someone else would play with it a while to make a new shape.  Some were very creative.

This toy combines two of my favorite things, building blocks and magnets.  I'm a Lego fan from way back,  I once built a road grader from Legos.  But the genius of combining magnets with blocks is astounding.  I think magnets are fun because one can play with a fundamental force of nature that operates on a human scale.  One rarely gets the chance to play with a mysterious force of nature and not get hurt (gravity is fun but the stop at the bottom of the hill can break bones).



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: 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
    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."