Project Manager as Enabler of Business Value

The roles and skills of IT professionals are shifting and project managers will be well served if they cultivate a personal brand of enabling business value. ...

... "enabler jobs such as business enterprise architects, business technologists, systems analysts and project managers will be most in demand in the near future. " ...

Via ITBusinessEdge: Skills of Future IT Org

Agile Team Lead Role

SpinOff and Divestitute IT Projects

Not all IT projects are growth, efficiency, or talent enablers. Periodically, IT needs to support divestiture or spin-offs. These types of projects often can involve segmenting / securing the divested business in the existing enterprise systems, so that temporary IT services can be extended for a grace period. At some point, the divested business is fully separated from the systems. These types of IT projects are quite complex business projects that are interesting and offer IT project managers a great learning experience. ...

... "It was much more than an IT project. In practice it meant 1,800 users, 7 languages, 3 factories and interfaces with 100s of suppliers, customers and logistics providers! " ...

Via Personnel Today: Birds Eye Independence

Project Turnaround

Project Manager to Police the Street

Nice career move for technology project manager with financial and fraud experience ...

... "Storch has a strong background in technology systems and project management, Khuzami said in a statement. He will help to make us more efficient and nimble, and permit us to put more of our investigators on the front lines to detect and stop fraud ... " ...

Via New York Times: COO of SEC Enforcement

Experience Matters

Government technology organizations are learning (the hard way?) that experience matters. A project organization should have a mix of experience and skills, so that a pipeline of talent is being developed by more senior staff and there is adequate diversity of situational experience. ...

... "The latest Lessons Learned report from the Office of Government Commerce focuses on experience from the office's Gateway Reviews, which are the government's official assessments of its own projects and how they should proceed. " ...

Via Computerworld: IT project chiefs need experience

Project Managers Dig Deeper

Project managers perform the smell test on key measures of success and do not always accept the immediate answer without appropriate validation. Ultimately, the steering team is placing their trust in the project manager to execute on the plan, but also to understand the full business context and respond accordingly. Project managers that hone these skills are ideal candidates for future leadership roles. Keep on sniffing! ...

... "To gauge sponsorship accurately, you must gather perceptions across the project. After all, someone reporting directly to the CIO may have quite a different view than one working 1000 miles away ... " ...

Via ZDNet: IT project success factors

Project Leadership and Management

Halt Who Goes There ?

The VA executes a reset on the under-performing segment of its project portfolio. ...

... "Each of the 45 projects will be temporarily halted. No further development will occur and expenditures will be minimized. A new project plan that meets the requirements of Program Management Accountability System (PMAS) must be created by the project manager ... " ...

Via Department of Veterans Affairs: Increased Accountability

Project Managers Seek Points of View through Collaboration to Gain Strength

In a challenging phase of your project? Not sure what scenario will play out? Feel the weight on your shoulders as project manager? Hold steady on the tiller. And, open up and collaborate, per Bernanke, to educate yourself and your team on the opposing points of view. ...

... "Bernanke argued that a spirit of open-mindedness and intellectual modesty has driven his response to the financial crisis. " ...

Via Washingtonpost: Emerge Stronger

BC Commencement Address.

Separation of Project Duties

The case is made for filling management roles with multiple resources. The first lesson is to recognize that these roles exist. The technical and project roles are filled routinely. Don't forget the client relationship role and optimizing the customer experience - especially on IT projects. ...

... "Every IT effort requires that the service provider play three distinct roles: project manager, technical manager, and relationship manager. While many independent project managers and consultants attempt to play all three roles, they do so at the risk to themselves, the project, and the relationship. " ...

Via TechRepublic: Roles in IT project

Project Managers Specialize in the Project Management Lifecycle

US News builds on a NYT article regarding Tim Geithner's role as Treasury Secretary, which got me thinking about parallels to the project management space. ... Should the project manager who started the project in the front-end load part of the lifecycle be the one to finish it? ...

Normally, I would answer this with a firm yes, unless the project was running off the rails. A project manager should experience the full life cycle of the project and finish what they have started. It serves the person well and provides continuity to the project, the team, and ultimately to the enterprise.

However ... I have collaborated with project managers who are great starters, working in the front-end to understand business challenges, consider alternatives and navigate the politics to create a compelling business case that is sponsored for governance. And, I have also worked with project managers that are stellar finishers, who thrive on organizing and driving a concept to reality. Often, these project managers are not the same person. And, each part of the project lifecycle requires different skills to be successful. ... As this article suggests - that Geithner is not our finisher for various reasons ... Should we cultivate great starters and finishers in the project management discipline? organizing them into starters and finishers or openers and closers. ... Or, should we strive to build end-to-end process and people excellence?

What do you think about project manager specialization in the project lifecycle? ...

... "It's not even that Geithner was the wrong man for the job. He wasn't. He's just the wrong person to finish it. " ...

Via US News and World Report: Tim Geithner Should Go

Brasil Perspective on Project Management

Swim with the Sharks

Oh no! Turn your project managers into gamers ...

Leverage Checklists for Success

Whether you are a project manager or surgeon, don't hesitate to take advantage of the simple checklist to improve the quality of your actions. Recycle appropriate project lessons-learned into your checklist to keep it evergreen. ...

... "But a year after surgical teams at eight hospitals adopted a 19-item checklist, the average patient death rate fell more than 40 percent and the rate of complications fell by about a third, the researchers reported. " ...

Via NYTimes: Simple Checklist

UPDATE: Cool and recent reference post on checklists via ProductiveWise.

Project Manager Creates Collaborative Relationship

Healthcare continues its information transformation and progressive project management practices can accelerate the change. In this case, the project manager collaborated with the target department to understand the business challenges and the process capability --- creating the proper working relationship for a transformation journey. ...

... "Make cross-departmental understanding a priority - During implementation, our IT project manager sat in the HIM department until he fully understood our daily frustrations, processes and challenges. " ...

Via ADVANCE: Lessons Learned

Time and Budget Targets for Projects

Survey of project managers in Ireland show a greater focus on achieving the enterprise objectives over emphasis on time and budget targets. ...

... "only a third of project managers feel that completing on time and on budget are critical to project success. Some 70pc rated meeting organisational objectives as being the most important factor. " ...

Via SiliconRepublic: IT project managers

PM Goes Radical on Agile

Project manager's view on agile methods ...

Project Management Interview: Lessons from the Super Bowl, Continued

A newly minted PMP interviews for the project manager position ...

Project Management Challenge

Costing too much and falling short on delivery is the path to extinction. ...

... "Project managers agree that they are regularly charging too much – and not just to public sector clients. " ...

Via Finance Week UK: Project managers accused of costing too much, delivering too little

Project Management Career Path

Benchmarks for project manager's career path are discussed. ...

Google Project Manager Clip

Quick video insights from Google project manager ...

Project Manager Versatility

Ahhh, the versatility of project managers ...

