Ten Years of Deliberate Practice

Want to hone your craft? Commit to it for ten years of deliberate practice. ...

... "Reinforcing that no-free-lunch finding is vast evidence that even the most accomplished people need around ten years of hard work before becoming world-class, a pattern so well established researchers call it the ten-year rule. " ...

Via Micro Persuasion on Developing Expertise: Practice brings success

Service is a Science, Study and Improve It

Interesting move in the global landscape ... Singapore collaborates with IBM through a network of universities and industry partners to innovate in service management. Education in the science of services is planned. ...

... "The collaboration aims to develop a new breed of service scientists and service entrepreneurs who understand service systems, are trained to enable efficient and systematic approaches to service delivery, and serve as catalysts for service innovation in organisations and for various industry sectors. " ...

Via IBM: Service Science Initiative in Singapore

Business Games Teach Project Best Practices

Nothing creates understanding like a good game. Here's a novel approach to disseminating best practice process in project and service management. ...

... "Both simulations are high impact, interactive business games, developed to address the process and cultural challenges of implementing IT Project Management and Service Management best practice. This unique approach to business learning brings Project Management and Service Management best practice to life in the context of realistic and exhilarating scenarios. Participants quickly experience breakthrough understanding of best practice processes and methodologies resulting in improved individual, team and business performance. " ...

Via G2G3: Turkish delight

Free Learning: No More Excuses

The cost of a college education is astronomical and rising in the United States. Yet, that shouldn't prevent anyone from a self-led education, which they can do totally free, thanks to the Massachusetts Institute of Technology (MIT).

MIT's OpenCourseWare (OCW) is a revolution in education, much like the Open Source software movement. Through OCW, anyone in the world can undergo a full college curriculum, including video lectures, labs, assignments, study materials, projects, and more---online and free.

Want your staff to take some courses, but don't have the training budget to send them anywhere? Want to study a new discipline on your train ride to and from work? Do you wake up in the middle of the night with sudden aspirations to be a dentist? The training content is all here and free.

About the only restriction is that you cannot use the material commercially (for instance, you can't use it as part of your own commercial training services), which makes sense. However you can adopt and distribute the material, provided you cite the source and use a Creative Commons or similar free-use license. Also, these courses are not for college credit, and no degrees are offered.

And, while there is no faculty-student interaction, all the content is available for self-learners and educators to use. Many of the courses come with free video lectures.

According to the web site, MIT OCW's goals are to:

• Provide free, searchable access to MIT's course materials for educators, students, and self-learners around the world.
• Extend the reach and impact of MIT OCW and the "opencourseware" concept.

Visit the site below and welcome to the world of free education...

MIT OpenCourseWare MIT OpenCourseWare

Challenge IT Talent Poaching With Development Strategy

The battle for IT talent rages and is particularly acute in Asia. Consider exciting training programs, career path tracks, and other soft incentives, such as telecommuting to provide some work-life balance. The enterprise that masters talent development is sure to succeed in the future and have fun doing it. ...

... "To provide a continuous supply of IT staff and retain existing IT talent, the company started to establish various initiatives on staff development. " ...

Via MIS: The Asia IT Talent Challenge

Project Management Costs

Getting started with your PMO ... training is key to jump-starting the organization. ...

... "For an IT project, approximately 5 percent to 15 percent of the budget should be dedicated to PM functions required to carry it out. " ...

Low Cost

Team Kickoffs: Breaking the Ice

Whether conducting a project kickoff, a seminar, or a training session, it's always fun to start with an ice breaker. It doesn't have to be anything fancy. I've seen ice breakers that were nothing more than a funny video, but served to loosen things up (nowadays that's pretty easy with YouTube, such as this one we posted on PMThink).

I've also seen ice breakers that served to get people moving around and networking, such as having each person use pictures (and no words) on a piece of folded flip chart paper to describe themselves, and then having people pair off for a minute at a time and interpret each other's pictures.

