Saturday, February 5, 2011

Culture, with a Story About Everything

Culture is everything people learn, believe and consider real that is apart from their genetically determined physicality. Culture lives in people and is preserved in imperfect artifacts that transmit information when new people engage them. A bit of culture dies with every person, and a slightly different culture is relearned and recreated by following generations.

Culture is a living meta-creature. We may think some things are true and unchanging, but we re-create them every generation, factoring in our own needs and experience. We cannot live, even imagine very accurately, outside of our own time. Consequently, history is tricky and subjective.

Culture has limits. We are incapable of avoiding certain repetitive patterns such as war because true, awful experience dies with the experienced. Culture cannot transmit deep visceral, horrifying experience to enough new people to prevent new wars and other terrible recurring cultural patterns.

I wrote the above on FaceBook in response to a question from one of my beloved daughters, Meg, "What is culture?" It seemed worthy of reproduction, editing and extension here. I am not a cultural anthropologist, have no specialized training. So what I write, distilled from my life experience, is probably not new. Very little is new.

The culture of the past two hundred years has been grossly distorted by abundant fossil energy. We have come to believe culture has somehow advanced or progressed. The Great War killed the idea of human perfectibility for that generation, but like a weed, "progress" springs up again in the popular imagination. We just take for granted the electronic marvels that have so changed how we communicate and learn in a mere decade. We do not understand the energy it takes to develop and manufacture what will soon be yesterday's quaint marvels. We do not grasp the intricacy and fragility of the interlocking technology network. We have put culture on steroids. One fairly grim consequence, the AK-47 is ubiquitous. But losing hope would be the wrong interpretation of my little tale.

The great distortion in human circumstances since the industrial revolution was and is completely dependent on abundant supplies of energy, mostly finite fossil energy, and the new materials and methods that energy has made possible. We cure disease with that energy, redirected with all our mutual cleverness. We feed a vastly inflated world population with crops bred to respond to massive amounts of fertilizer and pesticide from petrochemicals. These crops respond to mechanical cultivation, fossil fueled, of course. Like every civilization before us, clear challenges line the horizon, but we really believe we can solve any problem. Solve it before the consequences of that problem take large numbers of us out in a massive orgy of misery.

I sail a small, fiberglass, aluminum, Dacron and polyester sailboat on the very sea men have sailed for eons. I have come to appreciate that ancient people knew more about harnessing the wind and traversing the sea than I shall ever know. The only difference is I have access to more useful materials. That, I submit is not really progress, simply better tools. I do not risk my life making a living from the sea. I don't really know how. They could do it 1000 years ago and did. For all my technology, I am ignorant as a baby compared to my seagoing fore-bearers. I cannot fit the concept of progress into this picture.

Those of us in relatively new societies, like the USA, have short cultural memories. This leads us to simplify issues. Peoples with longer traditions, Serbs, Albanians, Jews, Palestinians to pick a few you may recognize, live in a present which includes an ever living past. The emotional fire of ancient wars, massacres and genocides can be as real as going to market yesterday. These ancient cultural realities combined with exploding populations without economic future cannot be defused. They will play out over hundreds if not thousands of years. One might think I would be a pessimist. Once I was.

So it may seem strange that I am optimistic about the future of Homo Sapiens, our species. I'm optimistic about my life and my grandchildren because there is no percentage in pessimism. Yes, there's lots of bad stuff, but almost all of it is out of my control. So I chose to focus on what I can influence, which is this glorious day. One day in my lifetime, one day in the Earth's 4.7 billion year lifetime. Mere existence is such a thrill.

I must digress on ancient peoples to establish perspective. Our biological relatives, other hominids, migrated out of Mother Africa many times over at least 2.5 million years, spreading in various directions. They left clues which allow us to deduce their existence. The currently dominant view among scientists who devote their lives to studying such things, is that all people alive are almost entirely descended from a small group of people anatomically identical to us. This small group of direct ancestors, Homo Sapiens, as few as 50 thousand people, migrated out of Africa perhaps 50,000 to 100,000 years ago. More intelligent and adaptable than older lineages of hominids, they replaced other hominids, with some interbreeding of course, and spread to every environment on the planet.

