Skip to main content

A Splendid Mirror

Oh the irony of a Pig and Chicken paradigm.


If you know of the Scrum parable of the pig and chicken.  Then you may find this story humorous.   I'm working with a group trying to teach them just enough Scrum to form a project team.  Trying to facilitate just enough team formation to allow them to self organize.  We planed a 3 day workshop, to be immediately followed by sprint one.  It went well.  Although some troubling patterns were apparent, we summoned up the courage to keep moving forward.

Fast forward to Sprint Two's planning session.  Only three of the seven team members were at the planning session, one had to leave for an hour during the session.  The product owner did not appear, the scrum master had a higher priority meeting.  Summing more courage to venture into the unknown the 3 team members and the two coaches (we pair coach teams) ventured into the unknown. We discussed the obvious impediment in the room.  Created a working mitigation plan for the missing product owner and we planned the sprint as best we could without any guidance from the missing leadership.  The team asked for help in raising this impediment.

I sent an email to the team's director - the sponsor of the project, and included the whole team in the email.  An example of raising an impediment, a teachable moment.  Just the objective observation of what was happening, and how it was impacting the team.  Along with some subjective opinion of the risk.

"I'm very concerned with the number and frequency of team members absences from team events and Scrum process meetings.  I've not encountered a successful Scrum team that can operate with this low a level of team commitment to the project."

The private reply was: "Thanks for the email. Who else on the team are chickens?"

Now this question took me quite a while to process.  Oh-boy, wouldn't a face-to-face conversation be so much better.  Have I fallen into poor behaviors?  Behaviors that are in contrast to my principles.

I do not use the pig and chicken joke to teach the distention between team commitment and and stakeholder interest in my practice.  However, it is a well known piece of the Scrum vernacular.  Now, we must sort out this misunderstand of the term "chicken" within the Scrum context.  Who on the team is a chicken?  The obvious answer is no one on the team is a chicken, the team is made up of pigs.  Yet the sponsor, who rightly considers himself just an interested party (a chicken) appears to be searching for a well defined set of roles that will allow him to know who on the team is required for the team's meetings.  And he does this using the exact parable which was used to explain the definition of the term 'scrum team'.

Oh irony - what a splendid mirror you make.

In our 3 day workshop we spent quite a bit of time talking about how words have various meanings to different people.  One word that we used to illustrate this was the word "team."  We did various exercises to define words, to start sharing a common understanding of the words and phrases we use in our work day.  We obviously have more work to do.

What does it mean to be on a team?
Will a group of part-time participants become a high-performing team?
How does one best accomplish achieving low priority commitments?

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&#…