Monday, March 29, 2010

The Art of War Chapter 1 - Entry 6 - "The Plan is useless..."

At the end of the first chapter of the Art of War, Sun Tzu gives direction that may make the strongest case for project management in the entire text.

"Those who triumph,
Compute at their headquarters
A great number of factors prior to a challenge"*

He goes on to explain that those who spend less time planning do not succeed. According to Sun Tzu, more planning = greater success, less = greater chance of failure and no planning at all pretty much guarantees you have no shot.

The first chapter of the Art of War ends with Sun Tzu claiming that by observing the time spent in "computation" he can determine whether or not one will succeed in their efforts.

From a PM's standpoint, this has relevance on a number of levels. The most obvious application would be to the idea of actually planning out a project, and if you follow the rest of the lessons of the Art of War, this is going to end up bringing in many of the elements included in a traditional project plan. Things like risk planning and developing a communication strategy are critical aspects of Sun Tzu’s formula for success.

One application that might not be so obvious is how this planning can play out on a smaller scale. Something as simple as a business meeting, offers a great opportunity to prove out some of Sun Tzu's claims. If you've ever been in a meeting where you arrived not knowing what was going to happen, or what you were going to say ahead of time, you are probably already all too familiar with the formula for defeat that is mentioned above.  For my own part, this is a lesson that took a long time to learn, but over time I have learned that if I make the time for "computation" before a meeting, things go much better. In terms of preparation, working out things like how the Five Measures fit within the context of the meeting, thinking through what will take place based on who is likely to be present, what objectives or motivators they might have, who might say what, how the others in the room will respond, and especially, how to raise the issues I need addressed as well as how to respond to the questions I'm likely to be asked, seems simple but it is unfortunately something most people don’t take the time to do. It may sound like a lot of work, but my experience has been that once you get into a habit of doing it, this tends to come fairly easily. Whatever your goals in the meeting, even if it is just to get through it with your job intact, putting in the time to prepare before hand is just basic risk management. It will give you the freedom to devote the time and attention necessary to cover the things you were not able to think of before hand.

If success in the meeting equals getting your issues addressed without losing credibility, taking the time necessary to be prepared to participate with confidence and ease is just basic risk management, the same as you’d do on any project. And as for the others around the table, as Sun Tzu says, examining they prepare will give you a lot of insight into their ability to succeed or fail once things get underway.

While it can be fairly simple to see how this applies to Project Management, it has a lot of relevance to an Agile approach as well. If taking an Agile approach is intended to offer the freedom to handle constant change while incrementally working towards a desired goal, The Art of War in right in step. The basics of things like forming the team, having the team determine how they will best work together, what the vision statement is, etc. are all part of the “computation” Sun Tzu is talking about. These practices have even greater application later on in the Art of War. In a later section of the book Sun Tzu talks about the need to be fluid and adaptable, in order to do this successfully, someone leading an Agile project, or an Agile team, still needs to take the time to understand the basic concerns mentioned in this chapter.

The bottom line is, success is determined by your ability to make the time to learn about what you are facing and considering what will happen when things get underway.

Or, as President Eisenhower put it, "The plan is useless; it's the planning that's important."

* Quote taken from "The Art of Strategy" by R.L. Wing

Friday, March 26, 2010

Project Potion 8 - The Fonzi - Isaac - Radar - Mr T Report


Wednesday, March 24, 2010

Are you tired of filling out those boring old Red Amber Green reports?


Introducing THE FIRM REPORT!









Last week I was talking with a co-worker about the status report we have to file each week. It’s called a RAG Report. He asks why it is called a RAG Report. I explained to him that RAG stands for Red-Amber-Green and we spent some time discussing the various merits (or not) of completing that type of report. The intent is clear – show red, amber or green to quickly convey a message about the state of the project, but in practice, the sad thing is that the simple color system easily lends itself to a situation in which an executive will simply look at the color and ignore the rest of the detail that has been painstakingly crafted and tuned by the highly developed creative spin tactics of the project manager (or lead).

So, that conversation got me to thinking that maybe a RAG format had outlived its useful(less)ness. Being the hard working, creative mastermind that I am, I started trying to work out a new alternative to the Red-Amber-Green… and now I am proud to give you…