Some 10,000 years ago we humans developed agriculture. Settlements followed, civilizations developed, government, organized religion and all the rest. The earth is about 4.7 billion years old. Life arose on earth about a billion years later. Some view the universe as a complex self-organizing system. Complex, self-organizing and unpredictable from the big bang onwards. Life seems inevitable in such a system. We are an instance of life. Self-organizing life.

But the entire history of intelligent life here is a mere blink in the history of the Earth. We have greatly changed the face of the earth. We are the first great, continent resurfacing intelligent species on earth. Anyone coming after us will unearth our works, sift through our landfills and wonder. Homo Sapiens took a developing planet and altered it unmistakably. Rarely altered it for the better if you look at it from the viewpoint of the planet or the biosphere. Subdued it we have. Humans are extremely adaptive and ubiquitous. We can eke out an existence almost anywhere in the terrestrial biosphere.

It has been mathematically proven that history is not deterministic. The future is unknowable, unpredictable. Every non-trivial prediction about the future is wrong. Nevertheless, if enough predictions are recorded, some come close enough to future events that we laud their authors as prophets. But prophets are right only once, thus proving by another, weaker method that the future is unpredictable.

The fun of thinking about things on a large scale is to create a plausible story about the future, sort of like science fiction. This is my story. It is most certainly false except in the most general possible way. But fictions can give us hope, can let us willfully deny the arbitrariness of the future. Fictions can give us faith. As a species, it seems to me we need faith to move forward against what seems to be an impossibly hostile future.

We are cresting a bubble fueled by fossil energy. This energy has permitted our species to increase in numbers vastly higher than the Earth could otherwise support. The ultimate drug, energy. We have reached the point where we are probably changing the climate of the planet. Planetary climate has a wide range and, if history is a guide, can exist in many varied stable states besides the one we currently enjoy.

One scientific suggestion is that Homo Sapiens is the naturally selected product of a long period of climate instability in Africa. Wet, dry, hot, cold - quick flips that rendered many less adaptable creatures extinct. We were pressed very hard and many died. Our forbearer hominids had the genetic prerequisites and variations, so to speak. The best adapted to surviving fast, huge environmental changes survived, became Homo Sapiens, us. Perhaps larger brains and language were the result of this terrible pressure to survive constant change.

What is different now is that we fully inhabit the planet, not just part of a continent. We are more adaptable and resourceful not because we are much smarter, if at all, but because we have infinitely better tools. Any horror we can imagine, including full thermo-nuclear war, vast climate disruption, asteroid hit, famine, plague, volcanic eruption, will probably be insufficient to wipe out every last settlement. Only the minimum human breeding population - perhaps 2000 people, need survive. The planet will survive as it always has, probably in some form that will support human life somewhere.

That part, the survival of just enough, is sort of based on probability, based on the effect of tools and culture and sort of based on hope. Unknowable, remember. Given time, which the Earth has plenty of, those future humans will know what we know from having decoded our garbage. Hopefully they will have developed some characteristic that allows them to avoid our fate. If not, the earth has time for more cycles of boom and bust in the inevitable self-organizing path to sustainable intelligent life.

This process is probably taking place on other planets revolving around other stars as well. Is there intelligent life elsewhere in the universe close enough to contact? Maybe not. Perhaps in our neighborhood, we are THE instance of intelligent life in the process of evolving the universe. We are just not ready to fly yet. Another 10,000 years, the same interval since we invented agriculture, things could be unimaginably different. And a million years? Who's counting years on a planet that has existed for 4.7 billion of them and will exist for at least several billion more? Perhaps the next step in the self organization of the universe is to become intelligent itself in some way we cannot understand, but in a way in which we played a part. We primitives, we cavemen with our addiction to fossil fuel and wreaking havoc on our partners in the biosphere. The first to leave big footprints on the planet. Probably not the last.

So that is my happy ending, smile or frown. At best a wild-ass guess in vaguely the right direction. In my story, everything really does work out in the end. We're just fixated on the wrong time-frame. Our imagination lacks enough zeros. As a population, our job is to work, eat, grow, nudge the culture and reproduce. Lives upon lives upon lives. Tiny bits of existence to experience and wonder about. Our lives have meaning, just not very much in the scheme of my imagination today.