... "My sister recently went from being an IT project manager at a major North American company to selling ladies underwear for lingerie manufacturers. " ...

Via edmontonsun: Peace of mind

Change Management Situational

Get aligned, find a champion, and leverage the art of change management to your project situation. ...

... "In my experience, successful projects tend to revolve around a certain type of project manager or coordinator. Someone who really knows the organization, is respected, collects chits constantly, listens well, doesn't personalize disagreement, remains flexible, and generally wraps a friendly persona around a persistent pursuit of project objectives. " ...

Via CMS Watch: Change Management Challenges

BlackBerry, The Project Manager's Best Friend, Just Got Better

Get this for your project managers ...

Federal-IT Project Management Progress

Feds make progress on the IT project management front, close gaps in security, and have more work to do on talent. ...

... "OMB also reported that, based on current agency submissions, 83 percent of major IT investments have qualified project managers compared with approximately 70 percent reported in last year's submissions. " ...

Via GCN: IT Perspective on the Federal Budget

Project Controller: The Project Manager's Best Friend

Halleluyah! Finally, there's an article saying what I've been saying for years. With projects becoming more and more complex, and leadership and stakeholder management requiring more attention than project managers have time for, there's a need for another role to manage the "control" aspects of the project.

This article by Robert Wourms on Projects@Work details how organizations such as State Farm have had success doing just that. Bring on the Project Controller. As a member of the leadership team for PMI's new standards for program management and portfolio management, I witnessed first hand how valuable this role was, as it freed the program manager up to actually lead the program.

The article shows how the project controller's role can include tasks such as:

1) Educating the team on processes
2) Facilitating Planning and Control sessions
3) Developing the project schedule
4) Controlling progress
5) Tracking and analyzing costs
6) Managing Issues, Risks, and Changes
7) Documenting and delivering status information

So what's left for the project manager to do? Plenty. Supporting this, the article offers a valuable table outlining the role of the project manager vs. the program controller. Read on...

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

Getting good at estimating

A couple of the current consulting engagements include good work estimation of project activities as a required end state. And it needs to be done quickly!
In one case there are a couple of high-profile projects with rigid completion dates. And the organisation has a history of fixed duration scheduling. In a balanced matrix project management environment where the functional managers have traditionally taken care of resource availability, the project managers are concerned with meeting dates. The top management is now concerned that there are sufficient fumctional resources to meet the project workload.
The other case is in a less advanced organisation. Top management wants to implement a project management regime that provides for cost and schedule management. In this weak matrix environment, there is no history of estimating either cost or schedule.

A quote I came across recently points up the dilemma:
"The trouble with using experience as a guide is that the final exam comes first and then the lesson" (Anonymous)

The challenge for an organisation is to have the lessons before the final exam. And that means starting to capture the experience. And the realisation that the capability cannot be built overnight.

There are many references as to how to 'do' estimating. The PMBOK is one obvious example and Simon Wallace at the EPM Book gives a very readable description. But we're still faced with the issue of getting to the point where estimating is an established part of the project management process. And that is not a quick transition.

So what's to do? The short answer is 'make a start'. Start creating estimates - using the techniques described in the literature. Start recording estimates. Start measuring actual effort. Start feeding back variance information into the estimating process. Start engaging other parts of the organisation in the importance of estimating. It won't happen overnight but the sooner you start, the sooner the client organisation will improve its project management capability.

Is Project Management Relevant?

Over the years, I've had discussions with software developers who question the need for project management. I've heard everything from "The developers are the only ones who really know what's needed anyway!" to "All the project managers do is slow things down and add unnecessary bureaucracy!" to "Why can't the the developers just work with the customer to give them what they need and avoid the middleman?"

The fact is, given the right developer and a fairly isolated project, all of these are valid statements. But many projects are much more complex than that. They involve multiple stakeholders with conflicting needs, offshore resources, multiple vendors, complex interrelationships with other activities and departments, and more. They frequently involve managing all of this against budget and schedule constraints.

Leading, facilitating, and managing all of these elements is where a good project manager can help. An effective project manager removes barriers for a team rather than adding barriers. Any activities that may appear like "nuisance work" to technicians, such as reporting time or percent complete against milestones, are often necessary to meet the project's schedule or budget constraints.

A good project manager will work with developers to determine the appropriate project approach, depending on the constraints and the level of uncertainty involved. Perhaps an agile approach is warranted, with learnings applied incrementally. Perhaps piecemeal deliverables can be achieved for quick wins and earlier value. A good project manager will also prepare management reports, conduct presentations, and deal with vendor issues.

Most of all, a good project manager will communicate to all parties throughout the project. Although some developers do indeed have the expertise to do all this, it distracts from the work they need to do.

This is not just a nuance of the software industry. The same holds true in any industry where technical or subject matter experts question the need for project management. Project management is a completely different skill set, necessarily so. It's geared toward leading people to achieve objectives. An organization can of course put the project manager in a better position to be successful by providing adequate tools, general principles, and minimal bureaucracy.

The article below offers clear and simple evidence of the importance of project management. It begins with the results of a 1999 study that showed that the number one reason companies stopped working with Internet design firms was not about their lack of creativity or high costs---it was about their inability to effectively manage a project.

Here's the article...

MB Journal Article Archives

Project Execution

Tom Peters and crew on strategy implementation through execution ... here's a chance for the project manager to shine ... Get the leadership support. Break the plan into chunks. Schedule the first chunk and resource the team. Start driving. ... Sounds simple. ...

... "Great execution happens in small manageable chunks by taking large plans and breaking them into manageable parts. Otherwise, the path to execution can seem so overwhelming, people can't conjure up the energy. " ...

Via tompeters!: Execution through Projects

Requirements: Where Are You Headed?

There's a good article on Projects@Work about a project manager who won an iPod by submitting his story to a "Requirements Horror Story" contest.

I can relate to his horror as his boss touted their software's ability to "solve anything" to a client---software that, by the way, didn't exist yet.

His story makes the point that, unless there are agreed-upon requirements, there's no way to tell when the project is over.

I've sometimes had this debate with clients who are afraid to commit to requirements, preferring to keep things loose. While I'm all for "managing to the present understanding," and allowing for the ability to change course based on learnings, this should all be coordinated and agreed upon at every step of the way. There should at least be an initial set of requirements or objectives. It's hard to redirect your course if you have no course.

Here's the article. Maybe you have your own requirements horror story to share!

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

Managing Expectations: Surprise Machine

Nice article on managing expectations, which is critical for project managers and business leaders. Are we managing a surprise machine? An "upside" is good, when it comes to benefits. Should we routinely under-promise? ...

... "Says Robert Sutton, professor of management science at Stanford University: If you're managing a large organization, you're managing a surprise machine. " ...

Via Charlotte Observer: Link

All About OPM3