If you're looking for ideas, here's a nice list to help get you started. I think my favorite link is the last one.

Ice Breakers

Chief Innovation Officer: Get Trained

Attend training on the Chief Innovation Officer role. The Chief Innovation Officer course is targeted to push the frontiers of the field and brings into focus fostering innovation talent, creating portfolio techniques, and enabling business processes necessary to execute innovation projects in support of growth. ...

... "BMG's Chief Innovation Officer seminar is designed specifically for business leaders who are leading the charge for innovation inside their organizations. This 2-day interactive seminar features emerging strategies, tools and techniques from some of the foremost thinkers in innovation today.

Upcoming Seminar Date: 4/30/2007 2 days Denver, CO " ...

Chief Innovation Officer Seminar

Project Management Training: Foundation For Success

With federal IT investment slated to increase, info technology professionals in government would be well-served by training in a foundation of project management basics. ...

... "officials interviewed for the study said their teams lacked or may lack sufficient training to effectively estimate costs, identify risks and develop baselines from which to plan project costs, schedules and technical requirements. " ...

Via Federal Times: Link

Control vs. Accountability: Are We Our Own Worst Enemy?

In our never-ending struggle to gain more control over the chaos in our organizations, and with more and more focus on change management, who would think of going in the opposite direction and allowing more freedom?

Let's take a look at a story with some surprising results (sent courtesy of my old friend, Larry Beane).

Thanks to a project initiated by the European Union, seven sities and regions in Europe have completely done away with traffic signs. The originators of this idea must have been on to something. Contrary to the normal expectation that this would result in pandemonium, the accident rate went down!

Now arguably, this may or may not work in a congested city, but it got me thinking about the need for accountability. Perhaps the more rules we inflict, what we're really doing is relieving people of accountability---the paradox being that we need to give people freedom to make them fully accountable. Otherwise, we claim ownership of the problem instead of delegating it.

This is not unlike Toyota's policy of trusting their work teams to solve problems independently, and trusting that if their solutions are wrong, they'll work to correct it and learn from the experience. This is what a learning organization is all about.

This isn't to say we should just abandon all change management processes. On the contrary, providing people with effective processes can lead to successful outcomes. But for each rule we devise, we should consider an alternate approach of holding people accountable for outcomes, and insuring they have the capacity to succeed. Yes, provide processes, training, principles, guidelines, etc. But then focus on outcomes and accountability. And allow for learning-based corrections.

It's a radical thought, but a little anarchy may just bring the control that we need.

Here's the article about the successes of traffic anarchy...

Controlled Chaos: European Cities Do Away with Traffic Signs - International - SPIEGEL ONLINE - News

Microsoft enters the project certification arena

This press release from Microsoft, timed shortly before the PMI Global Congress, announces a certification programme for users of Microsoft Project 2007. The new version of Project Server is due to be released in the New Year and aims to integrate further with other organisation systems and processes. Offering a standard for training does seem like a good idea. It will be interesting to see how the new certification from Microsoft, which has a reputation for setting its own standards, aligns with the PMBOK.
The announcement says the "training and certification product lines ... were developed after consulting the A Guide to the Project Management Body of Knowledge ...".Microsoft Advances Its Project Management Technology and the Project Management Profession

CRM Project: Old Hat?

Interesting article explores current evolution of CRM projects, which have been bolstered by on-demand-software, integrated view of the customer, efficient training delivery options, and referenceable value benchmarks. ...

... "As far as business cases go, start early and establish your baseline before you start seeing a return from the tightening-up of the business processes in preparation of the application installation. " ...

Via TechLinks: Hal Harz on The State of CRM ...

Leadership Seminar: Announcing The Leadership Quadrant

For project managers looking to expand their horizons in the leadership arena, I'd like to invite PMThink readers attend an exciting two-day workshop at The National Constitution Center in Philadelphia, PA on November 15th and 16th, 2006.