We cannot stop reproducing, cannot stop or even influence the process very much. The problem space was bounded long before we got here. Wait, maybe descendants of the whales populate our bit of the Universe. Nah, that's a movie plot.

Friday, February 4, 2011

The Letter to our Grandchildren

Hi Nathan, Jacob and Katy,

Grandma thinks it is time we started to develop some better lines of
communication with you. So she has pestered me to write this. Well,
not that I resisted, I just had to think about what to say.

This may be a new idea for you, but Grandparents can be very useful.
We accept you for whoever you are all the time. We never expect you
to be anything other than you. We support you. We are always
available. You can call or write or Skype or whatever. We are
extremely non-judgmental. We think you are terrific who ever you
decide to be.

Both of our grandparents were important in our lives. We are who we
are because of their example and support. Julie's two grandmothers
sent her a full set of household stuff when she ran away from home at
18 and married Bobby. Julie's mother abused her, verbally and
physically from age 10 to 13. She told Julie she was ugly. She she
yelled at Julie and told her she could not show any emotion in return.
When Julie left home, Julie's mother was furious and her father was
distant. Julie's Mother stayed furious with Julie from 18 to 34.
Frances was an angry woman. (they made up finally) Julie had no where
to turn except to her grandmothers. There are plenty of other stories
like this. I just wanted to give you an example.

We want to return the favor to our grandparents. We could never do
that in a meaningful way while they were alive. We were too young.
The way we pay them back is to be as good to all of you grandchildren
as we can be. We have no program, advocate no agenda. We're just
here for whatever comes up. What happens between us stays between us
if you want it to be that way.

We did not get a letter like this from our grandparents. It was a
different time and people thought differently. But we both think we
would have had a much easier time of it if we HAD gotten a letter like
this. Here it is.

Talk between yourselves at some point and make sure everyone gets the
letter. I don't know if I have the right email for everyone. I will
not write a letter like this again. This is the first and only. If
you don't understand something I write about, be patient. You will
understand when it is time.

We love you much more than you can understand. We did the best we
knew how raising one of your parents. You are the wonderful result of
our efforts, our nudges to guide your parent. We are pretty happy
with all of our children. We think you are very lucky to have good
fathers. In large measure, they learned to be good fathers because
David's father and grandfather were such good fathers. The skill gets
passed down when things are working at their best. You always have to
make a lot of it up on the spot, you never get it right every time,
but if I remember the place my father came from toward me when I was a
kid I have a clue how to raise you. Irving loved me so much. When
you love someone, you do your best for that person.

Grandparents are not as closely connected with the day-to-day bustle
of your lives. Your parents have hopes and dreams for you. They are
guiding you in the best way they know how. They care very deeply.
The stage of life you are entering, adolescence, can be very tough.
During this time you figure out who you are, you try on various
behaviors to see what works. Usually you are terribly insecure, not
because anything is wrong with you, but because you do not yet know
enough to recognize that you are just fine. What you are feeling is
normal, whatever that is. Parents sometimes are too close to the
situation to be neutral. Parents have ideas of who you will become,
but we very rarely turn out just as our parents wished. That is
because we become ourselves, not just a projection of who they think
you should be.

It is rarely a good idea to fight with your parents, although part of
the process of becoming an adult involves creating your own identity.
Sometimes that means rebelling against them in some way. You do what
you have to, hopefully with love. You know your parents best. Some
kids refuse to really talk about what is going on with their parents.
I was lucky enough to never get out of genuine two way communication
with your fathers when they were going through their teen years. We
could always talk, and we both think that helped. But we are us and
you are you. "Your mileage may vary," as the sticker says. We each
have unique, different lives. We each have the incredible opportunity
to decide who we will be as adults. From this point in your lives,
you could be anything. You will try out lots of ideas. You will
change your mind. You will be uncertain and may feel like walking in
Tibet. You will get stuck and unstuck. You will have the first loves
of your lives. By the way, you get over the breakup, because
eventually it usually breaks up because you change as people. But you
never forget your first love. Every love of your life, really. But
the first serious deal you never really get over. Everything for the
first time. I could go on for hours and write a complete book on this
subject, if I wanted to.

