Skip to main content

Waggle Dance -or- Standup Meeting

Bees do a dance that bee keeper refer to as the Waggle dance...

It is with great pleasure that you can watch and using the power of science have this dance translated into English.

Bee Dance (Waggle Dance) by Bienentanz GmbH

What does this have to do with Scrum?  The power of a metaphor was well known to the creators of Extreme Programming (XP) - so much so, that it is one of only 12 "rules" that those really smart people decided to enshrine into their process.  It is also the most likely rule to not be mentioned in any survey of software development practices.  Unless you happen to be chatting with Eric Evens, and he may agree that he's captured the underlying principle in Domain-Driven Design, the Ubiquitous Language pattern.


Have you ever observed a great scrum team using a classic tool of many innovative company environments - the physical visual management board (Scrum Task Board). The generic behavior for a small group of people (say around 7 plus/minus 2) is for the group to discover that a form of dance where the speaker moves to the board and manipulates objects on the board as they speak gives everyone else the context of what story they are working upon and what task they are telling us they have completed. Then they exit stage left - so to speak. And the next dancer approaches from stage right, to repeat the dance segment. Generally speaking one circuit of this group is a complete dance for the day. The team is then in sync with all there team mates, and may have negotiated last minute changes to their daily plan, as the dance proceeded. In my observation of this dance great teams complete this ritual in about 15 minutes. They appear to need to perform this dance early in the morning to have productive days. And groups that practice this dance ritual well, out perform groups that are much larger and groups that don't dance.


So going all honey bee meta for a moment...  Let's use our meta-cognition ability to think about the patterns.  We love to pattern recognize - our brain is well designed for that (one of the primary reasons a physical visualization of work is so much more productive as a accelerator of happiness than virtualization of the same work items).

When do we use great metaphors - in design great NEW experiences for people that are reluctant to change.  And to communicate the desired behaviors, the exciting new benefits to adopting something new.  I'm thinking of the 1984 introduction of the Graphical User Interface by the Apple pirate team that produced the GUI, the Mouse, the Pointer, the DropDown Menu, etc.

Can you see a pattern in this... a pattern that relates to people changing systems, behaviors, disrupting the status quo?  It is resonating in my neurons, I'm having a heck of a time translating these neuron firing waves of intuitions, into the motor cortex to make my stupid fingers pound out the purposefully retarding movements on a QWERTY keyboard to communicate with you over Space-Time.  If only we could dance!

See Also:

The Waggle Dance of the Honeybee by Georgia Tech College of Computing
How can honeybees communicate the locations of new food sources? Austrian biologist, Karl Von Frisch, devised an experiment to find out! By pairing the direction of the sun with the flow of gravity, honeybees are able to explain the distant locations of food by dancing. "The Waggle Dance of the Honeybee" details the design of Von Frisch's famous experiment and explains the precise grammar of the honeybees dance language with high quality visualizations.
This video is a design documentary, developed by scientists at Georgia Tech's College of Computing in order to better understand and share with others, the complex behaviors that can arise in social insects. Their goal at the Multi-Agent Robotics and Systems (MARS) Laboratory is to harness new computer vision techniques to accelerate biologists' research in animal behavior. This behavioral research is then used, in turn, to design better systems of autonomous robots.



I was just reminded of @davidakoontz's wonderful metaphor for the daily #Scrum: waggle dance :) pic.twitter.com/h3c1B49mkC

— Tobias Mayer (@tobiasmayer) April 7, 2017


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…

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…

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…

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Refactoring_FirstExample.zip Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.