PMI's Organization Project Management Maturity Model (OPM3) is not without controversy, and things are heating up more than ever. Some tout it's ability to help organizations navigate a growth path and others claim it's too focused on academia and doesn't hit on real world issues facing project managers.

Here are a few recent articles that show the good and the bad ---- all you need to know to decide if OPM3 is for you.

First, this month, AllPM is highlighting articles on OPM3, including the following:

The Essence of OPM3

The Business Value of Maturity Assessment

OPM3 and your 'C' Level

Comparing CMMI and OPM3

For another perspective, there's a very insightful critique of OPM3 on Projects@Work:

Assessing OPM3

Of course, we need to keep in mind that it's the first iteration, and will evolve over time. I do know that there are major improvements in store for the next release. It'll be interesting to weigh in after the product matures. Meanwhile, it's a tool, and, like any other, can easily be misapplied or overused.

Project Management Quotations

Here's a Wiki Quote site with a number of project management quotations. Despite some tired and well worn ones, there are a few gems in there, such as:

"The bitterness of poor quality last long after the sweetness of making a date is forgotten."

"Some projects finish on time in spite of project management best practices."

"The more ridiculous the deadline the more money will be wasted trying to meet it."

"The most valuable and least used phrase in a project manager's vocabulary is "I don't know"."

"The nice thing about not planning is that failure comes as a complete surprise rather than being preceded by a period of worry and depression."

"The project would not have been started if the truth had been told about the cost and timescale."

"You can con a sucker into committing to an impossible deadline, but you cannot con him into meeting it."

"All project managers face problems on Monday mornings - good project managers are working on next Monday's problems."

"At the heart of every large project is a small project trying to get out."

"Everyone asks for a strong project manager - when they get him they don't want him."

"Good project managers know when not to manage a project."

"If you don't attack the risks, the risks will attack you."

Enjoy...

http://en.wikiquote.org/wiki/Project_management

Project Management Imperatives: Ten Keys to Success

Someone recently asked me what I felt the critical success factors were for any project (i.e. what were the top "must do's"). Although I can think of many more, here were what I felt were the top ten:

1) Get the roles right. (Insure accountability; use a RACI chart or Responsibility Matrix so roles are clearly defined. Insuring people understand their commitments up front will avoid problems later.)

2) Get the goals right. (Make sure all the key stakeholders agree on the goals. I've seen more projects go wrong for this reason than any other. Time spent here will pay dividends later.)

3) Get the current scope right. (I say "current scope," because change should be expected. Projects by default contain change because they are unique in nature. It's not whether you'll experience change, it's how you analyze the potential impacts and manage the approval of the change that counts. Agreed-upon and approved scope changes are perfectly acceptable, with one caveat: It's often wise to set a limit to the number of times scope can be changed for the current product release, and defer some changes to a subsequent release, else value gets delayed.).

4) Obtain commitment from the business, customers, and other stakeholders as to their part in the success of the project. (Many projects derail because the customer doesn't live up to their side of the bargain, doesn't understand their side of the bargain, or some other necessary constituent isn't cooperating for various reasons. Obtain the right commitment up front, starting with senior management.)

5) Determine the critical success factors and risks. (Critical success factors and risks go hand in hand. Many people ignore this or sweep it under the rug, and accept any related risks as a given. The critical success factors will identify related risks and help set expectations).

6) Set expectations. (This is frequently overlooked and is a key cause of failure. The sponsor, customers, and anyone impacted by the project must be given realistic expectations for what is needed from them, how long the project will take, how much it will cost, what the uncertainty factor is, what the available resources are, and anything else necessary to avoid surprises and/or an under-equipped effort.)

7) Beware of conflicting directives. (I call this the "Robocop Syndrome." In the film, Robocop, the titular robotic policeman goes on full tilt when he encounters directives that conflict with his primary directive. I see this happen often in organizations where a project sponsor demands something that is in conflict with other key stakeholders' wishes and/or top organizational directives. This could be covered under "goals" or "expectations," but it's so important that it warrants its own point. The project manager must head this off at the pass before the project goes down a rat hole it won't recover from.)

8) Plan Collaboratively. (The act of planning is not an isolated exercise. It's a collaborative exercise and should be done with the project core team and subject matter experts via some sort of facilitated brainstorming session---possibly with sticky labels on a wall.)

9) Beware of unilateral and granular "one-size-fits-all" solutions. (This is often ineffective, both as a project management methodology and a process implementation policy. Look at the big picture, and the potential variations. Keeping a framework high-level can allow for greatest flexibility and adaptability. Aim for principles over rules wherever possible. Use rules when safety is involved, regulatory requirements exist, or exact accuracy is needed---per Marcus Buckingham's guidelines from "First Break All the Rules.")

10) Don't let rank set you off course. (Often, a senior manager pulls rank and makes requests that are either detrimental, unwise, or in direct conflict with organizational goals. When this happens, see rules 6 and 7. It is the project manager's responsibility to set the right expectations, warn of potential risks, and head off potential conflicting directives at the pass.)

There it is. My list of "must do's." Project management isn't rocket science. In fact it's not a science at all. It's more of an art. Hopefully, the guidelines above can serve as a useful palette.

Predictive or Adaptive?

WSJ article makes light of inaccurate predictions, something which project managers need to get comfortable with (think project and portfolio estimates and forecasts). However, the prediction below seems to have come true, if you are a frequent visitor of college campuses. ...

... "In 1929, a New York City haberdasher, John David, predicted that the well-dressed man of 2020 will wear shorts for every occasion except formal events. " ...

Via Wall Street Journal: Deja Vu

Influencing People: The Project Manager's Secret Weapon

I recently attended a presentation on self-awareness and influence by Dr. Charles Dwyer, Academic Director of the Aresty Institute’s Leading and Managing People program in the Wharton School. I was so impressed with the presentation that I bought his book, The Shifting Sources of Power and Influence.

This book was a real eye-opener, and a jewel for anyone in project management. In the book, Dwyer states three major challenges we all face:

• Dissonant Value Systems (i.e. people’s conflicting value systems, made even more visible by the advent of the media, internet, etc.)
• Diffused Power (i.e. power being spread around in a matrix fashion, with more and more decentralization and special interest groups, etc.)
• Limited Resources (We all face a limited set of resources, made even more challenging by our lack of a mindset geared towards accepting tradeoffs, or a good mechanism to guide operational priorities)

Sound like any projects you know?

Dwyer goes on to caution that public statements, such as vision, mission, organizational values, etc. may be useful for articulating the values of the leadership or giving people a sense of structure, but do not in themselves change anyone’s value systems. Many leaders assume they can use these statements to change people’s value systems to match organizational values, but this is a myth.

What is needed instead is the ability to influence others by getting them to change their behavior to match your values. To do this, have a clear picture of what you want the unit to look like; set specific, measurable objectives; and insure that people have a way of achieving those objectives.

