Fundamentals of Project Management

Joseph Heagney

• Éditeur: AMACOM
• Année: 2016
• ISBN:
  9780814437377
• Édition: 5
• Sujet: Betriebswirtschaft
• Sous-sujet: Buchhaltung & Budgets

Project mishaps are all too common but often easy to avoid. Fundamentals of Project Management gets both new and current managers up to speed on the basics—the first crucial step for completing projects timely and on budget.

Having already helped many generations of project managers navigate the ins and outs of every aspect of successful project management, this revised edition remains the perfect resource for succeeding in this complex discipline that has changed greatly in recent years.

In Fundamentals of Project Management, management expert Joseph Heagney contains new information on topics including:

• Clarify project goals and objectives
• Develop a work breakdown in structure
• Create a project risk plan
• Produce a realistic schedule
• Manage change requests
• Control and evaluate progress at every

Fully updated in accordance with the latest version of the Project Management Body of Knowledge (PMBOK®), this all-encompassing book contains expanded coverage on areas such as estimating, stakeholder management, procurement management, creating a communication plan, project closure, PMP certification requirements and more.

Full of tools, techniques, examples, and instructive exercises, Fundamentals of Project Management will refresh your knowledge and equip you with the proper skills to succeed.

CHAPTER 1

AN OVERVIEW OF PROJECT MANAGEMENT

What’s all the fuss about, anyway? Since the first edition of this book was published, in 1997, the Project Management Institute (PMI) has grown from a few thousand members to nearly 462,000 in 2015. For those of you who don’t know, PMI is the professional organization for people who manage projects. You can get more information from the institute’s website, www.pmi.org. In addition to providing a variety of member services, a major objective of PMI is to advance project management as a profession. To do so, it has established a certification process whereby qualifying individuals receive the Project Management Professional (PMP®) designation. To do so, such individuals must have work experience (approximately 5,000 hours) and pass an online exam that is based on the Project Management Body of Knowledge (PMBOK® Guide).

A professional association? Just for project management? Isn’t project management just a variant on general management?

Yes and no. There are a lot of similarities, but there are enough differences to justify treating project management as a discipline separate from general management. For one thing, projects are more schedule-intensive than most of the activities that general managers handle. And the people in a project team often don’t report directly to the project manager, whereas they do report to most general managers.

So just what is project management, and, for that matter, what is a project? PMI defines a project as “a temporary endeavor undertaken to create a unique product, service, or result” (PMBOK® Guide, PMI, 2013, p. 5). This means that a project is done only one time. If it is repetitive, it’s not a project. A project should have definite starting and ending points (time), a budget (cost), a clearly defined scope—or magnitude—of work to be done, and specific performance requirements that must be met. I say “should” because seldom does a project conform to the desired definition. These constraints on a project, by the way, are referred to throughout this book as the PCTS (performance, cost, time, scope) targets.

PMI defines a project as “a temporary endeavor undertaken to produce a unique product, service, or result.”

Dr. J. M. Juran, the late quality management guru, also defines a project as a problem scheduled for solution. I like this definition because it reminds me that every project is conducted to solve some kind of problem for a company. However, I must caution that the word “problem” typically has a negative meaning, and projects deal with both positive and negative kinds of problems. For example, developing a new product is a problem but a positive one, while an environmental cleanup project deals with a negative kind of problem.

“A project is a problem scheduled for solution.”

—J. M. JURAN

Project Failures

Current studies indicate mixed results regarding project management success rates. The Standish Group’s recent Chaos report, with a focus on software development projects, indicates a 29 percent success rate, with 52 percent challenged, and 19 percent failed. It should be noted that success factors have been “modernized” to mean on time, on budget, and with a satisfactory result. The success rate is virtually unchanged from the 2011 report. Standish does emphasize that smaller projects have a much higher success rate than larger ones. Gartner, an IT research and advisory company, echoed these findings with recent reports that larger projects (those with budgets exceeding $1 million) have higher failure rates, hovering around 28 percent.

Most telling were the data recently reported by the Project Management Institute. PMI consistently measures the state of project, program, and portfolio management. Their 2015 “Pulse of the Profession” study reveals some positive trends but also indicates the percentage of projects meeting their goals has remained flat at 64 percent since 2012. To effect improvement, PMI suggests that organizations go back to fundamentals. The three basic areas cited are:

1.Culture. Work to create a project management mind-set.

2.Talent. Focus on talent management, continuous training, and formal knowledge transfer.

3.Process. Support project management through the establishment and adoption of standardized project practices and processes.