The point is, Julie and I were exactly where you are and wherever you
go. We went through every life stage you will go through. We have not
forgotten in the least what it was like to be your age. Julie and I
like to say that inside Julie is a shy little girl about nine who is
very innocent and pretty. The little boy in me and the little girl in
Julie are good friends. We are buddies and you could never pry us
apart. We have a rich relationship as adults, but we are friends with
who the other person was at several ages. This is something that can
take a long time together to develop, but it's a sign that it's real.

You will fall in love. You will think that you and your love will
somehow become one person. Almost everyone goes through that. It
never lasts because it is untrue. You are really different people,
would not be half as interesting as if you were the same.

Not volunteering information is not lying. You all look after your
own interest. Don't tell a fib, but don't spill the beans either if
the result will be bad. You may be accused of lying, can't prove it
until you confess, generally. we just see it as survival. This rule
applies all through life. What people do not know sometimes does not
hurt them. The instinct to share every last bit of your life history
with someone is generally a bad idea. Better save some things for
surprises later. Don't tell people things that will hurt them. You
will feel rotten later.

You will each carve out an independent trajectory through life, be a
person who never was before and will never be again. You will decide
things, be careful about decisions that limit what you can be or do
for long periods of time. What is fun for two years is not
necessarily fun for twenty. You will make what seem like horrible
mistakes. Keep it together and you will come out of it. Never be
with a violent person. Never stay with anyone who hits you. there is
a parental exception. Parents get to raise you as they think best
until you are of legal age. Your parents may get angry with you.
Handle it as best you can and try to avoid whatever triggers the
anger. Do whatever you need to to retain your sense of self-worth
and respect. You already do that, I'm just saying it is normal not
evil. At 18 you can change arrangements or not.

Please feel free to share this with your siblings in your own words
they may not understand reading it. You know the answer. They will
not understand much and you may not understand yourselves for another
ten years. hang on to this and other letters we exchange. You will
understand what we mean when the situation arises. Go easy on each
other, you will be a lot stronger watching each other's backs than
competing with and fighting each other. I have not written anything
that would surprise any of your Fathers. They know this is how we
feel and this is who we are. So you should talk about it. this is no
secret, this is how family works. If you sense you will get a bad
reception, then wait for a better time.

We claim the right of grandchildren and grandparents to communicate
with or without their parent's approval. We claim the right of
family.

Your Grandparents, Julie and David.

Thursday, February 3, 2011

Weakness, Strength and the Agile Hero