According to Dwyer, some tried and true methods include asking people for help, offering or implying something in return, or influencing indirectly (i.e. working through someone else who’s in a better position to influence).

Dwyer points out five guidelines for influencing people (I’ve paraphrased them):

1. Insure they have adequate capability (Do they know what to do, have the competence and self-confidence to carry it out?)
2. Address their perception of “Potential Value Satisfaction” (WIIFM or “what’s in it for me”)
3. Address their perception of the probability of value satisfaction (i.e. Do they trust you? You must build trust through visible examples.)
4. Address their perception of cost (Do this by giving them alternatives or a sense of options, and helping them understand the costs and implications.)
5. Address their perception of risk (Try to assume or distribute some of the risk. Don’t ignore it.)

These are the five things everyone weighs in their mind when someone attempts to influence them. In essence, the five elements (four of which are perceptions) make up an equation for behavior. We can influence people’s behavior by addressing this equation (I’ve paraphrased for simplicity):

Behavior=Capability + (Perceived Value * Trust factor) – (Perceived cost and risk)

These are just some of the gems of wisdom in Dwyer's book. He offers reams of memorable examples, often with a humorous style. With 90% of a project manager's job being communication (including influence), I highly recommend Dwyer’s book for project managers, or anyone in a leadership position for that matter.

Olympic IT Project: Risk Management Challenge

Atos project team will manage the Olympics IT project for Vancouver games. It manages risks by leveraging accumulated knowledge and experience forward. Lesson learned, knowledge transfer, sustaining core team members, and scaling high-performance teams are all ingredients of successful Olympic technology events. ...

... "In June 2006, only months after completion of the Torino 2006 Winter Games, Atos Origin dispatched IT managers and engineers to already start working on the Vancouver project. Currently the size of the Atos Origin IT team in Vancouver is around 15 but the team will grow rapidly over the next couple of years. During the 2010 Winter Games, Atos Origin will manage the technology consortium team estimated at 2,000 staff, including 400 Atos Origin experts, made up of locally hired staff, local volunteers and overseas Olympic Games technology experts.

The complex, massive IT infrastructure of the Olympic Games is deployed by large teams of people into different cities in different countries every other year. Such a major task is all about risk management capitalizing on the knowledge gained from previous Games Operations. This knowledge and experience transfer is critical in keeping costs down and in lowering the risk of future Olympic Games. " ...

Via Atos Origin: Atos Origin IT Team already in place for the Vancouver 2010 Olympic and Paralympic Winter Games

Right Brain Project Management

I recently re-read Daniel Pink's book, A Whole New Mind. I noticed now that it's out on paperback, the subtitle changed from "Moving from the Information Age to the Conceptual Age" to "Why Right-Brainers will Rule the Future."

The latter is probably more accessible and gets to the heart of the book. The premise is that with more technical jobs being eliminated due to automation and offshore outsourcing, we're left clinging to the one thing that computers and offshore resources can't replace---the soft skills. It's not that offshore people don't have the capacity to do this, it's just not effective from a remote location.

The books specifically outlines Six Senses that are now required to compete in today's market (I'd add that these were always needed for effectiveness, but now it's a necessity for career survival). The Six Senses we need to build are:

1) Not just function, but DESIGN (the WOW factor)
2) Not just argument, but STORY (i.e. we need to be storytellers to make a good case)
3) Not just focus, but SYMPHONY (i.e. synthesis of complex relationships vs. heads-down analysis)
4) Not just logic, but EMPATHY (incidentally, the key trait in Daniel Goleman's Emotional Intelligence)
5) Not just seriousness, buy PLAY (fun leads to employee satisfaction, which leads to customer satisfaction and profits. Therefore, Fun=$ !)
6) Not just accumulation, but MEANING

FACT (not from the book, but relevant nonetheless): Per a recent management forum of 70 business schools, many of them are requiring less quantitative courses and more leadership courses. Also, a number of organizations are now recruiting design students instead of MBAs.

The key is that the logical, sequential left-brain stuff is still necessary, but we need to compliment it with the more contextual and feeling right-brain skills. With communication being 90% of a project manager's job, I'd say this directly applies to project managers as well.

Below is a link to Pink's book on Amazon...

Amazon.com: A Whole New Mind: Why Right-Brainers Will Rule the Future: Books: Daniel Pink

Managing the Grey Areas: Lessons from the Leadership Quadrant Seminar

On November 15th and 16th, I conducted a seminar with productivity consultant Jerome Jewell called The Leadership Quadrant: 4 Ps for Organizational Excellence. The 4 Ps are Principles, People, Productivity, and Process. It was held at the National Constitution Center in Philadelphia, and we incorporated the museum’s rousing multi-media show, Freedom Rising, into the seminar.

The seminar participants came from the healthcare, criminal intelligence, and manufacturing sectors, which led to some fascinating discussion and dynamics. With any seminar, the value to all in attendance is magnified by the contributions of the participants, and this was no exception.

In the seminar, which included sections on principles, emotional intelligence, systemic thinking, talent management, innovation, project management, and more, the collective group highlighted a number of “grey areas” that a manager must frequently weigh when making decisions.

Some questions arose, such as:

"What if someone no longer likes a role they excel at and prefers a role they're poor at?"

"Do people always need to see the big picture?"

"Should one person be expected to serve the role of a manager, leader, and administrator? A strategist and tactician? A generalist?"

"How do you strike a balance between effective time management and remaining available to your staff?"

"Are recurring meetings effective or are they time wasters?"

In line with these questions, below are some of the factors that managers must consider:

• People’s individual needs vs. organizational goals
• Big picture inclusiveness vs. security (or the desire to give people narrow focus)
• Using generalists vs. specialists (and where the specialty should focus – on a functional area or on a particular skill)
• Effective time management vs. flexibility and being available to your staff’s needs
• Recurring meetings vs. consideration for people’s time
• Informing vs. influencing (for deciding whether to email or meet; even then, the decision is not always straightforward)
• Innovation vs. execution (knowing when to move from ideation to “getting things done”)
• Systemic (whole view) thinking vs. systematic thinking (routine, repeatable process)
• Vigilance vs. delegation (how much is safe to delegate, and to whom?)
• Firm principles vs. ethical dilemmas (should a firm principle ever be bypassed?)

In all of these cases, the group determined that the answer isn’t always black and white, and that each situation requires weighing these items. The trick is to observe, orient, decide and act quickly (referencing Colonel John Boyd’s OODA principle).

On the item of firm principles vs. ethical dilemmas, the group applied lessons from various cases throughout history where the US Constitution was challenged. It was obvious that there was no “one size fits all” answer.

With more recent events, consider OJ Simpson’s book. If you manage a bookstore with a principle of defending freedom of speech, do you carry O.J. Simpson’s new book, even though it is "ethically challenged," to say the least? Most large-chain bookstores creatively tried to satisfy both sides of the equation by donating all of the proceeds to the victims’ families. Of course, in the end, the book was canceled, but for a while, this was a real challenge to bookstores.

