January 2009

Upcoming Events

With the annual hiatus in public seminars and events over the holidays, it seems like forever since I've been away from the office, even though it's really only been a month since the IQPC PMO Summit in Coconut Grove. Now that the end-of-the-year festivities and the PMO survey webcast are behind us, it's time to hit the road again.

Here are the confirmed upcoming events that I will be at, in case you are in the area and interested in attending. We have some other stuff in the works, including a few local events, but this gets us through Q1. I know, it's all wildly self-serving and normally this kind of stuff would just be twiddled on Facenet, but, dude -- I'm just not hip to all the groovy new social networking options (it seems like only yesterday that I was spray painting this stuff on the side of abandoned buildings and underpasses).

Here's the rundown:

PMI Central Virginia Chapter Meeting; January 26th at 6:30 PM in Richmond. I will be presenting "Principles of Integrated Portfolio Management" at this open-to-the-public event, which is also being promoted by the Greater Richmond Technology Council. See the chapter calendar on their website for more information.

CampIT Project and Portfolio Management Conference; Chicago, February 5th, at the Stephens Convention Center. This one-day event is targeted at senior managers and CIOs interested in furthering their IT PPM initiatives. It's just outside of O'Hare and cost-effective, at only $219 for a full day of presentations. I am the opening act, with several other speakers as well as an expert panel on the agenda.

2009 Rocky Mountain Project Management Symposium; Denver, March 12-13th, at the Colorado Convention Center. The PMO Specific Interest Group will be hosting the PMO track on Thursday at this large and well-organized regional symposium, featuring yours truly, Jim Furfari of Colorado Springs Utilities, David Sides of ESI, and Art Drake of AIG and the Executive chair of the PMOSIG, who will be moderating a panel discussion. Oh, some guy named Steve Forbes will also be speaking at this event; yeah, me and Steve, we're tight, hitting the speaking circuit together and all. See registration information on their event site and click on the PMO track for more info. Might as well get in some spring skiing while you're there.

Other Stuff…

I was recently interviewed by Ron Powell, the co-founder and editorial director of the B-Eye Network, which covers the world of business intelligence. It is a run down of Planview and how our products intersect with BI, and is now available on B-EyeNetwork.com.

It looks like the PMO 2.0 Survey is already generating some buzz in the industry; I did an interview with Katie O'Connor of Projects@Work about the survey results after the webcast last week. They have posted several articles from us in the past and are planning to feature the survey report in their new PPM Executive newsletter. More to follow on that one as it develops.

Elizabeth Harrin, author and goddess of the popular PM4Girls blog, has also picked up the survey on her own site, as well as at PMtips.net. I need to add her to my blogroll. Speaking of which, did you notice there are new links added? Thanks to the folks upstairs and behind the curtains that help me out with such things.

Are We There Yet? The Elusive Nature of Knowledge-Based Work

Whew. Aaaahhh. Ooohhhh.

You know that exquisite feeling of satisfaction you get after a long project is finally successfully finished? I'm taking an oh-so-brief respite to savor just such a moment.

We (finally) released the 2008 PMO 2.0 Survey Report today in conjunction with this morning's webcast. The whole effort started back in August with the survey design, so it is wonderful to stick the proverbial fork in that one. We had several hundred attendees register for the webcast, and I expect quite a few more will avail themselves of the opportunity to access the on-demand version that should be up by Monday. Some webcasts are more fun than others, and this one was pretty OK. Thanks to everyone who joined in! Lots and lots of great questions from attendees that we didn’t have time to get to and must ultimately be addressed, but not today.

OK -- I'm done savoring now. Back to work.

Besides the survey, I've also been writing -- a lot -- lately. Clearly not in the blog, but writing nonetheless. One topic I was working on recently seemed like a great thing to share with you, so let's take a moment to reflect on the winsome peculiarities of knowledge work. You know -- the things most of us do every day to create tangible deliverables out of little more than thin air and mental gymnastics. Fascinating. I touched on this topic about a year ago (see the 2/5/08 posting), but not from the same perspective.

We all know that fission is the process of turning matter into energy. Shouldn't the converse of that be true when we take mental energy and turn it into mass? If that is the case, then wouldn't we get incrementally smaller every time we turned our brain power into a project charter or a report? Duh, never mind -- I just realized the energy is actually conserved -- that's why a report is warm when it comes out of the laser printer. Of course, that means we've made something out of nothing, thus the violating the Theory of Relativity, so we are back around to the essence of knowledge work. Of course, knowledge work has always been around. Plato was a knowledge worker, as was Socrates, Shakespeare, Da Vinci, Confucius, Jesus and Mohammad. Back in those days, everyone else was pretty much farming, forging or fighting -- I remember. But in these modern times, the Knowledge Worker Club is decidedly less selective, so almost everyone has joined up. Trust me, it sure beats roofing.