(drumroll please)

THE FIRM REPORT!

The FIRM report embraces a new model for rating project health:

F = Fonzi
I = Isaac (your bartender)
R = Radar O’Reilly
M = Mr. T

Here is how this works:

If you get a Fonzi, that means “AHHHHHHEEEY”  -  things are very, very coolamundo!

If you get an Isaac (portrayed here with his classic “Double Issac” hand gesture), this means things seem to be more or less okay, but it would probably be a good idea to head down to the Lido deck and start having at the Mai Tais (yes that is the plural… I looked it up) post haste.

If you get a Radar you should be remembering all those times in the TV classic M*A*S*H (ATTN Gen Y… TV Land is your friend) when Radar (IMHO, the greatest PM ever portrayed in film or TV) cocks his head ever so slightly, and says “CHOPPERS!” This usually happens about 20 seconds before anyone else hears them. In other words, there is some seriously bad stuff in the air, some of which is bound to be missing a few limbs, and they are headed your way Sport!

Finally, we get to Mr. T… as in “I PITY THE FOOL!” which means… Dude, you are simply screwed, and no amount of gold around your neck is going to save you from the fact that someone is going to be taking you sweet, sweet iconic 1980's van away very soon.

More on this in the next episode of Project Potion… and I’ll be posting a status template for you to test your job stability with very soon. 

Stay tuned!
The Mike Sutton Sessions - Part 4 - Startup Diary

Two weeks ago I had the pleasure of co-teaching a CSM class with Mike in Malaysia. In part 4 of the interview we shot he talks more about the work he is doing there and his startup diary, which can be found here.

Saturday, February 27, 2010

Project Potion Special Interview with Thushara Wijewardena

Working With an Agile Offshore Team

Project Potion #6 - Dave Goes to Macworld

Where the ProjectShrink intervews the drunkenpm about his visit to Macworld and his efforts at setting up a PM Mac User Meetup


Thursday, February 25, 2010

The Mike Sutton Sessions - Part 3 - ScrumFest

Part 3 of the drunkenpm interview with Mike Sutton, CEO of Wizewerx and founder of ScrumFest.

In this part of the interview, Mike talks about his work putting on ScrumFest in the UK and his plans to hold additional events elsewhere.

Tuesday, February 23, 2010

Art of War Chapter 1 - Entry 5 - The Tao of Paradox

The next section of Chapter 1 starts by introducing one of the core strategies of Sun Tzu's teaching. In "The Art of Strategy" by R.L. Wing, the section is translated as:


Heed me by Calculating the advantages

reinforce them by directing outwardly.


This has a very direct relationship to the strategic work a PM does in that it calls upon the practitioner to measure and understand their true position and then "reinforce" (read as spin or manipulate) the perception of that position by how you represent it.


As he moves into the next section, Sun Tzu provides more clarity into how the perceived reality can be manipulated:


Thus, when able, they appear unable.

When employed, they appear useless.

When close, they appear distant

When distant, they appear close.



They lure through advantages,

And take control through confusion.



In the R.L. Wing translation, this is referred to as the "Tao of Paradox". The instruction is to create a perceived reality that is not necessarily accurate in order to gain advantage. This is "playing dead" or manipulating how we project ourselves and our situation in order to gain the upper hand. There are obvious implications in the context of an armed struggle, but think about it in the setting of a meeting at work, when you pretend to know less than you do in order to either gain more information, or learn more about another's understanding of a situation. Even down to basic interviewing tactics where you lead an interviewee towards an answer you hope to get by pretending you have a problem you have not been able to solve.


This tends to be one of the areas of the text where "nicer" people often get stuck. They perceive this as dishonest or misleading and, rightly so, if they consider themselves to be honest folk, it is something they would not purposely strive for. But beyond a physical conflict context, this is something which all of us do in our daily lives from childhood, often without even being conscious of it. As children we learn to get what we want by creating a sense of urgency that will draw the response we are looking for from our caregivers. While not many PMs would willingly admit to lying to create a false impression, how many would be able to say that they had never added a little spin to a status report to create a more positive impression, or led their team to believe that failure to meet a deadline meant certain doom for their employment, in order to drive the team to getting the work done on time.