The seminar, which I'm co-facilitating with Jerome Jewell of Jewell Consulting Group, is titled: The Leadership Quadrant: 4 Ps for Organizational Excellence. We're offering a $100 discount to select groups, and PMThink readers certainly qualify (plus group rates are available for parties of 3 or more).

In case you're wondering what the 4 Ps are, they are: Principles, People, Productivity, and Process. In the seminar, we'll explore topics such as Napoleon's Six Winning Principles, Systemic Thinking, Emotional Intelligence, Setting Better Priorities, Asking Better Questions, and more.

Best of all, we're incorporating Freedom Rising, the museum's acclaimed multimedia presentation, into the workshop. For details and a seminar brochure, visit the Marengo Group training web page.

Business IT Projects: ERP Implementations ...

Article summarizes key elements of successful ERP projects: committment, speed, scope management, empowerment, phased implementation with quick wins, data cleansing and standards, education and training. ...

... "So it is now perfectly possible to turn what might well once have been an unrewarding slog (likely to end in failure) into a structured project with manageable milestones and relatively quick wins for the business along the way. " ...

Via SciTech Today: Toward Better ERP Implementations

ITIL Certification Training Support

EXIN and BCS confirm their committment to the certification and training of ITIL for IT service professionals. ...

... "We will continue to guarantee the quality of training institutes providing ITIL courses for the ITIL Foundation, Practitioner and Service Manager Certification. Current applications for accreditation are valid, and we encourage new training provider prospects to become accredited. BCS-ISEB and EXIN and other stakeholders, will aim at a continued cooperation with accredited training providers in order to maintain the high quality of the ITIL certification standard. " ...

Via EXIN INTL: Statement BCS-ISEB and EXIN following recent announcements by OGC on ITIL ...

Einstein Project Management Tip #4: Think Value

And so we continue our series on project management tips from Albert Einstein. Here's another...

"Strive not to be a success, but rather to be of value."

This sums up perfectly the problem with most projects today. They focus on "success" without fully defining what success means. Project managers and PMOs track schedule and budget metrics. Then, at the end of the project, some capture customer satisfaction, almost as an afterthought.

What really needs to happen is to insure value to the customer, and this usually goes way beyond being on time and on budget. We spoke about the need for clear goals. Surely that's part of it. We also need to deliver in small, frequent iterations to provide the quickest value and get more immediate customer feedback.

Customer satisfaction should be measured and tagged as an index throughout the life of a project, just as Earned Value uses indices to track cost and schedule performance. This allows course correction to be made in areas such as goal clarification, communication, and other areas needed to provide good value.

And when the product has been delivered, be sure that the customer can maximize the benefits of the product through proper training, tips & techniques, next steps, or any other items that will help them get the value expected.

These are the very items I've attempted to address with my Service-Oriented Project Management (SOPM) framework, with its four phases of Understand, Prepare, Iterate, and Transform (UP-IT).

More Einstein tips coming soon...

Is the Role of the Project Manager in Jeopardy? - An Editorial

A few weeks ago, I posted a blog about the new Program Management credential from PMI. In it, I referenced PMI's definition of a program manager vs. project manager in their FAQ page.

