The Lost Art of Project Management
From the The Business Driven PMO Blog
by David Blumhorst (Daptiv)
Stories from the trenches and practical advice on how PMOs can more effectively support, prioritize and fund strategic business initiatives.
Recent Posts
What’s So Bad About Spreadsheets?
Top Five PPM Trends to Watch Out For in 2014
Insights and Trends: Current Project Portfolio Management Adoption Practices
Life after project completion: Is a project complete without benefits realization?
How Important is Adoption for a PMO?
Categories
2012 Takeaways,
Active Projects,
Adoption,
Adoption Practices,
Benefits Realization,
Best Practices,
Business Direction,
Business Process,
Business Value,
BYOD,
Clinger-Cohen,
Continual Improvement,
Daptiv,
Daptiv Connect,
Daptiv PPM,
Decision Board,
Decision Making,
Educause 2012,
Edward Deming,
Events,
Federal Government,
Gamifiication,
Gartner,
Gartner Symposium,
IT Governance,
IT Leaders,
IT Project,
Lean PMO,
Magic Quadrant,
Mobile,
Obama,
optimal schedule,
PMO,
PMO,
PMO Success Webinars,
Portfolio Management,
PPM,
PPM Consulting,
PPM solution,
PPM Tools,
Prioritization,
Project Managers,
Project Management,
Project Manager,
Project Managers,
project managers,
Project Reviews,
Project Staff,
Resource Leveling,
Risk Analysis,
ROI,
SaaS PPM,
Saving Projects,
Scoring Models,
Spreadsheets,
Strategic EPMO,
successful PMO,
Survey,
Team Collaboration,
Teams,
Top Management
Date
As both an IT-PMO Director and CIO, I've had occasion to hire and evaluate quite a number of project managers. During one of those stints a colleague of mine and I decided project managers generally fell into two camps - what we called task managers and project leaders.
The task managers had the "science" of project management down pat. They could put together great task plans, log issues and risks, and produce project status reports. They loved checking off tasks as complete, checking off requirements as done and completing projects on time, on budget, and on scope.
Problem was, they often missed the target. Say we started a project to enable customers to configure their product on the Web. We had one of these that was proceeding apace using the then-current technology. The PM dutifully checked off the tasks, kept the project in scope, and we were well on our way to having working screens and data. But as I looked at the result, it seemed to me to be difficult to use and required a lot of maintenance. One of the Web developers on my staff suggested a new technology that she claimed could be used to get a better result in half the development time - and she was right. I killed the project and we started a new one. I put the developer in charge of the new project (not a formal PM by training), and we ended up with a great interface that was easy to use and easy to maintain and modify.
What was the difference? The technical project manager did not understand the business target. Indeed, he was not trained in Web development and did not know the technologies. But he did know how to "manage" a project. The problem here is a project isn't something to be managed - it as a process that is intended to achieve certain business outcomes. Without achieving those outcomes, the money and time are both wasted.
Project Leaders, on the other hand, have a good sense for business and understand the desired outcome. They then lead and motivate a team to accomplish that outcome. In one of my favorite projects - an ERP implementation - the project manager knew that managing users expectations as we migrated from one major system to another would be a big challenge. She worked with me on the internal political problems that inevitably arose, and made an ally of the biggest internal skeptic. I knew we were ready to go live when I talked to the skeptic and she said "I didn't think we could do this, but you know what? We're ready". If the skeptic says you're ready, you probably are, and we successfully went live that weekend. This project manager was also not shy about changing scope and requirements if needed to make sure the processes we were implementing turned out right in the new tool, and asked for a slight extension and budget increase. We were slightly over budget and time, with numerous scope changes but guess what - we had a successful ERP implementation in a global company. Not a small achievement by any means.
So what do I look for in project managers? People who understand that project management is as much art as science. People who have the soft skills to understand the business outcomes and lead a team to deliver those outcomes. They need to know the fundamentals of project management, but even more so they understand project management is a craft - and they are masters of that craft.
Posted on: June 13, 2011 07:19 PM |
Permalink
Comments (7)
Please login or join to subscribe to this item
Bill Kiessling
President| BK Consulting Group LLC
Brookfield, Wi, United States
Very basic article - nothing new. Article brought me back to 1985. Especially with the "ERP" reference.
 | rlbarto |