My own survey, based on 28 years of project management, best practice identification, project consulting, and training, reveals that the more things change, the more they stay the same. Not enough planning is being accomplished. Large or small, software, R&D, or administrative, successful projects rely on good planning. Too many project managers take a ready-fire-aim approach in an attempt to complete a project quickly. Many organizations do not allow project managers significant planning time or virtually any time at all. This often results in spending far more time and effort reworking errors, soothing unhappy stakeholders, and backing out of blind alleys. In short, the lack of adequate planning causes projects to fail.

The PMI survey states that “it is time for organizations to revisit the fundamentals of project management and, essentially, go back to the basics” (p. 4). I could not agree more. You, the reader, must lay your foundation and understand the basics presented here to ensure improvement and success as you move forward and manage your projects.

What Is Project Management?

The PMBOK® Guide definition of project management is the “application of knowledge, skills, tools, and techniques to project activities to meet the project requirements. Project management is accomplished through the application and integration of the 47 logically grouped project management processes comprising the 5 Process Groups: initiating, planning, executing, monitoring and controlling, and closing” (PMBOK® Guide, PMI, 2013, p. 6).

“Project management is the application of knowledge, skills, tools, and techniques to project activities to achieve project requirements. Project management is accomplished through the application and integration of the project management processes of initiating, planning, executing, monitoring and controlling, and closing.”

—PMBOK® Guide

The new PMBOK® Guide has added five new project management processes:

1.Plan Scope Management

2.Plan Schedule Management

3.Plan Cost Management

4.Plan Stakeholder Management

5.Control Stakeholder Management

This change emphasizes the requirement for the project team to plan prior to managing. The processes Plan Stakeholder Management and Control Stakeholder Engagement have been added to coincide with the addition of Project Stakeholder Management as the new (tenth) knowledge area (see page 22). This new knowledge area highlights the importance of appropriately engaging project stakeholders in key decisions and activities.

Project requirements include the PCTS targets mentioned previously. The various processes of initiating, planning, and so on are addressed later in this chapter, and the bulk of this book is devoted to explaining how these processes are accomplished.

It would be better if the PMBOK® Guide specified that a project manager should facilitate planning. One mistake made by inexperienced project managers is to plan the projects for their teams. Not only do they get no buy-in to their plans, but their plans are usually full of holes. Managers can’t think of everything, their estimates of task durations are wrong, and everything falls apart after the projects are started. The first rule of project management is that the people who must do the work should help plan it.

The first rule of project management is that the people who must do the work should help plan it.

The role of the project manager is that of an enabler. Her job is to help the team get the work completed, to “run interference” for the team, to get scarce resources that team members need, and to buffer them from outside forces that would disrupt the work. She is not a project czar. She should be—above all else—a leader, in the truest sense of the word.

The best definition of leadership that I have found is the one by Vance Packard, in his book The Pyramid Climbers (Crest Books, 1962). He says, “Leadership is the art of getting others to want to do something that you believe should be done.” The operative word here is “want.” Dictators get others to do things that they want done. So do guards who supervise prison work teams. But a leader gets people to want to do the work, and that is a significant difference.

“Leadership is the art of getting others to want to do something that you believe should be done.”

—VANCE PACKARD

The planning, scheduling, and control of work represent the management or administrative parts of the job. But, without leadership, projects tend to just satisfy bare minimum requirements. With leadership, they can exceed those bare minimums. I offer a comprehensive application of project leadership techniques in Chapter 14.

It Is Not Just Scheduling!

One of the common misconceptions about project management is that it is just scheduling. At last report, Microsoft had sold a huge number of copies of Microsoft Project®, yet the project failure rate remains high. Scheduling is certainly a major tool used to manage projects, but it is not nearly as important as developing a shared understanding of what the project is supposed to accomplish or constructing a good work breakdown structure (WBS) to identify all the work to be done (I discuss the WBS in Chapter 7). In fact, without practicing good project management, the only thing a detailed schedule is going to do is allow you to document your failures with great precision!

I do want to make one point about scheduling software. It doesn’t matter too much which package you select, as they all have strong and weak points. However, the tendency is to give people the software and expect them to learn how to use it without any training. This simply does not work. The features of scheduling software are such that most people don’t learn the subtleties by themselves. They don’t have the time because they are trying to do their regular jobs, and not everyone is good at self-paced learning. You wouldn’t hire a green person to run a complex machine in a factory and put him to work without training because you know he will destroy something or injure himself. So why do it with software?

The Accidental Project Manager

Have you been suddenly thrust into the role of managing a project without the title “project manager” or much support? Did you consider yourself the project manager and the project team? You are not alone. Increasingly, individuals are managing work t...