All of this reaffirms that management is abstract, not concrete. Managers cannot have all the answers; but they can and must insure that the right questions are considered, and they must have the courage to make decisions.

Extreme Project Management: Reality Rules

I just finished reading Doug DeCarlo's book, Extreme Project Management. I met Doug at a recent PMI event we both presented at. Not only is his keynote presentation a crowd pleaser (hint: he plays the drums to illustrate the pace of a typical project and uses Noah's Ark as a sample project from the "ultimate Sponsor"), but his book is chock full of practical, immediately usable ideas.

I was amazed at how much his philosophy mirrors my own, with a focus on simplicity, value, results, and the understanding that change is inevitable. A key point of Extreme Project Management is that reality rules. Plans are nice, but then results must drive further planning instead of assuming reality will yield to the plan.

As an example of simplicity, consider what he calls "The Four Business Questions":

1) Who needs what and why?
2) What will it take to get it?
3) Can we get what it takes?
4) Is it worth it?

As another example, check out his "Three Sentence Project Skinny":

1) Who will do what for whom?
2) This project will be considered completed when: ___
3) Why? This project supports the organizations objective to: ___

The book also offers handy checklists (such as what to ask the sponsor during the first and secend meetings, etc..), the 4 Accelerators, the 10 Shared Values, the 7 Win Conditions, and more.

Although the book is the size of the Encyclopedia Britannica, it's extremely readable and has diagrams that bring together all the concepts in the book. I highly recommend it to anyone looking for a book grounded in reality as opposed to academic theory. Above all, this will help project managers succeed where the rubber meets the road---communicating and dealing with stakeholders.

Amazon.com: eXtreme Project Management: Using Leadership, Principles, and Tools to Deliver Value in the Face of Volatility: Books: Douglas DeCarlo

Earned Value Lies and Truths

There was a great quote from Benjamin Disraeli in David Hillson's letter to the editor in the latest PM Network Magazine.

Disraeli allegedly* said, "There are three kinds of lies: lies, damn lies, and statistics."

* As an aside, there's apparently some debate over the actual origin of this phrase.

In any case, Hillson's interesting letter was cautioning those who frequently misapply statistics, and offered some clarification the terminology----specifically, the mean (average), mode (most frequently occuring item), and median (the middle item if all were lined up in order).

I find that many misuse Earned Value statistics the same way. The intent of EVM is to be an early indicator of a potential cost or schedule overrun (and I personally feel that it's better at predicting cost than schedule). However, much like the Ghost of Christmas Future, it's not set in stone. There are many things a project manager can do to get things back in order. More importantly, sometimes there are reasons for the apparent variance that indicate that the variance is explainable and not a concern at all.

The key with EVM (much like any metric) is to not take the statistics at face value, and to use them as a trigger to do further subjective examination. It's a tool, and organizations often overuse such tools (much like they do with Six Sigma). If all you have is a hammer, everything looks like a nail.

Microsoft Live: Project Management App ...

Review of the Microsoft Office Live servicce by CNet ...

... "The Premium version has more back-office tools, like a project management application and a time manager. " ...

Via CNet: Link

IT Project Managers: On Board?

We need IT project managers to be on-board with project management tools. What works? Compliance or coaching? ...

... "We get more buy-in on using the new tools from IT's customers than from the IT project managers. How do I help get them on board? " ...

Via ComputerWorld: Read

Hug a Project Manager Today ...

Fun video .......

Unconsulting: Common Sense Lessons for Project Managers

At someone's recommendation, I just finished reading Unconsulting, by David Newman. Fascinating and energizing book for anyone in business.

His book is partly inspired by Peter Drucker's statement, "Only marketing and innovation produce revenue. All other business functions produce costs." To this end, Newman offers that "the bottom line is meaningless if the top line is weak." He points out that, according to studies, "Companies with the same earnings per share that got there from SALES were worth about 30% more than companies who got there with COST CUTTING."

Newman, who, according to the book's back cover, has been called "a younger version of Tom Peters with less hair," offers 95 common-sense "in your face" tips.

A few more key points, paraphrased from the book:

• When consulting, talk to people (especially the impact points such as customers, suppliers, etc.) to gain anecdotal data to gain texture, context, and perspective.
• 95 percent of problems can be addressed by making significant changes to 5 percent of the processes, people, or technology.
• Simplicity defined: Find the shortest way to the best answer.
• Be with the client, not of the client. Rock the boat. You're there preceisely for that reason and to give advice. You're there to do your thing for them, not be a "yes" man (or woman).
• There is no cookie-cutter. Don't sell canned solutions. Listen to the client and look at unique angles to each engagement.
• Bill Cosby says, "I don't know the key to success, but the key to failure is trying to please everybody."
• Don't isolate talent management and organizational development to one department. Institutionalize it in all your management.
• The unconsultant handles an engagement in this way:
  
  "I'll ask some questions, do some research, guide the discussion, help set clear and specific objectives for the work, offer options, tools and answers each step of the way, and then we'll do the work together."
  
  All in all, very refreshing stuff. And a good model for project managers as well. I highly recommend this book. It's not available on Amazon.com, only on Newman's site, but well worth getting. Also, see the wealth of free white papers on his site, as well as his blog...
  
  David Newman: Professional Speaker Motivational Speaker and Keynote Speaker and Business Consultant

IT Management Career Evolution: Flexibility ...

Flexiblity, coordinating, bridging, IT-savvy are all descriptions of the new (project) manager position in the information technology field. The "computer guy" career path is evolving. SIM finds these as requisite skills: planning, budgeting, scheduling, leadership, and risk management ...

... "But it's even more about IT-savvy project managers pegged to coordinate initiatives that bridge departments, where the dotted lines on the org chart are every bit as important as the boxes. " ...

Via Information Week: IT Manager Jobs Are Up 44% In 5 Years ...

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.

Leading and Influencing: The Project Manager's Secret Weapon

There's an excellent article by Frank Saladis on allPM about how to lead and influence others. Topics such as boosting your credibility, practicing empathy, and maintaining organizational awareness are discussed, as well as some good tips for engaging team members and obtaining buy-in.

From my experience, these are the things a project manager needs to get right. The rest is just details.

Here's the article. Well worth reading.

Positive Leadership in Project Management – Team Building, Influencing and Leadership By Frank P. Saladis, PMP :: ALLPM Project Management :: Project Manager - Project Management - Information - Forum Manager- PM Tools - Articles -PMI

IT Project Management Book For the Ages

For those managing IT projects, an invaluable resource is Jolyon Hallows' comprehensive book, Information Systems Project Management. Be sure to get the 2nd edition (link is below). It's a bit expensive, but Amazon has it used as well for less money.

Even though I've been managing projects for years, I always like to check out various books to gain new perspectives. This one is exceptional. It offers practical advice with"what if" situations covering most political quandaries, handy checklists (there's a great one on scope considerations), and concise "real word" tips on using various methodologies.

