Thursday, March 15, 2012

Reinventing The Wheel

Who asked for a new wheel anyway?

Possibly the greatest expression of inefficiency and wasting of time in any process is the re-invention of the wheel.  The wheel I am referring to in this case being any tool, template, form, process, database, log, etc that a project team routinely requires to get the job done or track and execute task completion.  Time and time again I see fancy new wheels spinning along the project execution cycle, certain that the existing wheel would have achieved the same thing with less time, effort and confusion.  And how then, if it proves 'road-worthy', will this new wheel find it's rightful place amongst the tools available to all other PM's?  This failure to seek out and use best practices and tools is to the ultimate detriment of a project, the project team, and future project efforts.

Not that new ideas should not be welcomed or encouraged - in fact new ideas are vital to progress and efficiency, and are a basic element of a CAPA type system every PM organization should have set up (corrective and preventative actions).  But starting from scratch is rarely less effort than the few steps it takes to source the latest platform and customize it within reason towards your new vision of things.  It is worth noting that virtually all project teams are made up of functional resources moving from project to project within a similar environment.  When similar, recognizable tools are shared between projects there is a less steep learning curve at the task beginning, or in the event of inevitable team member turnover.

Except for a highly regulated environment or very narrow range of application (such as a pre-flight checklist or nuclear waste containment protocol, perhaps..?), templates and tools are made to be a guide which can then be modified and customized to fit current needs.  Templates typically represent a tried and true standard for execution, having all of the bugs already worked out.  If, however, a template in practice shows inefficiency, error, etc, that is what feedback loops and Lessons Learned meetings are for (see post elsewhere in this blog), along with a system to flag the latest established version.  So, your shiny new wheel could be the best thing to happen in your industry, but if it is not systematically shared and fed back into the 'wheel pool', future teams cannot benefit.  Likewise, fail to use a perceived 'old wheel', and you may be missing out on a past team's hard-earned knowledge.

Besides the missed lessons or potential misalignment between team members and other project teams, an extension of this reinvention problem occurs where you risk invalidating your output or procedure due to the deviation from an accepted norm or industry standard.  Take the case of pooled project data or downstream application of a project output where an upstream team reinvented a variable capture, timing or definition.  When multiple project output is later pooled and the variables do not match, what additional problems have then been created that a standardized approach would have prevented?

Is there ever any reason To reinvent the wheel?  Of course!  If the old wheel contributes to known problems or proves to be dated and unreliable, throw it away.  When cultural, regulatory or economic shifts portend the birth of a new reality, it's time to take a fresh perspective.  If the new tasks are so unique that the old wheel does not conform sufficiently, establish a new one and make it available for current and future project teams to use.  It should be noted, however, that few projects conducted in the same basic environment are truly significantly different from recent ongoing project activities.  And if, finally, through sharing of Lessons Learned, the shortcomings of a particular wheel are shown to outweigh its value.

Best practices are not always The best practices but should at least serve as a starting point for project and functional leaders, and at times may be the de facto requirement whether perfect or not.  The key is in obtaining consensus from past and future end-users, alignment with standards, implement a Lessons Learned or feedback loop, and have a process for updating and centrally locating all tools, templates, etc (essentially best practices) where they are known to all and easily accessible.


Tuesday, February 7, 2012

Scope Change vs Scope Creep (Part 1)

Change is inevitable and not necessarily bad, but problematic when it creeps

The subject of scope creep is one about which most project team members know and talk, yet few seem to be able to define exactly what it is or acknowledge what to do about it - or when.  Change is a natural occurrence and change will happen to virtually every project of long enough duration and detailed enough scope.  Most project-savvy organizations have a change-control process with proper identification, approval, documentation outcomes to address change and all resulting implications.  Scope creep is more than just change; it may linger undetected until too late, and involve processes which may or may not be adequately covered by your change-control process. 

Scope Creep is essentially OOS (out of scope) work, but the 'creep' part adds several additional elements to typical scope change.  'Creep' tends to accumulate slowly and sometimes without the knowledge of the PM, team or stakeholders.  'Creep' has many sources, but it also comes from what you as PM allow and do not allow (knowingly or unknowingly).  It can manifest itself in several ways from first not properly identifying what is in scope, and allowing OOS work to proceed, or by snowballing from one or two passing allowances into items of bigger and bigger cost, schedule or resource implications.  "We allowed this and this, why not that?"  Scope creep, unfortunately, can also result from a "lost in translation" effect when the requesting party and the performing party each make divergent assumptions on some defined element of scope.  You know..., 'ass - u - me'.

