Dec 07 2008
The Tao of Scrum: A short essay to Product Owners
Our way of thinking is not linear, yet we put a lot of effort trying to work, write and plan in a linear fashion. Off course this leads us to dead ends and difficult situations. I’ve seen and experienced this myself.
One of the meanings of “being agile” is that you are prone to see things in a diferente perspective. One that embraces changes, last minute ideas and that you not only embrace a non-linear way of think, but you try hard to enforce it. Even though we realize it, changing our behaviour pattern is not that easy. Here are a few hints of how I have been able to overcome it.

Teamwork: many people really do think better
As the P.O. for Brasigo (www.brasigo.com.br) I have a team working *with* me not *for* me. That might seam obvious, but in fact is a great insight. Think about it for a minute: as a species humans are not the strongest, fastest or have the best senses and yet, we dominate the planet. That is so because our greatest strenght is to be good working in teams. It makes sense to enforce teamwork. When you work in teams you’re naturally allowing non-linear thinking to happen. This leads to the next point.
Allow non-linear thinking, embrace it, enforce it
Linear thinking, in most cases, is anti-natural. Why do companies spend so much energy enforcing linear thinking, throught papers, forms and a whole bunch of processes? Almost always people loose focus on the product and start working to follow pre-determined processes that have been implemented by someone else. If they screw up, whose fault is it? Working in teams means everyone has a stake for the sucess or the failure. I am not saying that there should be no process. I am saying you sholud have as little process as possible. Workng in teams will naturally enforce non-linear thinking. It’s almost like a constant brainstorming state. There is a sutile, but important difference between being in state of mind that allows you to have ideas all the time and being in a state of mind in which you enforce your team to be crazy, lazy or out of focus. Crazy won’t get you far.

Discipline and commitment
Those are important factors to achieve high performance. It is quite common that people in your team mislead this into some sort of unwanted behavior. Often if people are not mature enough they will loose focus in the name of “wild thinker” sindrome. And they are in this state it is sometimes kinda hard to bring them back to reality. So there has to be a pace, aimed at creating a “locomotive effect” imprinted by the PO. As a PO you should be contagious.
Translate thoughts in written language
This is hard. One great discovery of Jaques Lacan was that our subconscious operates over language. So what he did was: he used that together with Freud’s findings to create his own psicanalysis. When you can anouce, say in a phrase, the problem, you will be able to solve it. In business, you have to translete your ideas (your team’s ideas) into written stories. And it has to be done in a way that anyone upon reading them, will be able to understand. If you take a hundred pages to do it you are not doing a good job for the sake that no one will read it, thus people will pretend to understand it and you will never get what you want implemented the way you thought. Here are handful of artifacts to help you:
- Mind maps (try Freemind and Xmind)
- Work Breakdown Structure
- Drawings
- Post its (and alikes)
- QFD charts
Mind Maps are a great visualize what has to be done, but there are some caveats: they are not so easy to spot the SEQUENCE you will do things. Things I like to answer via a Mind Map: What is this all about? For whom is it made? When? Where?
A Work Break Down Structure, or WBS is a very simple artifact that can be derived from you Mind Maps. It helps you to visualize how things will be done and begin to wonder in which order.
Drawings are always nice. Get a sheet of paper, and start drawing your diagrams, ballgrams on it. Do that alone AND with your team. Writeable walls are nice, but they get erased, paper you can keep and refine your thoughts. Drawings are a good resource for deciding what will be done, generally done after your mindmaps.
Post-Its can be used in many ways: TO DO lists, as Kamban and keeping you personal passwords (NOT!). Let give one example on how I like to use them. Gather your team in a room and start a collective mindmap about every possible way something can be failled. After a while, you will notice that some categs/patterns will emerge. Write down on the wall those categs and start placing Post-its of everything in the current pipeline. Voilá, now your entire team can see where you’re week or strong. Hints for using Post its: use diferent colors and sizes to diferenctiate things. Use red for critical things.
QFD (Quality Function Deployment) is a japanese technique that allow you to understand “WHATs x HOWs”. It is very useful artifact since it allows you, in a simple way, to decide based on a spreadsheet that measures what you want to do versus how you will do it. QFD is an entire world itself, so it will fit best within a post for itself (and I promisse one post only about it soon).

Last, but not least: bear in mind that you should always adapt.
There is no right formula that will work everywhere, or even all the time. As a PO you should know what to use in whcich situation. As a rule of thomb I like to decide what will be used based on ROI. I ask myself if the time invested in some task will pay out. Why spend 4 hours putting together a diagram when I can simply draw it, take a picture an attach to the stories I writting? Maybe the story needs the diagram, so it pays off.
Maybe you’re working for an Advertising Agency, so things are a little different, you can always adapt. Whenever adapting have in mind one thing: you’re adapting the form, not the principle.
As Darwing would state: Adapt or die!



