Fissure eNewsletter
Fissure Newsletter Volume 10
May 2006


Public Workshops:
Curriculum

Public Registration Please See Scheduled for the following Locations:

  - Chicago, IL
  - Minneapolis, MN
  - Raleigh, NC
  - Sioux Falls, SD
  - Central, IL


Visit the Fissure Website:
www.fissure.com

Dear Fissure Friends, 

I was reading Geof Lory's article on the "Perfection Game" and it got me thinking about perfection and what do we mean by perfection.  At first thought you might say that bowling a "300" game (also known as a "perfect" game) is an example of perfection, but if you scrutinized each of the 12 strikes, I'm sure you could find 1 that was not exactly in the pocket. And what about a hole-in-one in golf? Is that perfection?  It might be for that hole, but that's just one hole out of 18.  

Perfection - according to Webster, "is the state or quality of being or becoming perfect". I'm glad Webster included "becoming", because I would have a tough time identifying anything about me that is perfect (and I'm sure that all who know me would readily agree, especially my family). But I have to admit that at times in my life I have felt perfection if only for an instant or a few moments in time. What I'm referring to is that feeling you get when everything just feels right and you wonder how it could ever feel any better. 

I hope you have all experienced this feeling many times in your life.  Maybe it was when you held a new born child for the first time, or got that first job offer, or first promotion, or hit the perfect golf shot, or tasted that perfect meal.  At that moment in that environment it just feels perfect.  But perfection doesn't stay around for long; the baby cries, you start to worry about meeting your new responsibilities (job, promotion, or baby), and that feeling of perfection leaves.  But I'm OK with that because the fun and the learning are in the journey, and the reward is the satisfaction of a job well done and that beautiful feeling you get when the perfect moment happens. 

Mike Wold has contributed again and this time he shares with us his experience and "learnings" from planning and managing a volunteer team of project managers in painting a house (Paint-A-Thon) once a year.  Mike's shows us that even as "seasoned" project managers, the "soft" things are the most important in keeping a team productive and happy.

As I said earlier, Geof Lory's article is about the "Perfection Game".  It is an interesting and effective process improvement approach you will want to try.  This time Geof tells us how it was used to provide feedback for him.

Our upcoming public workshops are in the left hand panel - our computer simulation based workshops are an effective and fun way to learn AND EARN PDUs.  Make sure you also check out what's happening at Fissure (Fissure News). 
 
This issue contains:

Thanks for reading and have a great quarter,
Jesse Freese

Fissure, President


 





PROJECT PARENTHOOD
Learning and Feedback
by Geof Lory

In this quarter's article I want to share a protocol to create a learning environment and provide structure to the review process. This protocol, called the PerfectionGame*, is extremely effective at creating a positive environment and forward focus for improvement.

I particularly enjoy the PerfectionGame because it directly addresses the four key elements necessary for optimal learning in a team environment. To recap from the previous article, these are:
  1. Create a safe environment for bringing your best to the team
  2. Provide a familiar and shared structure for the feedback
  3. Keep the learning forward focused
  4. Be specific and timely
In addition to setting the stage for optimal learning by creating the above conditions, this protocol has the added value of dramatically increasing the team's overall alignment around their goals and objectives while fostering an environment of creative collaboration. For any team, alignment and collaboration is extremely valuable, however in software development teams, especially teams trying to grow their agile methods, missing these elements is the kiss of death.

To learn the Perfection Game protocol I highly recommend you start by actually playing the PerfectionGame to become familiar with the rules and structure. Once the rules are understood, you and your teammates will then be able to apply the protocol as desired to your everyday interactions for critical feedback and honest, creative and safe input.

Here's how the Perfection Game works.
  1. Players start by sitting in a circle so all can see each other.
  2. Each person in the circle names a task or action that he believes to be simple and that he is willing to perform throughout the game - for example, "Humphrey Bogart imitation," "juggling," or "flipping a coin."
  3. The first player performs their task named in step 2 using the following structure:
    1.  The first player announces  "Okay, I'm starting now." Everything the player does after this point is subject to perfecting.
    2. The player performs his task.
    3. The player says, "I'm done." Everything up to but not including this statement is subject to perfecting. 
  4. The remaining players/observers then provide feedback through the following process.
    1. "On a scale of 1-10 (where 10 is a perfect performance of the task), I rate your performance a ____."
    2. " I give it a ___ because ?.." Here the person providing the feedback states specifically what they liked about the performance that earned it the score they gave instead of a 0. Be especially careful to avoid stating anything that was wrong or what they didn't like about the performance.
    3. "In order for me to give you a 10 you would have to ?." Here the feedback is focused on what would need to be true in their next performance for them to receive a 10 from that feedback provider.

  5. After each observer has provided feedback, steps 3 and 4 are repeated two more times. The player uses the feedback expressed by the various observers to modify each performance.