If you're an IT project manager and only buy one book this year, this is it. Of course, if you buy two books, you can check mine out as well. :-)

Amazon.com: Information Systems Project Management With Infotrac: How To Deliver Function And Value In Information Technology Projects: Books: Jolyon Hallows

Project Framework Leverages ITIL Provides Common Status View ...

ITIL-capable service solution is implemented as a management framework across multiple implementations to enable a common performance status view. ...

... "Aspiren has selected Infra's IT Service Management solution, infraEnterprise, to support the rollout of a new National Performance Management Framework (NPMF) to local authorities across the UK. The infraEnterprise implementation will ensure that all procedures associated with deploying the initiative are fully compliant with IT Infrastructure Library (ITIL) best practice. Aspiren is using infraEnterprise's Workflow module to automate the management of 400 local authority technical installations, and to provide managers with one common view of the status of the implementation project. " ...

Aspiren Puts Infra To Work On New National Performance Management Framework ...

NPMF - What Is NPMF?: "The project has successfully established the first truly national template for a performance management framework in Housing Benefit departments. Essentially it brings together in one place all the key components of a world class performance management framework ... "

Einstein Project Management Tip #5: Imagination Counts

Our next project management tip from our Einstein series regards the need to challenge the status quo----to think out of the box. Consider this quote:

"To raise new questions, new possibilities, to regard old problems from a new angle, requires creative imagination and marks real advances in science."

Of course, Einstein also famously said, "Imagination is more important than knowledge." To a project manager, who's typically focused on things like scheduling, monitoring, reporting, and driving the team to completion, this can be a particular challenge. But it's important nonetheless.

Imagination is required in many situations, including (but not limited to):

• Achieving success when the odds are against you
• Conceptualizing ways to achieve the objectives more effectively
• Brainstorming solution ideas and possible risks
• Overcoming barriers, whether political, technical, or physical
• Improving the cusotmer experience

For some practical advice on building the right team for innovation, see my blog series on Tom Kelley's The Ten Faces of Innovation.

More to come.

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...

Einstein Project Management Tip #3: Silence is Golden

Here's our next installment of project management tips from Albert Einstein, the ultimate "PMThinker."

Everyone knows Einstein's famous equation, E=MC2. But he had another one that was also enlightening...

"If A=Success, then the formula is A=X+Y+Z. X is work. Y is play. Z is keeping your mouth shut."

How true this is. Often, a project manager's natural tendency is to be vocal and forward. And sometimes, this is indeed warranted. But more often than not, it's a good idea to show restraint and wait to hear all sides before offering your views.

This should not be confused with the vital need to ask plenty of questions. Rather, this refers to the need to think through the issues and hear all sides before voicing definite opinions. Sometimes, silence is golden.

Einstein Project Management Tip #1: Goals Rule