A project manager, according to PMI, has the following responsibilities (I've put some of the key points that jumped out at me in bold):

• Perform their duties under general supervision and are responsible for all aspects of the project for the life of the project
• Lead and direct cross-functional teams to deliver projects within the constraints of schedule, budget and resources
• Demonstrate sufficient knowledge and experience to appropriately apply a methodology to projects that have reasonably well-defined project requirements and deliverables.

A program manager, according to PMI, has the following responsibilities (again, I've bolded the key points):

Under minimal supervision, program managers are responsible and accountable for the coordinated management of multiple related projects directed toward strategic business and other organizational objectives. These programs contain complex activities that may span functions, organizations, geographic regions, and cultures. Program managers build credibility, establish rapport, and maintain communication with stakeholders at multiple levels, including those external to the organization.

Clearly, a program manager must be closely tied to the strategic goals and benefits, monitor the program accordingly, and have a strong connection to senior management. And I also feel that the new credential seems on the surface to set the bar appropriately high.

But I can't help but feel that, in contrast, the PMP credential is losing steam. First, there are myriad organizations virtually guaranteeing an "instant-PMP" after a crash course and some tweaking of one's background experience (although PMI is now doing audits of work experience).

Second, a project manager must, in many cases, go beyond the PMP/tactical focus and possess the same traits and skills that PMI has designated as requirements of a program manager, especially in the case of an enterprise and/or global project, such as a business transformation effort. I realize PMI's role definitions are a way to differentiate and justify the new certification and I suppose one could organize their effort into a "program" to qualify for that certtification, but in these changing times (and with greater challenges for project managers), I think PMI needs to evaluate and revamp the PMP certification as well.

When I do presentations on principle-based leadership training, I have a slide where I present what I call "The PM Challenge." I present it as a boxing match. In one corner, we have a project manager, armed with MS/Project and the PMBOK, but lacking:

• Business Acumen
• Leadership Skills
• Conflict Management Skills
• Negotiation Skills
• Presentation Skills
• Communication Skills
• Strategic Intuition

In the other corner, we have the "challenger," represented by "the project," with the following characteristics:

• Global, virtual team
• Complex technology
• Complex change
• Multiple vendors
• Offshore resources
• Conflicting Stakeholders
• Scrutinizing Executives

Such a project manager, without the appropriate leadership and soft skills, doesn't stand a chance. Wouldn't a person with the skills PMI describes as a "program manager" be more apt to have success?

In the latest PM Network magazine from PMI, there are not one, but TWO articles that illustrate this point. One is titled "Project Management 2.0: Project Management is at a Crossroads," by Peter Fretty. The other is titled "No Limits," by Marcia Jedd, and talks about what project managers must do to crash through the glass ceiling and elevate it from the tactical trenches.

Perhaps a start would be to take a new view of project management beyond just "executing to a set of requirements to deliver on-time and on-budget." The current tactical focus might explain the consistent failure rates of projects. One problem is that PMI has traditionally "followed common good practices in the field," which of course is what a standard is supposed to do. The problem is that common practices have brought common results, which aren't all that good. Time for an upheaval. Perhaps they need a section, apart from the "standard" itself, for "new frontiers in project management," which could outline those who are breaking the mold with good results.

I'd be interested in others' thoughts on this topic. Who knows---It just might help drive requirements for the next version of the PMBOK and/or PMP credential.

Project Success Story: Veterans Heath Administration

When Ken Kizer took on the challenge of revamping the horrific state of affars that was the U.S. Veterans Health Administration (many of you have probably seen the movies that showed the sorry state of Veterans Hospitals), nobody suspected that they would go from "last to first."

Forget "Good to Great," these hospitals literally went from "worst to best!"

Reading the writeup on it in this week's issue of Business Week, I was struck by the similarities between Kizer's approach and Napoleon (whom most of you know I'm quite familiar with).

Whereas Napooleon was focused on equality, Kizer was driven by quality and safety. Like Napoleon, Kizer inherited a disastrous state of chaos and provided order, visibility, improvements in technology, training, accountability, decentralized decision-making, and most of all, hope and pride. Also like Napoleon, Kizer had his share of enemies, some who felt he was too arrogant and others who perhaps felt threatened by the changes. Finally, like Napoleon, Kizer was eventually ousted, except by Congress instead of foreign powers.

Fortunately, unlike Napoleon, Kizer's successors continued his methods and his passion. Because of these changes, every nurse and doctor in the network has instant access to electronic patient records, and drugs are filled robotically, avoiding the mistakes common to most other hospitals. And because these hospitals treat the patients for life, they spend more time and money on preventative care, as they realize it costs everyone less in the long run (talk about Total Cost of Ownership!).

I highly recommend picking up this week's Business Week (the July 17th issue with "The Plot to Hijack Your Computer" on the cover). Meanwhile, below is another article that talks about the amazing transformation that Kizer led the VHA through.

Expect to hear more on this as I research this in more depth. I also ordered the book, Straight from the CEO: The World's Top Business Leaders Reveal Ideas That Every Manager Can Use, which is mentioned in the article and apparently covers Kizer's story.

Here's the article (not the Business Week one, but a good one nonetheless) ...

"The Best Care Anywhere" by Phillip Longman

Project Measurement Framework ...

Article explores the transformation experience of AGEdwards where the project management success rate was improved, through leadership training, a measurement framework, and enhanced organizational models. ...

... "Ed Pilewski, now VP of IT productivity and quality, chose not to take the traditional route of forcing a rigid project management methodology on the technology staff - a tactic that can backfire and create resistance to change. Instead, he implemented a standard framework for measuring, monitoring and reporting on a project's progress that fosters transparency and accountability. " ...

Project Measurement Framework: Via CIO: When Failure Is not an Option

Globalization of Research and Development: EMC China Center ...

EMC Corporation will open its first China-based research and development facility next month, which is a a state-of-the-art software development center in Shanghai. It will play a strong role in the localization of EMC products for Asian markets. This center is a component of EMC's five-year China investment strategy. ...

... "The new center is part of EMC's global research and development investment, which is expected to be more than $1.2 billion in 2006. In China, EMC has established a comprehensive China Solutions Center network, deepened its relationships with key Chinese customers, created partnerships with software and systems integration solution providers, opened training centers to certify networked storage specialists, and made significant contributions to the academic community in China. " ...

Globalization of Research and Development: EMC China Center: Via EMC: EMC to Open Software Development Center in China

Silence of the Project Managers

Have your stakeholders stopped screaming, Clarese?


As reported in Computerworld, a study by a Utah-based training firm found that the biggest cause of project failure is the inability of project managers to effectively confront management and key stakeholders on five major sensitive areas.

Here's an excerpt:

According to David Maxfield, director of research at Vital Smarts, the five
situations include the following:

• Setting arbitrary deadlines and inadequate resources that "set up a project to fail."
• Failing to provide the necessary leadership, political clout or energy for a project.
• Skirting or manipulating the project priority-setting process.
• An unwillingness by team members to support projects as required.
• Failing to acknowledge project problems until it's too late for remedial action.

These findings were based on interviews with more than 800 project managers and over 150 hours of observation. The article stresses the importance of standing up to management, which may seem intimidating, but no worse than what'll happen if you don't stand up and the project fails.

This one's well worth reading, folks. Speaking up early is a key lesson that can avoid many problems later. Here's the article...

Want to kill a project? Keep quiet about problems, study finds

PMO Process Primer

Last month, I mentioned a four-part series on Projects@Work about establishing PMOs. The first installment was on defining the role of your PMO up front.

Not sure what took so long for the second installment, but it's finally here and worth the wait (maybe it's a monthly series). This installment talks about the types of processes your PMO might undertake, and offers some food for thought with each process area. According to the article, a PMO might consider:

Project Processes (including demand management, approval, portfolio management, project/application lifecycle, and risk mitigation)

Analysis Processes (including business analysis, business case development, and process redesign)

Planning Processes (including planning and tracking, and capital planning and budgeting)

Administration Processes (including methodology management, training, tool development/ownership, and knowledge management)

To date, this series is an excellent primer on PMO startups. It's insightful and obviously written by someone who has had some varied experience in PMO implementation. I'm looking forward to the remaining two parts and will be sure to post the links here.

Kudos to the author, Ted Stephens, an associate principal at Intellilink.

http://www.projectsatwork.com/content/Articles/231627.cfm

PMO Success Story: A.G. Edwards Case Study

There's an excellent article in CIO Magazine this month showing how A.G. Edwards reinvented its PMO to bring their projects to an 88% success rate (from about 50% originally).

Some key lessons:

• They created a 25-step project management high-level framework of just the high level activities common to all projects. They didn't inflict a detailed application development methodology and left the "how" flexible, as long as the "what" was satisfied. At a more detailed level, they used Primavera for project tracking and dashboard metrics.
  
• They provided leadership training to boost the confidence of their PMs
  
• They moved the project managers from the PMO to the functional areas to encourage collaboration and better align the PMs with the business.
  
• They offered project planning services to assist the distributed project managers with using the new framework effectively (allowing them to use the planning tool of their choice, be it Excel, MS/Word, or a whiteboard). The 25 framework touchpoints, however, are common to all projects for cross-project comparison purposes (I assume enabled in Primavera).
  
• They redefined "success" as "projects that deliver business value." This gives customer satisfaction and business value even greater priority than being on-time and on-budget (note: they still improved their schedule and budget statistics anyway).
  
  This is the essence of the new model and bears repeating. The customer defines success. Under this model, it's quite possible to have a project that is late and over-budget and seen as a raving sucess.
  
• They tirelessly met with stakeholders in individual and group settings to offer the benefits and ask for their support. They used a subtle soft-sell approach with the "bad actors."
  
• They first involved the PMs receptive to new ideas as part of a pilot and them used them to "spread the gospel"
  
• They measured success rates and publicized them in quarterly reports to senior management.

These are all powerful and valid ways to make a PMO successful, and are philosophically aligned with the Service Oriented-Project Management (SOPM) model I've been developing. In this case, these changes collectively served to boost IT's credibility at A.G Edwards significantly.

Here's the full article. Don't miss the sidebar "8 Steps for Improving Project Management."

When Failure Is Not an Option - Editorial - CIO

PPM Software Evaluation Tool; Don't Get Stuck Without It

Yesterday, I posted a link to an excellent article on a software selection process. Now Projects@Work has just announced their PPM Software Evaluation Tool, a downloadable tool that offers "a comprehensive set of questions and parameters for organizations to consider when selecting a project portfolio management solution."

Here's an excerpt from the accompanying article (which is valuable in itself) ...

Don’t settle for presentations and proposals. Regardless of how you proceed through the procurement process, make sure to get your hands on the solution before you make a decision... An ideal, but time-and cost-intensive approach is to pilot the software on one or a subset of live projects before you commit to a full-scale implementation. While this last option will require you to invest in training and a limited installation of the software, if the solution turns out to be the wrong one you have minimized the cost of a failed implementation.

This is sage advice, as many of these tools look great in a demo---or even a brief conference room pilot---but until you experience how easy or difficult it is to actually configure the tools, you don't really know what you're getting yourself into.

As the saying goes, "Fail fast, fail cheap."

Link

Innovation Ideas for Project Managers

Looking to increase innovative thinking when developing solutions for your project's customers?

I discovered an interesting organization called SolutionPeople. For one, they offer something called AcceleratedInnovation Training, which focuses on using advanced innovation techniques to get to the bottom of "real goals, challenges or problems."

But the real find is an offsite innovation facility in Chicago called The Thinkubator, which, in addition to the expected multi-media equipment, boasts such unusual thought-boosters as Karaoke machines, a rooftop sundeck, disco lighting, unique giant chair sculptures, and my personal favorite..... get this.... restroom themes inspired by Albert Einstein and John Travolta.

Yes, for those who do their best thinking in the bathroom, you too can be ------ wait a minute---- Albert Einstein and JohnTravolta??? I'm trying to get a vision in my head of this. Frizzy hair and a white suit comes to mind.

In all seriousness, there's something to be said for creating an environment that fosters creative thinking. Here's a writeup in Training Magazine on what Thinkubator founder and president Gerald Haman calls "the four Ps of innovative environments (in PDF format).

Hey, maybe they should start a franchise. Apparently they already have a few Thinkubator locations and created "innovation centers" for companies such as Capital One and Lucent. Maybe a specialty facility for project managers is in order. PMThinkubator, anyone?

Join the Project Management Revolution; The SOPM Model Takes Shape

OK, I've been fleshing out the Service-Oriented Project Management (SOPM)™ model, and have come up with a more memorable and catchy representation of the four steps, although the actual content is pretty much the same.

The acronym for the four phases is UP-IT (which can symbolize "upping" the level of customer service, saying "up yours" to old ways of doing things, or "upping" the success rates of IT projects---in which case the "it" stands for "IT").

Ready??? Drum roll please......

The four phases are:

• Understand
• Prepare
• Iterate
• Transform

Here's a revision of my previous post on the topic...

1) UNDERSTAND ... Develop an understanding of the problem being addressed, the goals, constraints, the internal environment, the external market, benchmarks, the people and subject matter involved, potential solutions, risks, benefits/justification, and any other knowledge necessary for success. Most of all, understand the customer and what they need to be successful.

2) PREPARE ... After helping the customer obtain approvals if needed, prepare the project organization (resources, roles & responsibilities), operating principles, the infrastructure and tools needed to run the project, organizational alignment, preliminary training needed, communication, and anything else needed for a smooth road ahead.

