Part 1 Project
Management
Discipline

Chapter 1 Introduction to Project Management

Most organizations rely on a variety of projects, both large and small. Although small projects have unique challenges that are not present in large projects, small projects can still benefit from a defined project management methodology. To achieve maximum benefits, the process, tools, and techniques must be scalable and adaptable. The more successful you are with managing small projects, the more opportunities you will have to obtain larger projects.

Almost everyone, to some degree, is involved with projects and should be prepared to manage them effectively. Project Management for Small Projects suggests an approach that allows the project manager to apply structure and discipline to managing small projects while balancing the needs of the project with the project management methodology.

PROJECT OVERVIEW

Projects are a more important part of business now than they ever have been. They exist at all levels of every organization and must be managed proactively, regardless of size. Normally when we think of projects, we think of large initiatives such as developing a new product or service, developing a new information system or enhancing an existing one, constructing a building, or preparing for a major sports event. Small projects are not always viewed as projects and therefore are not always treated as projects—especially smaller, more informal projects, which are often called assignments.

Definition of a Project

As stated in the PMBOK® Guide, Fifth Edition, a project is a temporary endeavor undertaken to create a unique product, service, or result. A project can create:

• A product that can be a component of another item, an enhanced item, or an end item in itself

• A service or a capability to perform a service

• A result, such as an outcome or document.

A project has three distinct characteristics.

1. A project is temporary in that it has a beginning and an end. A project always has a defined start and end date. The project begins with a statement of work or some form of description of the product, service, or result to be supplied by the project, and it ends when the objectives are complete or it is determined that the objectives cannot be met and the project is canceled.

2. A project is unique in that the product, service, or result created as a result of the project is different in some distinguishing way from all similar products, services, or results. Unique also indicates that although a project might appear to be similar to another project because you are producing the same type of deliverable, it really is not. In both projects you are creating something that did not exist before. Even a revision to an existing deliverable is considered unique because the revised product is something that did not exist before.

3. A project is characterized by progressive elaboration. This means the project develops in steps and grows in detail. Progressive elaboration is continually improving and detailing a plan as more detailed and specific information and more accurate estimates become available as the project progresses. When you are first given a project, you have limited information to work with, usually in the form of a high-level project description, the project objective, and some assumptions and constraints. The scope might need to be further defined, and the work activities for the project need will have to be planned in detail as more specific information becomes available. Progressive elaboration allows you to manage to a greater amount of detail as the project evolves.

Another way to view a project is to see a project as something we do one time, as opposed to operational work, which is continuous and repetitive and is undertaken to sustain the business. Operational activities have no real completion date; they are ongoing. An example of a project would be to develop or enhance an accounting system. The operational activity would be to process biweekly payroll or pay monthly expenses. Both operational activities and projects are constrained by resources and are planned, executed, and controlled (Figure 1.1). However, projects, due to their temporary nature, are initiated and closed.

FIGURE 1.1 Comparison of Projects and Operations

Projects can intersect with operations:

• When developing a new product or result for an existing system

• While developing new or enhancing existing procedures

• When a project is completed and transferred to operations.

Definition of a Small Project

Small projects are perceived to be relatively easy, but other than this there is no one way to define when a project is a small project. In some cases small could be defined on the basis of cost, such as costing less than $1 million. Cost is relative, however, and depends on the income of the organization. Small could also be defined by time, for example, taking less than six months to complete. For the purpose of this book, we will use the following guidelines to define small projects. A small project generally:

• Is short in duration, typically lasting less than six months, and usually part-time in effort hours

• Has 10 or fewer team members

• Involves a small number of skill areas

• Has a single objective and a solution that is readily achievable

• Has a narrowly defined scope and definition

• Affects a single business unit and has a single decision-maker

• Has access to project information and will not require automated solutions from external project sources

• Uses the project manager as the primary source for leadership and decision-making

• Has no political implications with respect to proceeding or not proceeding

• Produces straightforward deliverables with few interdependencies among skill areas

• Costs less than $75,000 and has available funding.

If the project involves a few skill areas but the deliverables are complex, it is not a small project. If the scope is broad, the project usually involves more skill areas, so it would not be considered a small project. The more skill areas involved, the more effort will be required to manage the project.

A small project can be a portion of a larger project. For example, if a team lead is responsible for planning and controlling specific project activities and then reporting results to the project manager, the team lead is, in effect, running a small project. Most small projects center on changes in organizational processes or enhancements to existing systems. Other examples of small projects include:

• Developing a training course

• Implementing a project office

• Implementing a purchased software application

• Enhancing an existing information system

• Developing a website

• Evaluating an existing practice

• Developing a strategy

• Developing a project proposal.

The following are detailed descriptions of two small projects.

A small project can also be part of a program. (Refer to Chapter 12 for a discussion on Projects as Part of a Program.)

Definition of a Simple Project

This book differentiates between small and simple projects. Many of the best practices for small projects and simple projects are similar. When small projects and simple projects require different approaches, this book explains where and how.

Simple projects are even more straightforward than small projects. Simple projects are often called assignments. We usually do not think of assignments as projects, but assignments, like projects, have a definite beginning and end and produce a unique output. Assignments are usually short in duration and are completed by a small team consisting of three or fewer team members. Often only one person completes an assignment. (Refer to Chapter 13, The Power of One, for more details on one-person assignments.)

Because we do not think of assignments as projects, we do not treat them as projects. Assignments, because of their size and duration, do not need all the formality required by projects; however, they can still benefit from a simplified form of project management. Treating assignments as projects provides you with the opportunity to clearly define expectations, better use resources, and eliminate the frustration of wasted effort and unnecessary rework.

Examples of simple projects include:

• Developing procedures or a reference guide

• Revising a business process

• Developing an electronic filing system to store departmental documents

• Developing a presentation to communicate a new process

The factors that distinguish a small project from a simple project are duration, team size, and degree of formality required to effectively meet stakeholders’ expectations. The project manager must determine what combination of processes and tools fits the needs of the project.

WHAT IS PROJECT MANAGEMENT?

Project management is the application of knowledge, skills, tools, and techniques to meet project requirements. It includes identifying requirements for the project, defining and planning the necessary work, scheduling the activities to complete the work, monitoring and controlling project activities, communicating project progress among project stakeholders, and finally conducting activities to end the project.

Project management involves coordinating the work of other people. A project manager and a project team are involved in the project. The project manager is the person assigned by the organization to achieve the project objectives. Project manager might not be the person’s formal job title, but for the purpose of this book we will use the term for the person responsible for completing the project. The project team members are the people responsible for performing project work. They complete the project deliverables. They might or might not report directly to the project manager. For small projects team members usually work part-time on the project.

Is project management an art or a science? It is both.

Project management is an art because of the human element. The involvement of interrelationships among diverse groups requires the use of leadership skills, which are applied on the basis of the project situation and are unique to each project. Some of these skills are communicating, negotiating, decision-making, and problem-solving. The art of project management requires the project manager to gain agreement between technical and business resources, the project team and the customer, and multiple stakeholders. (Stakeholders are people and organizations that are actively involved in the project or whose interests might be positively or negatively affected as a result of project execution or project completion.) To effectively master the art of project management, you must have a degree of proficiency with the science of project management

Project management is a science because it is based on repeatable processes and techniques. The project manager has an array of tools, templates, and standards to assist with planning a project. In addition, the project manager has an assortment of metrics and status reports for monitoring and controlling a project. Mastering the science of project management is dependent on the effectiveness and efficiency of applying the appropriate project management processes and techniques.

It’s been said that project managers spend about 75 to 80 percent of their time on the art of project management and 20 to 25 percent of their time on the science.

THE VALUE OF USING PROJECT MANAGEMENT ON SMALL PROJECTS

For larger projects, success is measured by product and project quality, timeliness, budget compliance, and degree of satisfaction. Larger projects must balance competing project constraints, including scope, quality, schedule, budget, resources, and risk. However, for small projects, success can be defined as on time, within budget, and meeting the requirements of the project stakeholders. Managers of small projects need to be concerned with meeting this triple constraint, with an understanding that other project constraints may also need to be managed.

The value project management offers is the use of standard processes and tools. Project management is even more valuable when the processes and tools can be tailored to fit the different types and sizes of small projects. By using a methodology, the project manager is more prepared to define and manage the project scope, obtain project requirements, and provide ongoing communications. Stakeholders are engaged early and expectations are known. Add to this the ability to produce realistic estimates and schedules, and to effectively manage issues and risks, and you have a means of managing project constraints. When you can manage project constraints, you improve your chances for project success.

Finally, using project management on small projects will provide models for future projects. Most small projects tend to be similar in structure or outcome. If a template or model is developed, it can be used for future projects. This saves the project manager time and provides a basis for continuous process improvement.