To celebrate the one-year anniversary of PMThink (yep, we've passed the one-year mark and now have over 1,000 posts - meeting our goal for the first year), I've decided to have a little fun by tapping the mind of the greatest "thinker" of all time----Albert Einstein.

To many, Albert Einstein is synonymous with the word "genius," and rightfully so. In fact, the part of his brain responsible for mathematical and visual/spacial thinking was discovered to be 15% greater than the average human. In addition, it lacked the usual groove that runs through that area, which supposedly enabled his neurons to communicate more effectively. In other words, he's someone worth learning from.

Over the next few weeks, I'll enter some posts highlighting his quotes as they apply to project management. Think Einstein doesn't have anything to do with project management? Think again. Here's the first one...

"Confusion of goals and perfection of means seems, in my opinion, to characterize our age."

The same could be said for project management today. With all the focus on execution and delivery, many project managers fail because they make a huge assumption that the goals and requirements are clear. As we strive to perfect the ability to finish on-time and on-budget, let's not forget the need to make sure that the goals of the sponsor are crystal clear, since that's where most projects fall short.

Stay tuned for more "Einstein project management tips."

Sage Advice for New Project Managers

Mark Mullaly has a great editorial in Projects@Work, titled "What I Wish I'd Known." It's an honest, heartfelt answer to an inquiry from a reader asking what he wished he'd known before entering project management.

Mullaly makes some great points, especially around the importance of asking questions. A career project manager, he learned the ropes the hard way, through trial and error, and discovered what worked and what didn't.

As Albert Einstein said, "The only thing that interferes with my learning is my education."

I recommend that those new to project management read the article, if for no other reason than to understand what the real paths to success are, such as communication, business acumen, and a true understanding of people and what makes them tick.

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

IT Purchasing Standard: A New Tool for Project Managers

As reported in Computerworld, the Software Engineering Institute (SEI) issued a preliminary report on IT best practices on acquiring hardware, software and services, covering the entire procurement process.

This will extend SEI's Capability Maturity Model Integration (CMMI) as a new global standard for IT acquisition. The effort is being backed by GM and the U.S. Department of Defense, who will be piloting the standard.

The Computerworld article (link below) includes a link to the SEI preliminary report. It'll be interesting to see how this integrates with project management methodologies and PMI processes. It should be a welcome addition to the project management toolset.

GM backs IT purchasing standards

Talent and Project Management

I received the latest PM Network magazine from PMI the other day, and several things jumped out at me, especially following my last blog post on the winds of project management changing.

First, Neal Whitten had a great article about how a project analyst (what I've often called a "project control specialist") can be a valuable aid to a project manager by taking on the responsibilities of: project tools management, plan development, sub-plan collection, project support, supporting project tracking meetings, filling in for the project manager at times, and other areas that can free a project manager up to actually lead the project.

It got me thinking about the talents needed for the project manager role, the project analyst/specialist role, and any other roles needed on the project. But more than that, it got me thinking about talent management in general, and what it means to the project management industry.

Just look at these headlines, all from this month's issue:

• Attracting--and Keeping--top talent
• Executive Identity: Project managers should learn to think like executives
• A People Person: Succeeding in project management---and getting what you need from thise around you---requires a well-honed set of people skills
• Virtual Reality: Dispersed project teams are sparking shifts in management and leadership styles

Clearly, the talents needed to manage projects go way beyond schedule, budget, and cost control. Notice I said "talents" as opposed to skills or knowledge. As Marcus Buckingham points out in his excellent book, First Break All the Rules, there is a huge difference between skills, knowledge, and talent. The first two can be taught. The last one--talent--is innate, and cannot be taught.

This becomes clear when you apply Buckingham's definition of talent as "ANY recurring patterns of behavior that can be productively applied." Everyone has talent. It's just a matter of discovering it and matching them to the right role. The key point is that a person's nature cannot change that much, so it's important to select someone with the right talents (i.e. innate traits). Once that's done, you need to set clear expectations, motivate the person (through praise and recognition of their strengths), and ultimately develop the person (building on the strengths that already exist instead of fruitlessly trying to fix weaknesses).

So what does this mean to the project management field? Everything. It means we need to begin thinking about these innate talents when we hire and assign project managers, when we staff the project, and when we consider how to motivate the team. The talents needed for each role will be different. And, based on the nature of the project and the stakeholders involved, the talent required to manage each project may be different. There is no "one size fits all" when it comes to talent selection.

It's not that skills and knowledge aren't important, but these two items without the correct talents will not bring about success.

What I like about Buckingham's book is that it's based on facts---years of research with the Gallup organization. Anyone who selects and manages people should read this book. And when you do, think about the diverse talents needed for each person on your team, and for the project manager role for each individual project.

Project Management Winds Are Changing

There's an excellent article by Betsy Morris in the current issue of Fortune Magazine about how the Jack Welch way of winning is---dare we say---a thing of the past.

How is this relevant to the project management field? Well, for one, it means recognizing the winds of change in the industry, and how projects are selected, promoted, and managed. Above all, this impacts program and portfolio management. Particularly, note four trends in management thinking:

Innovation:

Let's take Welch's old rule of being number 1 or 2 in your market (or else fixing, selling, or closing the business). The new rule is to find a niche and create something new. The article uses CocaCola as an example of a company that was basking in their glory as number 1, but eventually realized (although it took a while) that energy drinks and bottled water were about to pass them. As the article points out, energy drinks "are now expected to outearn every other category of soft drink within three years." Parhaps marketing guru Harry Beckwith said it best in Selling the Invisible when he said that it's fine to do something 10% better until someone else comes along and does it 110% different.

Customer-Centric Management:

Welch started a whole movement of focus on the shareholder, which led many organizations to ignore the future amid pressure to appease shareholders and "make the numbers." Now, organizations realize that the customer is king. The article references several companies that have made this realization, and the trend is heading in that direction. After all, statistics show that even a minor improvement in customer retention leads to a major increase in profitability. The days of short-term thinking may be finally coming to an end.

Reinvention vs. Incremental Change:

Since it seemed Jack Welch could do no wrong, everyone imitated whatever Jack did---and Six Sigma was no exception. The problem is that, according to the article, of the 58 large companies that announced Six Sigma programs, 91% have trailed the S&P 500 since. As the article points out, that's mostly because Six Sigma is intended to "fix an existing process," whereas innovative companies that developed new and unique products (or reinvented their business) took the lead.

Stop Ranking Your Players; Inspire Passion:

Once of Welch's most controversial systems was to constantly rank his employees and regularly weed out the "C" players. But companies have had difficulty getting productivity and innovation out of "increasingly disenfranchised employees." In the article, Christopher Bartlett of Harvard Business School put it best:

"People don't come to work to be No. 1 or No. 2 or to get a 20% net return on assets. They want a sense of purpose. They come to work to get meaning from their lives."

Side editorial: For the "enlightened" approach of finding the hidden strength in everyone (something Peter Drucker always suggested), read Marcus Buckingham's Now Discover Your Strengths (or any of his books for that matter). Or read Dennis Littky's The Big Picture: Education is Everyone's Business. I assure you, you'll never be the same.

Meanwhile, I highly recommend the article (the link is below) for those looking for the latest trends in management thinking, and who want to remain one step ahead.

From a project management perspective, the handwriting is clearly on the wall. The traditional "execute to a set of deliverables" approach won't cut it. Today's project manager needs to be thinking about things like innovation, customer focus, business transformation, business acumen, change leadership, and team passion. Those focused on merely schedule, budget, and scope will soon be dinosaurs.

Fortune: The new rules - Jul. 11, 2006

Project Management Lessons From the Other Napoleon (Hill)

I've written plenty about project management lessons from Napoleon Bonaparte. But there's another Napoleon with equally valuable lessons---Napoleon Hill, author of Think and Grow Rich.

For those not familiar with Napoleon Hill (who, ironically, also found inspiration from Napoleon Bonaparte), he wrote Think and Grow Rich in 1937 after spending years of research on the habits of rich and successful men at the request of Andrew Carnegie. For his book, Hill interviewed some of the most famous achievers in history, such as Thomas Edison, John Wanamaker, Charles Schwab, Henry Ford, Woodrow Wilson, FDR, and others.

From the book, here's how Napoleon Hill describes the way to go from desire to riches (by substituting the word "money" with "objectives," we can apply the same lessons to successful project management). My comments are in brackets.

1. Fix in your mind the exact amount of money [exact objectives] you desire. It is not sufficient merely to say, "I want plenty of money." Be definite as to the amount [Same with objectives. Be specific].
2. Determine exactly what you intend to give [committments] in return for the money [objectives] you desire.
3. Establish a definite date when you intend to possess the money [objectives] you desire.
4. Create a definite plan for carrying out your desire, and begin at once, whether you are ready or not, to put the plan into action.
5. Write out a clear, concise statement of the amount of money [scope and objectives] you intend to acquire. Name the time limit for its acquisition. State what you intend to give in return for the money, and describe clearly the plan through which you intend to accumulate it.
6. Read your written statement aloud, twice daily, once just before retiring at night, and once after rising in the morning. As you read, see and feel and believe yourself already in possession of the money [objectives].

Hill once said, "A goal is a dream with a deadline." He knew the importance of setting target dates and looking at a concise statement of your goals and committments daily. This can be likened to a scope statement and milestones list, which should be read regularly and not stuffed in a folder.

He also discovered the power of positive thinking, what one might refer to as "thinking the future into existence" (hence the title THINK and Grow Rich). He found that, just by thinking of your goal regularly, you attract that which you need to achieve it.

In all, the book offers 13 steps to achieving your desire, be it money or anything else. It should be noted that the book is not just about acheiving money and gets into metaphysics, etc. as well. There's a reason why it has sold 15 million copies to date (the best selling self-help book of all time).

I highly recommend the book to anyone who is trying to achieve a goal, which should be everyone, and CERTAINLY should be every project manager.

The Distributed PMO: Lessons From Strange Places

I've read two pieces of information lately that couldn't be more different, and yet they both got me thinking about the benefits of what I call a "distributed PMO."

First, as I mentioned last week, I had read about Ken Kizer's magnificent transformation of the formerly abysmal Veteran's Health Administration (a poorly run group of hospitals mired in government hierarchy and bureaucracy). He established an network of regional "hubs" (what he called Virtual Integrated Services Networks, or VISNs - pronounced "visions"). Each VISN was itself a network of partnerships, associations, alliances, hospitals, etc. that worked together for the good of the customer.

The VISNs had the benefits of standardized quality with local presence. Decision-making was moved from Washington HQ to the VISNs, who were closer to the action than Washington HQ could ever be.

The role of headquarters became one of support, guiding principles, consulting advise, information services, and change leadership. Headquarters drives behaviors that benefit the overall structure.

Forms and approvals were reduced to a bare minimum. A relentless focus on the customer/patient (one of my battle cries, as most of you know) now guides all decisions and research.

If this isn't a good model for a PMO, I don't know what is. If project managers and functional experts (each who rely on one another for success) operated in various "regions" and/or functions (close to the action), and the PMO's role were to provide (and I repeat from above) support, guiding principles, consulting advise, information services, and change leadership, more PMOs would become a valued and integrated part of their organization.

And if the focus were on reducing forms and bureaucracy, helping project teams be successful, and improving the customer experience (as opposed to an internal focus on merely schedule and budget metrics), PMOs might find themselves more popular as well.

Incidentally, this also happens to mirror the Toyota organizational model.

The idea of a distributed, integrated network isn't unique to business. It even happens in nature (here's where the strange part comes in). I was reading about a giant sea creature, larger than a blue whale, called a Giant Siphonophore (Praya sp.). The creature (yes, this is true, folks) runs 130 feet long and is actually made up of many other life forms, each having its own specialized role that works to service the whole entity, yet is unable to exist on its own. In other words, the Giant Siphonophore is a "colonial life form." As I read this, I was again reminded of the concept of a virtual, yet integrated network.

Yes, I actually make these odd connections, but ideas can come from anywhere. By the way, the creature can be seen in the IMAX film, The Living Sea (available on DVD). Here's more info on the colonial nature of the Giant Siphonophore and it mutually dependent parts. Food for thought.

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 Management Lessons from Mars

Brian Muirhead, the project manager for the Mars Pathfinder program, had some good tips to share with Projects@Work this week.

Some key learnings, extrapolated from the interview:

• Innovation and bold ideas are often necessary to meet what often seems like an impossible challenge. The trick is to balance the cost and time savings with the risks.
• A diverse team is key. It's better to have people that are different, with complementary skills, than have a bunch of people who think and act the same way.
• A small core team that can share issues, problems, and resolutions, with one person at the helm, is an effective way to run a project.
• Trust, honesty, and personal committment are traits that need to be prevalent throughout the team.
• Test, test, and then test again. Don't rely on luck. If you can't test using the exact situation, then simulate it as best you can, testing as much as is possible.
• A team is only as good as it's weakest link. It's up to the project leader to identify those people that aren't up to the task and remove them or find an area that suits them better.
• Ensure team members have opportunities to make personal connections and grow.
• A project manager must simultaneously provide the glue (keeping the team cohesive and focused) and the grease (removing barriers).
  
  Here's the full interview...
  
  http://www.projectsatwork.com/content/Articles/232113.cfm

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

Move Over PMP: PMI Announces Program Manager Credential

As reported in PM Forum, PMI has announced their new Program Manager credential, which looks to be like a PMP on steroids.

Earning the new credential will be like passing the seven trials of Hercules, with education reviews by PMI staff, reviews of experience by a panel of program managers, a multiple-choice scenario-based exam, and an assessment by a team of raters selected by the candidate to rate them during on-the-job program management performance.

Any guesses as to what the new credential will be called? How about PME (Program Manager Extraordinaire) or KOAPM (King of All Program Managers - oops, that wouldn't work for female program managers). Maybe SPM (Supreme Program Manager)? Hey, we get enough jokes about the PMP acronym, why don't they continue the trend and use PMS (Program Management Specialist)?

I better quit while I'm behind.

In all seriousness, it's good that the credential will require such a rigorous application process. With so many organizations virtually guaranteeing "instant PMPs," this one should have quite a bit of prestige.

While the PMP certification assures a solid foundation of project management knowledge, this one should give organizations the confidence that the certified program manager is indeed worthy of managing large programs (although nothing is foolproof).

Here's the full article on PM Forum, where they list PMI's stated qualifications for certified program managers. One might argue that a senior project manager should have the same qualifications (although PMI's FAQ page attempts to distinguish the project manager role from that of the program manager).

PMFORUM, Connecting the World of Project Management PMFORUM Breaking News: PMI INTRODUCES PROGRAM MANAGER CREDENTIAL

One-Page Project Status Report; Keeping it Brief

There's a great writeup in Projects@Work about project status reports, including tips on meeting format and frequency as well as a format for a one-page status report.

According to the article, there are 5 Project Status Best Practices:

1. Consistency — The status process should be basically the same for large and small projects, and consistent with their measures of success
2. Escalation — The status process provides a mechanism for escalation of key issues.
3. Simple — One page with the ability to drill down for details when necessary
4. Public — Status is available to all (as appropriate) in order to communicate issues, risks and corrective action measures
5. Inclusive — All projects are required to provide status on a consistent set of metrics

For busy managers who see loads of project status reports, it's much easier to have a consistent, brief summary of what's really happening on each project. They don't need a dissertation on all the details, nor will they get a clear picture just looking at performance metrics. Much like on a business case, most just want the executive summary. Simpler is better. Less is more.

For those looking to improve their status reports (and their credibility with management), read on...

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

Test Your Project Management Savvy

Riddle Me This, Project Managers!!

For those who like puzzles, they're running a program on AllPM this month based on Napoleon on Project Management by yours truly. Each week or so (through June and into July), I've been asked to pose some challenging scenarios to be discussed on the AllPM forum.

After each puzzler runs for a week or so, I then respond with what Napoleon might have done (at least, as far as I know, since he's unavailable for comment).

Check out puzzler#1 for an example (it generated some good discussion in the forum). Then take a shot at discussing your thoughts on puzzler #2.

Best of all, the folks at AllPM are having some fun with this and will be offering some free French wine to at least one "winner," to be announced on Bastille Day, July 14th. Join the fun! Here's the link...

ALLPM Project Management :: Project Manager - Project Management - Information - Forum Manager- PM Tools - Articles -PMI

Dealing With Primadonna Software Developers; Are Project Managers Worth Their Salt?

OK, I'm sure many of you have dealt with software developers who feel that a project manager adds no value to the "war effort." Often, they view the project manager as a burdensome pain in the butt that keeps pestering them for completion dates, but has no understanding of the "real work being done."

Here's a great article that not only addresses just what an important role the project manager plays (above all, an ability to see the big picture, remove barriers, and proactively solve problems), but provides a good roadmap for project managers so they don't become what the software developers accuse them of being.

At any rate, it's a good list for all project managers to show developers when they question what value the project manager provides.

Ode to Project Managers

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

Project Manager Toolbox: Google Spreadsheets ...

Had a chance to test out Google Spreadsheets today and think they did excellent job with the beta. Feels like working with the client copy on the desktop. Can you imagine maintaining project documents (financial projections, issues lists, etc.) with a team --- collaboratively and securely using the internet from anywhere in the world without needing your own internal infrastructure --- servers, software. I am sure there are bugs and deficiencies, but this is clearly an inflection point in the IT industry. Kudos to Google for getting there first!

Project Manager Toolbox: Google Spreadsheets ...

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