Skip to main content

First thing we do is Review

I'm working with a wonderful team this week in a unique "kickoff" or as we call it in our vernacular a team launch.  Here I have a mental image of an aircraft carrier with a plane on the flight deck, cocked and locked in the steam powered slingshot.  The flight control officer drops a flag and pow the team takes flight off the deck and into the air - easy, peasy.

A new experiment I've tried in this launch is the one hour iteration.  We have been working day in and day out all week.  However I've set a cadence of one hour iterations.  We start promptly on the hour, work in the iteration for 50 minutes and break for 10 minutes (yes you're thinking of tomatoes).

I've started each iteration with a mantra, "First thing we do is Review."  After 3 days the group is now doing this with out my prompting.  Heck just yesterday, they even started 1 minute after the hour because I didn't stand up and start the meeting promptly.  Yes, I was sitting calmly watching the clock, waiting, like a viper ready to strike.  I had decided when to act (5 min past the hour).  But one of the team members reminded me of the time to start, and with just the slightest encouragement, off he went and started the meeting with a review.  It's a proud moment when the plane makes it off the deck for the first time.

Yesterday I also broke cadence - slightly by accident but heck I'm a consultant - I've learned the art of turning my mistakes into learning moments for the group.  During one iteration we didn't end on time - we ran 5 minutes past the XX:50 mark, so I announced twice we would start at 10:05 AM.  I got into trouble with the team at 10:02 for not starting on time.  Explained that I had adjusted their schedule and announced it - ah-ha it's their "fault" for not listening.  No, it's my fault for breaking cadence!  But it is a teachable moment.

Now do you think they will see the fractal nature of this workshop and the Scrum cadence of a Sprint, of the Daily stand-up meeting where the first thing they say will be a review?  Then a plan for the day.  I've got a game I want to play with them - a metaphor for this - and like the viper I'm ready to strike.

I hope I've put enough steam in the launch piston - I see the flag dropping.

See Also:

Liftoff: Start and Sustain Successful Agile Teams by Diana LarsenAinsley Nies 

Patterns in Nature - is there a fractal nature to the universe?





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