3) ITERATE... Using the axiom, "Think bold, implement safely," plan, design, build, test and pilot the solution before attempting a full scale implementation. Encourage innovation. Implement in phases to achieve quick wins, earlier benefits, and greater customer satisfaction. Consider iterative prototypes during the design phase. Don't forget additional training needed.

4) TRANSFORM... After each project phase and at the end of the project, evaluate and document lessons learned, customer satisfaction, and benefits achieved (vs expected) for the purpose of transforming yourself and the customer for the better. This includes guiding the customer to help them achieve maximum results with the product or service delivered, and laying the groundwork for their continued success.

Now that I have the framework locked in, I'll complete the model around these four phases. I am absolutely convinced that this model can help increase customer satisfaction and the general success rates of projects.

SOPM; A New Project Management Methodology

Service Oriented Project Management (SOPM) is taking shape as a methodology that fills the gaps in traditional project management, namely a RELENTLESS customer focus and the all-important analysis and benefits evaluation after the project has "completed."

As I fine tune the model, I'll post the iterations here, as a methodology in progress.

The four high-level steps in SOPM are as follows:

1) UNDERSTAND ... Develop an understanding of the problem being addressed, the goals, constraints, the internal environment, the external market, benchmarks, the people and subject matter involved, potential solutions, risks, benefits/justification, and any other knowledge necessary for success. Most of all, understand the customer.