As Sun Tzu says, "everyone uses the art of war". The Tao of Paradox is no exception. The question is, is it better or "more honest" to use it absent mindedly, or to understand it as a normal behavior without judging it and learn to be more aware of when and how you make use of this approach so that you can wield it with greater skill and a greater sense of responsibility.



When complete, they appear to prepare.

When forceful, they appear evasive.



As this paradox is created, what happens to the "opponent" is that they spend time gathering knowledge, interpreting and planning a response. This creates a window of advantage where, if you have followed the five measures and already have your approach planned, you can seize the moment.


They attack when the opponent is unprepared

And appear when least expected.



This is the Strategist's way of triumph.

It must not be discussed beforehand.



As someone managing a project, or a team, you need to be vigilant for those moments when you can achieve the little wins that build trust and drive the efforts toward delivery. The word "attack" is used above, but it does not have to be a negative attack. You can just as easily attack a lack of faith in the project or a negative perception of the team. As leaders, we are often able to have a greater impact when we bring order to the chaos around us if people have already decided that we are caught up in the chaos that has taken hold of them. When done well, this spin can make things look like you have saved the day with relative ease. It can be a double-edged sword, however, because when done poorly, you end up as one of those PMs who create a crisis just to solve it. The idea is not to create drama in the space around you, but take advantage of what is already there to engineer an impression of the situation, and your role in it, that will allow you to gain the position you desire.



Quotes in this entry from 

Tuesday, February 09, 2010

The Mike Sutton Sessions - Part 2 - Improvisation

Part 2 of the drunkenpm interview with Mike Sutton, CEO of Wizewerx and founder of ScrumFest.

In this part of the interview Mike talks about how studying Improvisation techniques have influenced his work building and leading Agile teams.

Friday, February 05, 2010



----------------------------------------------------------------------------------
The Art of War - Chapter 1 - Part 4
Having defined that which is to be measured, Sun Tzu provides examples of things to be considered when examining the five measures. He recommends determining which leader has captured the cultural mindset:

"Which leader
 Has the Way?"

And, which has the poitical and organizational advantage:

"Which side has
 Heaven and Earth?"

Who has the strength and rigorous enough approach to discipline to follow the processes they have defined as their path to success.

"On which side
Is discipline
More effective?"

"Which army
Is the stronger?"

According to Sun Tzu, understanding these will help you "know" victory and defeat. This is an important point to spend some time on. The idea is not that if you study these things, you'll win; but that if you study these things, you will be able to foresee who will win... which leads to a principle introduced later that is (simplified) never take on a battle you have not already won.

Following this thought, if you stick with Sun Tzu, follow his rules, he promises to lead you to victory. If you follow his guidelines, the Art of War will get your back and keep you from harm. However, this is going to include knowing when to back down, when to back away and when to take action in a way that is decisively final. In the workplace, my experience has been that the last part if often more difficult for people to adopt than the backing down. (But there will be much more on this later.)

Sun Tzu also goes on to explain that if you don't adhere to these rules, whether you use the Art of War or not, you've already ensured you will fail. This is another critical point in the Art of War. What Sun Tzu has essentially done is stated that if you stick with him 100%, he'll guarantee success, anything less than that, and you are not using the Art of War and you will fail.

For those familiar with Scrum, this would be "The Art of War, but..." and it has about the same chances of success as "Scrum, but..." (more on Scrum, but)

This level of commitment is something that appears a number of times throughout the book. It can seem a bit severe when put into practice, but it is something that (IMHO) truly differentiates practitioners of the AOW from those who merely dabble in it. Because war is such nasty business, once you have committed to it, Sun Tzu demands total commitment. At times, this means backing down and at times it can mean pushing further than you might normally. Even taking the time to determine, for yourselves, where the line is in terms of what you are willing to do in order to help the project succeed, can be helpful. As Sun Tzu says, we must know our opposition and ourselves. Often, trick for us as PMs, is to make sure there is a difference between the two.

Quotes listed in this entry are taken from John Minford's Penguin Books Great Ideas translation "Sun Tzu The Art of War (Strike with Chaos)" published by Penguin books in 2006. The passage covered in this entry can be found on pages 3 and 4 of the book.