Here's the thing about knowledge work when it comes to managing it -- it's really hard to develop objective specifications for what the end result is, or estimate how much time and effort it will take to get there. Oh wait, it gets better -- it’s just as difficult to definitively know when that elusive deliverable is actually achieved. In some larger organizations I have heard rumors of people who have actually made an entire career out of creating a single training curriculum.

Physical work is pretty easy to keep track of. Let's see, we have to run 200 feet of small bore piping from the elevated vertical fin hydration unit to subterranean ion converter pump, and it generally takes a day of effort to put in 50 feet. How are we doing? Heck, let’s measure it. Is that a good weld? Heck, let's x-ray it. Are we done yet? Heck, let’s sign it off and grab a beer. No problemo.

Have you ever tried to objectively observe knowledge work in progress? "Hey Sam, how's that thinking going?" "You look pretty wrinkled up and studious there and sure are a clicking a lot -- let's call it 50% complete." Can you really assess progress based on lines of code, page count or meeting duration?

It's the whole quality thing that really muddies the knowledge-based water and creates a dilemma. Besides being an inherent element of measuring progress, it is closely related to knowing when you are done. For example, I have to crank out seemingly endless presentations as a part of my job. No matter how many of these suckers I do, I get to that teeth-gnashing, gut wrenching moment of truth where I have to figure out whether it is "good enough." How is the flow and transition? Too many slides? Topics? Not enough? Do I need to tweak this one or that one a bit more? Should I re-do that graphic? I believe in ITSM terms we are talking about Utility and Fit for Purpose.

Of course, what I think of my product, or for that matter, what any other knowledge worker thinks of theirs, has little to do with the perceived quality of the results. That is left to the usually highly subjective opinions of others. Judgment -- how's that for a word that will extend any bit of knowledge work well beyond the point of reason?!

The way we try to control the duration of knowledge work and establish an inferred level of quality is by applying arbitrary deadlines. "Hrumph -- Johnson, I need that report on the Jones account on my desk by Friday!" Now, Johnson probably knows that Surly Boss probably isn't going to use the Jones report over the weekend, but by definition, the maximum investment in creating that report is now capped at whatever time remains between now and Friday; so is the level of quality. But what if Johnson has to let the Tom, Dick and Harry proposal slide in order to keep up with the Jones account?

A friend of mine and one of our consultants, Dennis McComb, relates a story from his EDS days about a harried staff member who came into his office, laid out all the tasks she had been assigned on his desk, and asked, "Which of these do you not need to be done in a quality manner?"

OK, if you are still reading this, then you are undoubtedly expecting some kind of a big payoff, right? I'll be the last one to say I have all the answers on this one. I struggle with managing my own work, just like everyone else. Sprinkled throughout the blog are snippets that help, but The Answer is not yet apparent, not to me anyway. The intent here is more to remind ourselves that the environment we work in today is a brave new world, where old rules and old expectations do not always apply and the new ones are not yet fully baked.

Essential PMO Staffing, 2008 PMO 2.0 Survey Report and Webcast

PMO 2.0 Survey Report and Webcast Happy New Year to all -- I trust your holidays were delightful and you are ready to confidently face whatever 2009 brings us! In Chinese Zodiac terms, we are coming in to the Year of the Ox, a symbol of hard work and prosperity -- one tends to beget the other, heh? According to Wikipedia, those born under this sign are calm, dependable and modest. Is it an oxymoron that they tend to not yak much? I'm buffaloed by the very thought if it.

(I, on the other hand, am a Monkey. Go figure…)

After much anticipation and work, the 2008 PMO 2.0 Survey Report will be going out to participants before this week is over. For everyone else, we will be holding a Web cast to review the survey results on Thursday, January 15th. The registration link is now up, and those who sign up for this event will receive a copy of the full report following the Web cast. For those who cannot attend the Web cast, we will make the report available for download from our Web site resource center at some point.

Speaking of which, if you are reading this, you are either on email distribution, have your RSS feed set up, or successfully navigated our new Web site to find me! The good news is the new site is really slick and more user friendly with better layout and lots of cool hover points. However, that once-handy link to the blog no longer graces our home page in such an obvious manner. For those of you who haven’t visited it yet, by all means, drop by for a tour. Hover over the Planview Resources tab on the lower half of the home page until my mug shot magically appears and then click on my face; go ahead, I like it -- it tickles.