This is another take on one of my pet peeves: Benefits Realisation. In a nutshell, companies do not do projects so that they can be delivered on time and on budget. Projects are undertaken to achieve some benefit for the organisation. It''s the old joke about, "the bad new is we''re lost, the good news is we''re making great time". What does it matter if you are on time and on budget if you don''t actually accomplish the business objective the project was created to meet?
The better the job of identifying and defining the business purpose of the project up front, and maintaining the focus on the benefits throughout the project, the greater the likelihood the project will achieve its purpose. A corrolary is that, in some cases, because the needs of the organisation change, it may be appropriate to kill a project that is on track, simply because the justification for the project has gone.
A final point. Working as a management consultant has taught me that you always have to dig a little deeper in defining the goals and objectives of the client. Often, the things the client says he wants in the first pass turn out to be two steps removed from his real objectives and he doesn''t realise the assumptions he has made in stating the objective. Pursuing the wrong objective (or a derivative of the true objective, can unnecessarily preclude possibilities for a successful resolution. For example, the client may say the objective of a proposed project is to speed up a process. A little digging as to the real underlying problem could reveal that what he really wants is to eliminate backlogs and delays. The possible solutions would be different depending upon how you define the objective. Based on the real objective, the process may take just as long to complete a cycle, but fixing an unrelated delay in the chain that is the actual cause of the backlogs succeeds, where speeding the process cycle without fixing the delay would fail to achieve the objective. Until you truly understand what the client wants as the outcome of the project, you can''t make adequate decisions about project direction or trade-offs.
Thanks for this post. Very motivating. This is really the core of project management.
Love the topic -- Business Driven PMO -- and look forward to collaborating with David on fleshing out the details of Business Driven Projects and PMOs.
Also its evident that there's a range of opinions about whether "Business Driven" is new and important or old and tired. My answer -- its old AND important -- more important than ever in today's environment.
Good projects have always been business driven, of course, advancing the cause of competitiveness, profitability, or growth in their organizations. It’s just that the rate of change, the intensity of competition, the sophistication of buyers, and the fluidity of global markets have all cranked up so high in most industries that the traditional rate of project success is no longer affordable to most organization. Missing the scope schedule or budget mark in 70% of projects (in the oft quoted stat) is no longer possible and may be deadly.
Doing the right projects for the right reasons and “fast failure” of those that drift off the mark can be the difference between strategic success and decline for your organization.
We often find clients that clients, once they have visibility into their portfolios, find 20% or more of their projects are off strategy, redundant, or too poorly defined to succeed. Fixing this is the core of being business driven. Learn more at our Business driven PPM blog http://www.powersteeringsoftware.com/blog/ and Linked in group (http://www.linkedin.com/groups?about=&gid=3790602&trk=anet_ug_grppro) .
Finally I don't disagree that project management can be more art than science, but being business driven is no more or less artful than other aspects of PM alchemy. There are plenty of tools and methods to help teams be more Business Driven. This groups would be well served by talking about the science (and a bit about the art) of making your projects more successful.
David Irwin
Project Manager| Contractor
Bangor, N.Ireland, United Kingdom
David - I'd be interested to know how the developer, (not a formal PM by training) got on with the technicalities of project management.
Ted Gibbs
Enterprise Sr Project Manager| HEB
San Antonio, Tx, United States
The art comes in knowing the business AND being able to negotiate requests based on if they really help achieve the stated objective. On the stated side you do not get a satisfied cusomer, but on the other side the project spirals out of control with 'it would be cool if'. Obviously you miss your time and cost goals as well as a disastified customer.
Thank you for posting. Great article delving into the real world of project "leadership", which is not all what a book or test attempts to make project management conform to as an industry. Dependent on the industry, you have to be able to take the foundation and make it work in the environment you are in -- PM is not one size fits all.
Please Login/Register to leave a comment.
|
"Man will occasionally stumble over the truth, but most times he will pick himself up and carry on."
- Winston Churchill
|