2) ENABLE ... After helping the customer obtain approvals, prepare the project organization (resources, roles & responsibilities), operating principles, the infrastructure and tools needed to run the project, organizational alignment, preliminary training needed, communication, and anything else needed for a smooth road ahead.

3) ITERATE... Plan, design, build, test and pilot the solution before attempting a full scale implementation. Implement in phases to achieve quick wins, earlier benefits, and greater customer satisfaction. Consider iterative prototypes during the design phase. Don't forget additional training needed.

4) EVALUATE... After each project phase and at the end of the project, evaluate and document lessons learned, customer satisfaction, and benefits achieved (vs expected). This includes evaluating how the customer can achieve maximum results with the product of the project, and laying the groundwork for their continued success.

By using an UNDERSTAND, ENABLE, ITERATE, and EVALUATE process, with COMMUNICATE as an overarching activity that extends across all four steps, we adopt a much more holistic and customer-centered approach to project management.

A few key points... Customer satisfaction should be measured at milestones throughout the project, not just at the end. It's as important as monitoring cost and schedule (i.e. Earned Value performance).

Imagine seeing an S-Curve showing Planned Value, Earned Value, Actual Cost, and Customer Satisfaction. Maybe your project is on schedule and on budget, but the customer isn't satisfied with the results (or with the project communication, or a whole host of other issues).