---

OK, let’s talk about staffing the PMO. Over the holidays, I got to thinking about if I were asked to set up a PMO, what skills would I consider essential, and why. This was spurred by some interesting survey results regarding PMO staff size that we will discuss in the web cast, but suffice to say in the interim that the magic number is "more than 4." Understanding that you have to have a critical mass of staff to meet basic objectives, the question then becomes, "4 what?" How these skills are distributed among the undoubtedly talented, eager and multi-faceted personnel I would put in place is less important than making sure all these capabilities are present. Here goes, in no particular order:

The Analyst -- this is someone who can take work and resource data like a pit bull with a Raggedy Ann doll and shake it until the stuffing flies, and be so happy doing it that they drool. The analyst is adept at separating informational wheat from chaff, or finding signs of intelligent life within the white noise of deep space. The analyst lives for trend spotting, yet does not see ghosts among the shadows. The analyst is the PMO canary in the coal mine; a veritable organizational NORAD.

The Marketer -- a huge trick for the PMO is to effectively influence without authority; this requires the ability to sell concepts, information and processes to a wary and fickle buyer. The marketer can put together a campaign around an improvement initiative so slick and inviting that they could sell ShamWows to Bedouins. Do not underrate this skill -- at our user groups, the biggest crowds are in sessions where customers relate how they sell their programs to the organization with inventive and catchy approaches.

The Accountant -- follow the money; every PMO needs someone who can deftly turn labor, time and other elements into dollars and sense. Everyone wants to know, "What does it really cost?" The accountant is as comfortable with a business plan as a ledger, and knows his way around a schedule and charge back program for services equally well.

The Report Guru -- data cannot hide from the prying queries of the guru. Regardless of the system, disparate information can be swiftly and accurately plucked from tables and presented so that it is readily digestible by executives, or meaty enough to fill the hungry working manager. Far from simply being a DB geek, the report guru inherently understands the business and what end users are going to need -- before they even know they need it. This person is either the alter ego of analyst or they eat lunch together. T5H, are you out there…

The Teacher -- a big part of the PMO is to educate, which is not an trivial task left to rank amateurs when it comes to dealing with reluctant (and often ADD) adult learners. Able to leap tall curriculums with a single bound, the teacher is competent and confident on a variety of subjects. Whether in a formal class or one-on-one mentoring session, the teacher is able to grab and hold your attention with a silky smooth demeanor and a mean half-nelson.

The Predator -- like a high flying drone and armed to the teeth, the predator quietly glides above the portfolio, scanning the landscape for evidence of issues and problems. The predator has years of experience as a salty project manager, so his (her) infra-red eye and all-weather BS detector cannot be fooled by misdirection or the cheap camouflage that is so often draped over an initiative in trouble. Chances are the predator knows a project is under duress even before the project manager does. Like a laser-guided missile, remedial action is decisive and surgical, all in the interest of keeping the peace. The predator relies upon the intelligence gathered by the guru, accountant and analyst.

The Evangelist -- drop to your knees, lift your hands, and accept the truth! The evangelist has inspired visions and is able to relate them to the masses. A persuasive orator, the evangelist can illuminate the transgressions of an organization like a flash of lightening, all the while making a compelling case for redemption to executives as well as general staff. It's not just hype either; the evangelist is likely a reformed sinner and can quote most common methodologies and standards chapter and verse. The evangelist has a proven track record of both conversion and building a tight knit, cult-like community of followers, with the help of the marketer and the teacher.

The Builder -- enthusiasm and information has to be backed up with workable solutions; the builder is the mechanic of the PMO, able to disassemble and rebuild processes, configure supporting applications and generally make sure things work. The builder can troubleshoot workflows, write documentation, develop templates and generally lube up the organizational chassis wherever it is binding.

The Judge -- when fiefdoms fracture, silos split or factions are frustrated, the judge brings order and calm by applying wisdom and offering sensible alternatives to the sticky issues of the day and getting everyone back on the same track. The judge speaks softly but a Louisville Slugger leans against the bench. In chambers, he or she is respected as an advisor and mentor.

The General -- for such a rich set of capabilities to be orchestrated to play in sweet harmony, someone has to write the score. The general clearly understands the objective and is able to plot strategy, while keeping the politicians informed and away from danger. As the fearless leader, this person also knows the importance of building strong allies across the organization. Not one to hunker in the bunker, the general is always near the front lines directing the battle but stays out of the trenches.

OK, there you have the ten qualities I feel are necessary for PMO success as my dream team of essential staffing. Any skills that you want to add? Offer up your own cast of characters via the comment link.