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

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.

Introduction

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…

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

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…

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…

Team Performance Model - by Drexler and Sibbet

Many of you have all heard of the Tuckman model of team dynamics (Forming, Storming, Norming, Performing).  It was created in 1966 and has become the most popular model for describing team behavior.  Is it time to level up in your mental model of team dynamics?  Are you ready for a richer more functional model?



Introducing the Team Performance Model by Drexler and Sibbet



Orientation - Why am I here?
"Orientation is about understanding the purpose of a team and assessing what it will mean to be a member.  you need to understand the reason the team exist, what will be expected of you and how you will benefit from membership.  In a new team, these are individual concerns, because the group is only potentially a team.  that is why these concerns are illustrated as occurring in your imagination at an intuitive level.  As a team leader it is important to provide time and space for people to answer these internal questions themselves."

Keys to when Orientation challenges are resolve…