A narrow focus on cost and schedule takes too much of an inward view. Besides, measuring customer satisfaction throughout a project allows for corrective action instead of managing in the rear view mirror.

More to come.

NOTE: I have since revised this model. See my updated entry.

Project Failure Case Study; Maine's Medicaid System

Talk about a project disaster. As reported in an excellent article in CIO Magazine, the Maine Medicaid Claims System project is a case study of a project gone awry.

The project was undertaken to switch from their legacy systems to a new web-based system to process Medicaid claims and facilitate HIPAA compliance (Health Insurance Portability and Accountability Act of 1996). As a result of the failed project, Maine is now the only state in the union not in compliance with HIPAA.

System problems led to many claims ending up in limbo, leading to hundreds of calls from health care practitioners, nearly 300,000 patients being turned away, several dentists and therapists going out of business, and destroying Maine’s finances and credit rating.

So what went wrong?

Mistakes included the following:

• Deciding to develop an entire system from scratch using unproven technology, while other states built a front-end onto their legacy systems
• Caving to pressure from management to meet tight deadlines with inadequate resources instead of pushing for a realistic plan to begin with
• Failing to notice why other bidders either didn’t bid or came in way higher (a sign that the schedule was unrealistic)
• Hiring a vendor with no experience in developing Medicaid claims systems because they were the lowest bidder
• Not having a Medicaid expert on the team, leading to errors in judgment
• Underestimating the time needed to meet with subject matter experts
• Competing with another major initiative (a department merger) for executives’ attention and resources
• Skipping project management basics (including piloting, adequate end-to-end testing, staff and user training, etc.) due to looming deadline pressures
• Failing to stop, regroup, and analyze the risks
• Taking a “big bang” approach to cutover with no contingency or backup should something go wrong