Change is somewhat conscious although it can be planned or unplanned.  Creep is virtually always unplanned, sometimes unconscious and is often happening or has occurred by the time you realize it has happened, and are forced into mitigation (stop it, allow it, take the hit or re-negotiate the SOW, budget, timeline, etc).

Staying on top of scope creep begins first and foremost with an adequately defined and approved scope in the form of a written SOW, linked to budget, time and resources - you cannot identify what's OOS or creeping if you don't know the agreed starting point.  This is followed a close second by acknowledging clearly and in advance with stakeholders what is (and in some cases is Not) in the agreed scope and what scope change control process is in place.

One critical technique to effectively managing scope creep is through adequate and frequent communication.  Many requestors of scope change do not know that what they are requesting is potentially scope creep, and/or may not have the proper authority to make the change request.  Ensure you have a method to flag this while the request is being made and before agreeing to or proceeding with the action (relying on the standardized change control process you established at the start of the project).  Many organizations will also have a processes in place to prevent work without prior written agreement, so keep an adequate allowance for delays associated with this too.

Monday, February 6, 2012

Scope Change vs Scope Creep (Part 2)

Expect it and plan for it and your project won't be adversely affected by it

Another method to help differentiate real change from scope creep is to track project changes with a log; all changes, big or small, creep or not, actionable or not.  Flag each according to a scale meaningful for your project environment; the critical part is to identify what the consequences could be, which to act upon, how and when. 

Project sponsors and stakeholders don't want to be 'nickled and dimed', and project managers are not effective by repeatedly going 'back to the well'.  If a small, simple request can be accommodated with a few keystrokes or an extra print-out, I sometimes choose to avoid the drip-drip of change requests and just do it.  Keep the project goal in mind and aim for satisfaction, but beware the slippery slope of agreeing to too much, too often.  It can sometimes help to bundle a few smaller OOS change requests into one change order.  The change log can also serve as leverage in moving more quickly to authorizing a big scope change in light of the several smaller changes requested earlier wthout revising the original scope.  Remember to take the time to explain the 'triple constraint' between cost, time and quality - at least one of these three major project elements is going to have to give for whatever change in scope is ultimately approved.

Talk about the process in advance with project sponsor/stakeholders so it does not come as a surprise.  Every undocumented or OOS request is not necessarily creep.  Change is not necessarily a bad thing either, although it is almost always associated with risk and consequence.  In the end, the sponsor and stakeholders should be delivered the deliverables they want - your job isn't to talk them into or out of deliverables, but to provide all necessary information (ie, constraints) to allow them to make the best decision possible.  As a project is executed you naturally know more than you did when it was originally defined (look up 'cone of uncertainty').  But creep will lead to mistrust and dissatisfaction or blown budget/timeline if not handled properly.

PRACTICAL EXAMPLE: A Form of 'Hidden' Scope Creep
It should be noted that scope creep may not be 'new' or 'added' work, but a result of miscommunication, misunderstanding and/or lack of specificity.  Consider a not-unusual situation when part way through execution a sponsor/customer/stakeholder was under the impression that the budget and schedule they approved for "Activity Y" included sub-tasks 88-100.  The minimum industry standard is, lets say, 1-87 and 88-100 are perhaps desirable but beyond whatever industry regulatory hurdle that exists. 
Upon re-checking, the signed project agreement states something like 'Activity Y will be performed to meet industry standard'.  While this can be considered reasonably specific, it could also be sufficiently ambiguous to lead the service-provider to believe 88-100 are not included and the customer to believe that they are.  The customer feels these should be obvious and assumed that they were included; all the project PM can reply is that the intended SOW is what was budgeted, unless they want to initiate a change order.

Although the service-provider has a contractual justification to continue to exclude the added project scope, the customer is not happy doing without or paying more and maybe waiting longer.  Either way represents a blow to trust and to satisfaction.  Now we can't anticipate every assumption, and a certain level of detail will start to become counter-productive - but like many elements of project management, it starts at the beginning and with lessons learned, best practices, proper scope definition, a scope change control plan, and frequent communication.

Saturday, December 17, 2011

Getting Into The Game

tips for new PM's

I believe there may be hundreds of great tips for new project managers which could be rotated into a short list of 'top tips' for a given project size, complexity, industry, timeline, etc.  To begin with, it really helps if you already enjoy structure and process and organization; and are able to retain the importance of small building blocks while maintaining focus on the big picture.  If you struggle communicating with people in different functional roles at varying levels, if you get frustrated with change or in influencing those responsible for implementing it, the road will not be an easy one.  Most procedural elements of project management can be taught or learned, but not all; the right approach and attitude are two less tangible qualities which will make a big difference to success.