As a game this can be a lot of fun. I use it in my training at times when teams need some guidance on moving forward through improvement rather than focusing on what isn't working. There is a strong inclination to provide feedback to the performer by stating what was not done well rather than what could have been done. The difference sounds trivial, but using this protocol opens the performer to accepting the feedback with the intention of improving rather than defending their performance.

Now, how do you take this from a game to everyday practice to provide value to teams and their outputs, processes and performances? The key parts of the protocol lie in the deliberate delivery of the three points of feedback in step 4. By integrating these three statements into how team members provide feedback, you will quickly create an environment that is safe and structured, and feedback that is forward focused, specific and timely.

Shortly after introducing this protocol to a project team, I sent out an email to the team documenting the process for initiating and approving change requests and asked for their feedback. Using the newly learned protocol I got a reply from one of the project managers in the following format:
Geof,

I rate your documentation of the change process a 7.

I liked that you were specific about the steps and levels of approval required. I also like the form you provided.

For this document to get a 10 from me I would like to have a graphical flow of the steps and I would like the form moved to the production template library.

Thanks for taking the time to document,


How perfect is that? Not only were his ideas good, I now knew exactly what I needed to do to "perfect" my deliverable. I have used this protocol on anything that is worth incrementally improving through successive iterations. Code reviews, design reviews, UI reviews, training reviews, even meetings. I once stopped a meeting that was going nowhere and we used the protocol on the meeting itself. Once everyone had expressed what would need to be true for the meeting to "get a 10" we got on with it and had a productive meeting.

Use of the PerfectionGame will help eliminate the tendency of pure negation, minimize the interpersonal disturbances in sensitive discussions, emphasize the desirable "results to date" with respect to the object/action being perfected, provide equal, specific creative contributions from all participants, and solicit critical thinking about improving to perfection.

And best of all, it can be used to provide feedback to less than open minded teenage girls when their parents "don't understand." It has been effective in giving feedback to my daughters on how they can do the best possible job of cleaning their rooms. They now know exactly what it takes to get a 10 from me.

Try it; I think you will enjoy it.

*This protocol is part of a larger set of team protocols presented in the book Software for your Head by Jim and Michele McCarthy. Jim and Michele, through their company, TeamWorx,  have worked with software development and management teams for many years. They guide weeklong Team Boot Camps, and the protocols presented in their book are practices and lessons learned from their work with hundreds of such teams.








Lessons from the Paint-A-Thon 
by Mike Wold, PMP

About this time of the year when the ice starts to break up on the Minnesota lakes and optimistic neighbors plant their flower gardens (only to be surprised once again by the May freeze), my thoughts drift back that fateful day eight years ago that had a big impact on my life.

It started out innocently enough. I was a new member of the Minnesota Chapter of the Project Management Institute and had just finished listening to a good speaker at a dinner meeting when the our visionary chapter president cruised over to my table. After exchanging some small talk, he asked me a question that would take me on an eight year journey that has given me many highs and a few lows.

Here is the "hook question" he asked: "Don't you think organizations like PMI should make it a point to find ways to give something back to their communities?" To me this was like asking "Don't you think project managers should create charters for their projects?" Of course I took the bait and said "definitely". Then he asked the 64 dollar question, "If you feel that way, how would you like to give our members a chance to use their talents to give back to the community by leading a Paint-A-Thon project?"

Now Paint-A-Thon is a program wherein teams of 25 - 30 people paint over 150 homes for economically disadvantaged seniors and disabled people for free within the Saint Paul-Minneapolis area every August. I could hear my self say, "Yes, I will do this". As I drove home I remember asking myself, "How did I get into this? This will be a lot of work!" And it was. But what I did not realize at the time was that I would receive much more than I gave both in the good feeling of giving something back to people in need and, to the point of this article, in the project management insights I have received from leading this project for the first few years of the program.

Picture yourself like me that first Paint-A-Thon project standing in front of an aging house early in the early morning next to an expectant family waiting for a painting team of 25 - 30 project manager volunteers from our chapter. Have you ever tried to manage 25 project managers? Well, learning how to manage a team of project managers who are used to leading their own projects turned out to be only one of many lessons I learned on this journey. Let me share some of them with you.

Although I learned a lot of practical lessons on the "technical" aspects of project management, like the value of using good process for project initiation, planning, execution, control and closure; the value of having a good communication plan and the importance of ensuring the resources and materials for the project are in place at the right time, I would like to share some of my learnings on the so called "human side" of the project management experience. Here they are:

  1. Manage by results - I remember the first year I was managing the Paint-A-Thon team, I spent a lot of time identifying the specific tasks that had to be done in order for the house to be prepared and painted. I had assigned certain people to certain parts of the house and was all set to "manage them" in getting a high quality paint job. Well, as you know, nothing seems to go according to plan. First of all, some of the people I expected to be there did not show up or showed up late. Then of course some of them had their own way of doing the painting and were pretty much "unmanageable". What I learned from painful experience is to do the following:

·    Divide up the project into subprojects (e.g., prepare one side of the house, paint the garage, clean up the yard, etc.)

·     Try to get an experienced person (with some people skills) to volunteer to take on each of the subprojects.

·       Let the rest of the people work on any subproject they like

·     Communicate a clear message on what quality looks like on the subproject (e.g., consistent coverage, no paint on sidewalks, etc.)

·    Give them what they need to get the job done (in this case their paint brushes, paint and ladders) and get out of their way!

  1. Lead the project; don't "do" the project - The first year I actually thought I should be doing some painting. This is a temptation of all project managers since it is often easier for us to do the project work than to lead the project. After the 10th person interrupted my painting to ask me a question, I realized that my job was to lead and coordinate the project and to provide any support that anyone needed to get their tasks done. The term "servant leadership" hit me as I found that the most useful things I could do once the painting started was to pour paint, provide water, answer questions, clean paintbrushes, and make sure that the young man doing an "aerial act" near a live electric line was instructed on safe practices.
  2. Honor their gifts - When I first started managing the project I made some assumptions about what people would be good at and what they might like. Of course in the heat of the battle I did not do the one obvious thing - ask them what they felt they were good at and what they liked to do. The whole project goes so much better if you take the time to find out what people's gifts and interests are and then try to match them. This point hit me hard one year when my best "painting detail" person informed me that, although she was a good detail painter, her real passion was gardening. Once I responded to this interest, you would not believe the great yard and gardening additions we have made to the delight of the home owners.
  3. Communicate the mission - After a while I realize that the Paint-A-Thon is not about painting but about the joy and appreciation in the eyes of the home owners. These are people whose days do not usually go very well and getting their house painted for free by a group of upbeat and friendly people makes their day. As the years went on I began to communicate to the team the message of the real mission of the project and it really energized people. Many people serve on the team year after year and tell the stories of the past projects and talk about seeing the joy in the home owners.
  4. Have some fun - We try to focus a lot of energy on making sure that the team has fun during the project. In fact we have a person on the planning team that does very creative recognition things and two people focus entirely on providing food and goodies for the team. Too many project leaders forget that having fun is a basic human need and carries the team through the tough spots along the way.
  5. Recognize them - You might think that people who are willing to give up their time to paint a house for a family in need would not need to be recognized, but I have found that everyone needs and enjoys some sort of recognition. It might be just a personal thank you, an article with their name in it, a picture on the web site, or a thank you note, but I have found out that this is one of the things that have people coming back year after year.
  6. Risk management (just do it!) - I got a real feeling for risk management the first year of the Paint-A-Thon when the weather forecast was changing from partly cloudy to pouring rain up until 7am on the morning of the paint day. As you know painting a house in a pouring rain has a major affect on the quality of the paint job. Our team always identifies its risks, including weather, loss of key people, and now even getting the wrong color paint from the program coordination organization. I learned that having real contingency plans (not just one that looks good on paper) is really critical. For example, that first year people I had only six people who had signed up a week before the event. I had to call in every favor I had ever done to my relatives and close friends to create the "contingency team". Fortunately, people began to sign up and I called off the brigade of relatives and friends.
  7. Celebrate! - Finally, the human spirit is energized by celebration. We focus a lot time on how we are going to celebrate at the end of the project. This is especially true of the planning team where we have had some very creative ways to celebrate - after we have recovered from the work. Many projects simply end without a celebration event. This goes contrary to what seems to be the basic human need for celebration and closure.

I hope that some of the lessons I learned in the Paint-A-Thon ring true to you and remind you that project management is not really about "managing" things but is more about "leading" people in an empowering way. My hope is that can apply some of this today in your project.





 

Fissure News
 
Fissure is going International having recently established a partnership with 3Rock in Tokyo, Japan. 3Rock will be offering Fissure simulation workshops in both English and Japanese.
 
Fissure has also partnered with Management Dialogue in Kuala Lumpur, Malaysia to offer our project management simulation workshops on a public and private basis in Malaysia.
 

Please visit our new partner's websites http://www.3rockconsulting.com/ENG_index.htmand http://www.m-dialogue.com/   (please add Links)

 

Farewell to Kindra Craig who has been faithfully handling fissure's books, she is looking forward to giving her undivided attention to her new son Owen. Owen will one day become a professional golfer if grandpa (Jesse) has anything to say about it!

 

Welcome aboard to Brian Toren who will be taking over the accounting tasks from Kindra and to Donette Gardner who is Fissure's new Program Manager (client contact for onsite training). It's great to have you with us.

 

Energy Level Newsletter System by WebKit.Click to unsubscribe.Click to report abuse