Management’s response, of course, was to switch program managers, and issue stronger demands to have a smooth system, but none of the changes or demands made much of a difference. Consultants were brought in to prioritize the many problems, but still, the complexities proved too much. It wasn’t until a Medicaid expert was brought in that things began to gel.

Like many project failures, it’s easy to point to the project management (and certainly there are many shortcomings there in this case), but the organization must share the blame as well if it insists on unrealistic deadlines and leads by fear (fear of shareholders, fear of competition, fear of management, etc.). None of these variables can make an unrealistic schedule more realistic.

It's really very simple. Either adequate resources must be committed, the expectations lowered, or a more piecemeal approach taken (or all three, if applicable). In any case, the schedule must be realistic and risks need to be managed.

Here's the full article. It's well worth reading, as are the reader comments.

Maine's Medicaid Mistakes - Editorial - CIO

Earned Value Management Trends, Best Practices, and Pitfalls

A few weeks ago, I commented on Part 1 of a three-part series on Earned Value Management on Projects@Work.

While Part 1 set the stage and illustrated some of the challenges of EVM, Part 2 of this excellent series offers some excellent case studies and learnings.

For instance, the US government agency, OPM (Office of Personnel Management) cites the following critical success factors:

- Continuous executive sponsorship (not just up front)
- Committment to funding for adequate tools and training
- Adequate allocation of project managers' time to manage using this system
- Piloting EVM in a small group of projects to illustrate success and fine tune the details
- Not underestimating the culture change management required, involving employees, managers, and timekeepers. Regularly maintained training and job aids are critical.

Another organization, Inter-Coastal Electronics, cites having shallow, simple WBS templates in their ERP system as a key success factor. They claim that a WBS that's too granular becomes too difficult to manage. I couldn't agree more.

I high