Knowledge of the industry and/or subject matter help greatly for both context and credibility, as does a basic appreciation for corporate politics and human psychology.  Accreditation is a foot in the door, but does not directly determine quality or success.  But for a new PM about to be illuminated by the spotlight of team and stakeholder scrutiny, I'd offer these five tips (un-ordered and un-weighted):

  • understand exactly who all the primary players are and their respective influence on the project, from stakeholders to sponsors to regulatory bodies to functional leads.
  • seek out and apply lessons learned, best practices, templates, tools, etc (reinventing the wheel is one of the biggest time-wasters and cause of preventable errors and delays).
  • collaborate in planning, then mind the critical path;  identify for yourself and your project what I refer to as a touchstone you can look to in times of uncertainty - a big-picture goal, or guiding principal or philosophy that immediately lights the way to your answer.
  • trust functional leads to know their deliverables, and be the supporter and enabler they need to meet schedule, quality and budget expectations;  empower rather than becoming the project police.
  • don't sweat it.  change will happen and satisfaction will wain and trust will be tested but these are more common than you might have expected and are rarely personal reflections (oh, but don't screw up....)

But keep in mind the following corollaries:
- logic alone rarely wins an argument;
- when given an estimate, multiply by 2 and add 5;
- change will happen while you're changing the changes from the latest change;
- satisfaction is typically a U-curve (don't make it an L-curve);
- patience is a virtue;
- time does, it seems, speed up as a deadline approaches (a corollary to Pareto Principal that 80% of the results come from 20% of the effort);
- the path of least resistance is the one always chosen whether it leads to the planned result or not;
- agreement does not necessarily result in compliance;
- the key resource you were promised will be promised to the next important project;
- your 'dedicated' resources are likely allocated outside your project as well;
- praise often goes to the team when a project is successful;
- blame often goes to the PM when off track or unsuccessful.

Friday, November 11, 2011

A Shout-out To The Bleachers

Who's cheering for you?

I'm choosing to start by raising a topic less quantifiable in the carefully tracked and measured world of the Project Manager.  I recently came across an effective way to conceptualize what truly motivates people, and why we think the way we think and do the things we do.  A condensed interpretation of an MCN article by Mark Barnes follows.

Essentially each of us has a cheering section in our heads, passing judgement on everything we do (a kind of Freudian 'super ego').  It is made up of influential people in our lives from birth to current events; typically mother, father, siblings, teachers, friends, mentors and heros, but also bullies, old bosses, your arch enemy and other 'frienemies'.  Further, they all manifest your own distorted impression of themselves and the world, comprised of how you believe that they would respond.  The folks occupying these bleachers witness your every thought and action and respond according to your perception of their point of view, with cheers or jeers.  When you screw up, they're there to remind you; another Nelson Muntz "ha-ha!" to add to the humiliation.  When you perform well, they go wild - who doesn't want to hear that?  The thing is - you Care what they think, despite all other external cues.

This internal rabble is by far more influential than any external audience could ever be.  We've all witnessed someone exhibiting (so you perceive) bizarre behavior or annoying those around with loud music, cell phone conversation, careless driving, etc.  While bothering you, their external audience, they are receiving positive, reassuring validation from the audience in their head.  There are as many different cheering sections as there are people (heads) on earth, and each marches to his/her own - it is because you can rarely accommodate the unique make-up of someone else's team bench that people have differences and disagreements.  Even logical and/or carefully presented arguments can be abruptly over-ruled or dismissed by your internal American Idol Panel.

This is also why when a risk-taker approaches a cliff, his/her cheering section applauds while that of the risk-averse boo and disapprove (leading to inevitable actions).  One typically revels in the approval and thumbs their nose at detractors, then acts accordingly.

Communication and motivation skills are cornerstones of effective project management/leadership.  The work environment dictates acceptable operating norms to which most adhere in order to get along, keep their job, acquiesce to corporate standards, etc.  When working with project team members who seem to consistently think and react differently from you, keep in mind the silent presence of voices shouting from their bleachers.  Cut them a little slack.  Pause long enough to consider what might be motivating them beyond the mixed priorities and pressures of the day, and continue to seek acceptable compromise - one that allows them (and you) to appease those within.  You know when you screw up or fall short of your expectations - it is your internal audience that just passed judgment and now demands restitution.  And when you achieve greatness, take a well deserved bow (in your head) to the only real audience that matters.