Some posts back, (http://swimbladder.blogspot.com/2010/10/spider-in-my-head.html) I proposed to make my shortcomings public to save everyone the time it takes to discover them. Everyone has weak areas. You do not fully understand anyone until you figure out where they are not strong. It is possible to develop workarounds for weakness, but a terrible lot of work. I was a very shy, stammering child and I have learned to speak in public and to be a successful salesman. But I am still that shy kid inside and once in a while he pops out. It is good to understand your weakness because you can team with others who have complementary strengths. This post is about weakness and strength, with a brief meditation on heroism for the Agilist.

I am very bad at acquiring names. When I meet you for the first time, if you wear a name tag or hand me a business card, I will keep peeking as we talk. If I physically write your name down, please do not take it as a sign of disrespect. By doing so I am fairly likely to remember your name. The kinesthetic act of writing facilitates my making this sort of memory.

I have worked on this problem for years with little progress. If I try one of the prominent name remembering methods, it takes so much effort I don't catch what what you are saying. I focus on your visage and message. Your name just vanishes. If you are a really attractive woman, I confess I am more likely to remember your name. Perhaps the association with potential physicality trips the switch. I really don't know.

If you repeat your name it doesn't help. I remember people photographically. I can picture you in my mind without effort. Meeting again, I probably instantly notice if you have gained or lost weight or now fix your hair differently. If I look at you embarrassingly however, please prompt me. Kinesthesis is apparently part of my name memory-making process. If I make notes, whether reading a book, listening to you talk or studying for a test, I remember more. This works even if I never look at the notes again. I'm sure Dr. Oliver Sacks could explain all this very satisfactorily and probably has.

My son, Scrum trainer Scott Dunn, embraces the concept that focusing on weakness is looking at the wrong side of the coin. Because weakness is so difficult to “solve,” Scott helps clients focus on their strengths. He uses a well-respected tool developed by the Gallup organization, StrengthsFinder, to identify what people are good at. Effort put into employing and improving your strengths is much more likely to pay off than chipping away at those annoying weaknesses. There is a strong message about the utility of working in collaborative teams here which you can work out for yourself.

We should not ignore our weaknesses, but team with others who are strong in those areas. “Hire toward your weak side” is classic management advice and difficult for many to put into practice. If I hire people more qualified than me, the little voice inside your head natters, they will overshadow me and I will fail. Oh Fear, Fear. We all experience fear at some level unless we are psychopathic. Courage is moving forward in spite of the fear. Heroism is putting yourself in grave danger, often an individual's final act. Have courage, but being an Agile hero may well end your ability to contribute at your current place of employment.

In the West, we celebrate the Spartans at Thermopylae, who set a standard for ultimate courage and sacrifice, but not heroism. Heroism is impulsive, accidental, stupid or all three. No one should set out to be a hero. Heroism is the creation of war propagandists, politicians and other venial creatures. I profoundly respect fear. Fear is healthy, fear keeps us alive. Being fear's captive protects you if hiding is a successful tactic.

But cowering is not generally positive business practice. If you shut down with fear you cannot access your strengths. Be confident enough in your strength that you can act in the face of your fear. Easily said, I know. A bit of a slow learner in this regard, I spent 20 years in management before I was really confident enough to consistently hire to my weak side. If you are not there yet, you are in good company, but keep working on it. Moving past your fear is worth the effort. Revealing your weakness is optional.

Sunday, December 12, 2010

Story Mapping is for Software

Story mapping is a very useful method for visually organizing the development of a software product. When we develop anything physical, story mapping ceases to be applicable and useful in the same way. Story mapping succeeds with software because software is intangible and can be constructed in almost any order. Software is only information. Both physical and software products can be described succinctly in the aptly named “elevator pitch.” Such a brief story can be implemented in software in an abbreviated path. Some input creates some output. Once it exists, a logical point in the code can be “widened” so that the point contains more complexity. If the rudimentary path can be demonstrated, each addition to that path can also be demonstrated. Refinement is everything and can be witnessed all the way.

Physical objects do not behave in the same way. I cannot create a real path through a circuit until some prototype of the circuit is physically built. Mathematical modeling is very useful, but it is only an approximation of the behavior of the real thing. Writing software is not modeling, it is the real thing. I can write instructions for building a wall, but the wall does not exist until it is built.

Story mapping involves listing major features of the software in some logical order. Typically the features are written on cards placed above a horizontal line, perhaps in the order they sensibly take following a work-flow path. Below the line, each major feature is decomposed (and described on a card) just enough that, taken from the beginning to the end, they form a “walking skeleton” of the software product. The logical flow of the product can be described, coded in rudimentary form, and demonstrated on a computer. Each element of the walking skeleton may be further decomposed as desired and written on cards that are arranged below their parent story. Another description of a walking skeleton is sometimes described as a rifle shot. A “rifle shot” through a proposed software product is a narrow path of functionality that includes every major group.

The horizontal axis of a story map is usually functional order. The vertical axis can be ordered in many ways, which gives the method it's power. Horizontally, one row of detailed stories can be assigned to each of the major user personas who will deal with the software. Rows can be assigned to software releases where everything in that row enhances the skeleton in the same logical way. Mapping elaborated stories in this way allows them to be arranged and developed in some strategic order. Commanded to produce the most valuable additional increment of user functionality with each sprint, the story map helps order work by business value. Story mapping as discussed here follows Jeff Patton's original description published in Better Software, January 2005.

Because the development of physical products proceeds differently, story mapping often leaves Product Owners in the physical domain scratching their heads over how to usefully apply the idea. Product functionality can still be arranged along a horizontal axis, but the order is somewhat arbitrary. We cannot order up a “walking skeleton” of our product from the machine shop. Product owners must create a strategic development path for each technology, each major feature. The concept of arranging product elements on a suitable coordinate system must be a bit more artfully applied.

The same objection applies to the "layer cake" and "sashimi" metaphors. With a physical product, thin slices are only sections and have no functionality or "business value" in Scrum terminology.


Saturday, November 13, 2010

Rip Van David

I am applying Scrum in non-software product development. I believe, together with a few others, that Scrum is applicable well beyond software. So I'm right on the cutting edge. This is a progress report on what I have learned so far. Although right on the edge, I am not bleeding yet. But I have just started.

I worked for nearly twenty years helping very dysfunctional entrepreneurial companies recover. Then, perhaps when I was ready, I was fortunate to run a very small, highly productive design and build operation for a few years. Work had never been so much fun for me and for most of the other people involved. We had plenty of what Daniel Pink now calls prime human motivators, autonomy, mastery and purpose. We had the autonomy to work without intrusive supervision, the ability to grow quickly towards mastering our jobs, and we felt purpose in what we were doing.

Then I went off and did something totally unrelated for ten years. I became an electrician fixing problems on recreational boats docked in several LA and OC harbors. Then I came back. I thought I knew something about high performance teams and understood even more now about working with people. Scrum actually found me. A framework for creating hyper-performing software teams, Scrum basically creates a small cell of knowledge workers. Special conditions are maintained within that working cell where people are encouraged to manage their own work, learn more about their craft, and build something of recognized value. Wow, that sounded a lot like what I had done 10 years earlier. Autonomy, mastery and purpose. After some due diligence and training I was hooked. I studied until I thought I understood why Scrum worked.

Understanding "why" was important because I became hooked up with some Scrum radicals who thought the basic values and principles in Scrum could be applied across many different kinds of knowledge work. Scrum was designed for software and is almost universally taught together with practices that usually work in software environments. Be careful what you wish for. I recently landed a job as ScrumMaster appling Scrum to designing small, complex machines. Almost immediately I had to start modifying things. The practices in Scrum work well in software, but can be comically inappropriate in other contexts. I believe the values and principles will hold up and are the source of the benefit anyway.

In Scrum, the entire set of known potential features for the software is called the backlog. The backlog can contain many more features than actually end up in the software product. This is fine, because developers can work on any feature in almost any order. If you order the set of features by business value and start from the highest value end, by the time you run out of money you have the best features working and can throw away the less important stuff or save it for later.

Building a physical product, you also have a set of features. But the set is much more bounded. The device will or will not have certain features. You may have more flexibility changing features with a Scrum-like process, but physical items are not nearly as plastic as software. There is a set of features the product must have right from the very beginning. A toaster is not a television. It matters very much which features are developed in what order. You may still have a backlog, but prioritization is much more complex than by "business value." Prioritization is much more about risk. You investigate the mystery features first, the stuff you do not know how to do, the things that can be solved several different ways. It makes a difference. Most of the final cost of a product is determined by design decisions made at the beginning of the process. So, I'm modifying one Scrum practice heavily, with an unknown number to go.

I said I would be the ScrumMaster in this new job. The ScrumMaster is not supposed to voice opinions. The team decides how to proceed with the work. Well, those of you who know me suspect I will violate this rule right away. Maybe and maybe not. This is new territory and I have had to make some quick calls. But I can operate with a very light touch. I promise not to dominate the team. I really believe their combined expertise in the product area exceeds mine. But control of the process is the ScrumMaster's job. I'm just going to have to redefine the process a bit too. If I have an opinion and they don't think of it independently, I have ways to suggest just by asking innocent questions. This is definitely a job for an old dog.

Perhaps you know the story "Rip Van Winkle," by Washington Irving. Rip falls into some sort of time warp and awakes from a good night's sleep twenty years later. Rip has aged 20 years in what seemed to be a night. Everything in his community has changed and he is astounded by the difference between what he knows and the world he finds. Which brings us to me, Rip Van David if you will. The business world I left is not the same business world I have re-entered only ten years later.

In some ways the new dysfunctional elements developed while I was away stand out in very stark contrast. Some things are very easy to spot. I don't know how to deal with them yet, but I see both new and old dysfunction very clearly. I also see some progress, some issues seem to be less disabling. To those around me things are just ordinary. They may complain, but people have always complained. To me, some of the complaints are new.

What most worries me is stumbling over something I don't recognize as a problem. But I am older and a bit wiser. I am forging alliances quickly with people in positions to warn me about problems new to me. Some are domain specific. Some are related to changes in how businesses run. Velocity seems to have increased. I'm starting to read more widely than just Scrumology. I know I'm going to fall down at some point, but I've also learned much more about getting up again. I have become much, much harder to kill politically. Kill me? So what, I'll go sail my boat. In case you wondered, I'm having a blast. This is absolutely as much fun as where I left off. I was determined to settle for no less.

Wednesday, November 10, 2010

Elephant Scrum

What are we doing when we put “Agile” ideas into practice? Let's limit the discussion to a subset of “work.” With Agile, we are employing limited human resources in ways that produce the most useful, valuable, new thing. We are taking advantage of one particular set of instinctive human behaviors for solving mutual problems. Whether this set of behaviors is more biologically or more culturally based is irrelevant. There are some patterns of interaction within small groups of people that are extremely effective. I speculate that such patterns of behavior repeatedly and reliably produce optimal results because they have been advantageous to the survival of our species. They work because they have been refined over millions of years. Our existence is testimony to their utility. Your narrative may differ.

The modern place where people assemble to work is organized by habit and custom. As proof of the existence of these customs I submit that admittedly dysfunctional working conditions and methods are much the same in many independent organizations. These organizational patterns developed for many reasons other than to create the best products. At worst they result in a group of people appearing to have a common purpose but spending most of their energy doing something else. Often that is fighting each other: Competing for limited rewards. Dominating and resisting. Passive and aggressive. Shifting alliances. Lying and betrayal. Illusion and misdirection. Smoke and mirrors.

For my purposes, “Agile” is about doing what really works to solve business problems based on fundamental small team dynamics. The team becomes an organism much more effective than all of it's members operating in parallel. The team can become “hyper-productive” with perfectly ordinary individuals. If you have never experienced hyper-productivity nothing I write will re-create the experience in your imagination. I ask that you suspend disbelief and resistance and ride with me for a while. Work does not get any better than hyper-productivity. Been there, done that, want to do it again. Want to teach you how to do it without me. Having done that before, having former associates create their own, I can say it's very satisfying.

Hyper-productive teams can be quite fragile if they are not knit together by kinship, religious, political, sporting or similar external ties. This is why we see them so seldom in modern life. Perhaps that is why we like observing team sports. Good teamwork beats all-stars. Clearly the dysfunctional behavior outlined above is utterly poisonous within a team. Good teams can be structured around a leader, but the best teams are collaborative and require no day-to-day leadership. This is partially because really effective leadership is harder to learn than collaborative teamwork. The most effective leader virtually disappears. The easiest way to disappear is never show up in the first place. In collaborative teams, everyone leads, everyone follows.

Work teams are rewarded for fulfilling someone else's vision. If the vision originates within the team, then it is not work, at least not the kind of work most of us do for our livelihood. Scrum is one approach to providing the structure and safeguards for hyper-productive teams to work fairly reliably on vision originating elsewhere. Since every team and every vision is different, Scrum is structured empirically. As the team works within the Scrum framework, they adapt their process (how they work together) to best fit their circumstances. The team periodically adapts it's work direction to best fit their customer's evolving vision. A role is established, Product Owner, to represent and focus the customer's vision. Another role is established, ScrumMaster, to keep the process on track, to be responsible for all the people stuff, and to keep the team thinking hard about what they are doing. The ScrumMaster role does not require being expert in solving these problems. It requires noticing “impediments” to hyper-productivity and mobilizing resources to remove them.

Scrum establishes a minimal framework necessary to protect the team from internal or external dysfunctional behavior. There are certainly other effective Agile frameworks. Scrum is simply what I know best. Nothing is included in Scrum that is unnecessary. Scrum is one complete idea. You cannot pick and choose the Scrum practices you are willing to do upfront. If you never get to hyper-productivity please do not ask me why. Are you actually doing Scrum or something equally complete and effective? Did you cobble something together and call it Agile? How are success, knowledge and courage coupled in your head?

Scrum as described within the past fifteen years is mostly about software development. Because Scrum is really about hyper-productive small teams in the workplace, it is much more widely applicable. Because it is empirical, Scrum will find a way to be useful implementing vision in more places than we can currently imagine.

You could successfully hunt elephant with a Scrum team using handmade tools the team creates, and that is not the least bit coincidental. If men hunted this way, you can bet the vision was from their mothers and wives.

Saturday, November 6, 2010

Tobias Mayer

What a wild year for Tobias Mayer. Perhaps most are, but this is the year I came to know and appreciate Tobias. I sought out Tobias for my CSM training because my closest Scrum contact, Scott Dunn, did his training with Tobias. Lucky for me given my then state of unemployment, I was able to complete Tobias' signature Welfare CSM training in early February 2010. Since that time I have been close enough to Tobias' orbit to keep my special Tobias-tan. I saw him last at the Phoenix Scrum Gathering in October. I am just getting used to working within Conscires Agile Practices, the creation of Bachan Anand, another being in the Tobias Orbit. Bachan is executing on a vision that may be at least as outlandishly idealistic as Tobias'. I'm not certain because my comparison scale is being pushed well past my previous work and life experience. Gaining a new lease on youthful hope at my age is disconcerting.

There are times I thought Tobias' idealism pushed him a little over the edge compared to my version of common sense. Generally I was correct in this, and I benefited immensely by his example. Tobias is a moving beacon, one fixed point of principle against a shifting landscape of co-option and compromise. At their best, idealists are like this. Tobias must have "feet of clay" somewhere. It makes me just a little nervous I haven't spotted them in any area that really matters professionally. You may bring me the hemlock when Tobias sells out.

I don't really understand how either Tobias or Bachan believe what they apparently do, but I consider myself extremely fortunate to have an opportunity to execute a small part of their vision in the work I am just starting. Without them and the mentoring of Lyssa Adkins, I might not dare believe I could succeed in my own, more limited vision. I am going to extend my personal experience of collaborative, cross-technology, high performance humanistic work to the organisational level. I'm not nearly as idealistic, but I have a career's worth of relevant experience and only the Reaper is going to stop me. Since Welfare SCM 018, I have spent nine months training, reading, and adjusting my attitude. I am ready.

I have no idea where the entire package of issues regarding the Scrum Alliance, certification and the like will go. I would simply observe that we can now communicate and organise independently and we will. I'd like to see the SA funnel it's cash horde in more ambitious, idealistic directions, but it really does not matter. When some nexus of ideas creates positive business results directly from more humane, collaborative work environments, a stinking million here or there isn't going to make much difference.

I wrote a letter of recommendation for Tobias mid-April, 2010. With him backing away from the CST certification, this is what I thought of his skills in my training. This is piling on, really, as there must be as much praise and criticism of Tobias published as anyone needs. So I'm actually reproducing this for my pleasure as I thought it was a good letter. Ah, honesty.

Training: WelfareCSM-018, February 4-5, 2010.

To whom it may concern:

I highly recommend Tobias Mayer's CST work based on my experience as his student. The sessions were lively, interactive learning experiences for me and for every other participant I talked to. Tobias organized and conducted the entire class with sticky notes and a taskboard plus a number of flip chart illustrations he drew as required. Tobias clearly came from a place of intimate understanding rather than a slide deck.

Tobias intensely engaged in getting us to view potential workplace activity from a Scrum mind-set. We spent much time in games and exercises. The benefits of these exercises were not immediately clear to many in the class. Virtually all came to realize the exercises helped us instantiate productive collaboration. We experienced the power of jointly solving a shared problem.

Tobias presented Scrum as a set of ideas and behavior that apply well beyond software development. I was familiar with basic Scrum based on a close study of the readings. (Incidentally, he didn't leave anything out.) Tobias challenged me to think through how Scrum might apply in other contexts. That took work on my part, but it deepened my understanding beyond elements, artifacts and ceremonies. Tobias Mayer made me think Scrum rather than simply remember what it looks like."