Skip to content
Ops for Law

Ops for Law

Law Practice Operations

  • About
  • Disciplines
  • Contact
  • Operations Fundamentals
  • Lean
  • Project Management
  • Six Sigma
  • Theory of Constraints

Project Management

Project management is a collection of tools and processes for the management of “projects.” The word “project” has a very general colloquial meaning – it just means something that needs to be done. What is a “project” in the sense used in management science?​

Work is managed by different methods based mainly upon the novelty to the producer. Novelty can be imagined on a spectrum, with complete lack of novelty at the left, complete novelty at the right, and a gradient between.​

At the left end with the least novelty is volume production, in which a set group of people execute a set series of processes to produce a consistent output. For example, manufacturing ball bearings brings little novelty; the only variability is that intrinsic in the raw materials (such as their metallic composition) and in the operation of processing machines (such as tolerances, temperatures, and state of wear). The main management challenge of volume production is to manage cost, which is expected to be low relative to the production undertaken at lower volumes. In operations terms, the work involved in volume production is “routine work.”​

At the right end of the management spectrum with the greatest novelty are “projects.” In management terms, a “project” is a task that is so novel that one of the main management challenges is to address the novelty. The classic example of a “project” involves a task done only once, and so novel that it is uncertain as to what is to be done, who is going to do it, how long it will take, and what it will cost. Designing and constructing a unique office building is a project in this sense.​

We note four points in thinking of work as routine or as a project.​

First, work that is routine in the management sense (and hence not a project) may be complex and may involve uncertainty. Heart transplantation is routine work in the management sense; a fixed team executes known procedures. The condition of an individual patient is incalculably variable, but the team is trained to address these variations. The same people execute the same (complex) procedures in a known sequence over a reasonably predictable time and at a reasonably estimable cost. While unexpected things will happen that may make the procedure for a given patient far from “routine,” the management challenges are nonetheless those of routine work (rather than project work). Some would refer to treatment of an individual heart patient as a “case,” denoting routine work that by its nature may still follow a unique course. The substantive complexity and uncertain course of legal work do not in themselves make legal work a project in the management sense.​

Second, the classification of work is relative; routine work for one producer may be totally novel (and hence a project) for another. If one not in the business of making ball bearings is asked to make one ball bearing, that producer must undertake a project to make the ball bearing. Who will do what when and at what price to make this ball bearing? These unknowns must become known and then implemented. Making the first ball bearing is a project for management purposes. Once a ball bearing plant is created, its ongoing operation will become routine work.​

Third, most any project will embed routine work. In building a house, project management methods are used to scope, price, and schedule the electrical work for this unique project. But for the electrician who arrives to wire the kitchen, the work is routine. Project management does not inform the electrician how to best do the specified work; this function is left to other disciplines used to manage and improve routine work. Project management organizes resources to a task; for legal work, it is about who will accomplish what when and at what cost for this novel task. It is not about how the work will be done. How the necessary routine work is done is a general operations and process improvement question. Project management may estimate the cost and timing of a deposition; project management is not about how to take a deposition well.​

Fourth, some work will fall in the middle zone of the novelty spectrum and hence be open as to whether it is regarded as a “project” or “routine.” Sometimes work that is fairly routine but which needs cost and schedule tracking can benefit from project management techniques (drawing in these more routine tasks is called “management by project”). Don’t be put off by the nomenclature, but master the point that the goal of project management is to address the novelty of an effort.

Project Management in Legal Work

Of the five operations disciplines we find most useful in legal work, project management has received the most legal industry attention. “Legal project management” includes the application of project management methods to legal work. This application first arose from client requests that they receive estimates or budgets of the costs that will arise in complex litigation cases. In order to estimate or budget for a complex case, one needs a method to organize consideration of what work is to be done, who is to do it, and at what cost. Project management has tools and methods for making these determinations. Hence, project management initially appeared as a budgeting tool. It remains primarily so, but once one has done the work to prepare a budget, the same information can be used to assign and schedule the work. Legal project management is moving into these functions as well.

​Legal Project Management is sometimes used to describe any method by which legal work can be done faster, better, or cheaper. This broad net draws in process improvement methods that are actually used for the improvement of routine work. Project management manages the respects in which work varies from one project to another; it is not designed for the improvement of the respects in which work is the same from one project to another.​

History of Project Management

Since the beginning of civilization, people have undertaken projects. The Egyptian Pyramids, the Gothic Cathedrals of Europe, all significant military campaigns, and every Thanksgiving dinner prepared in a home were projects in the modern sense. The methods by which these projects occurred were all project management methods, but they were long associated with their application – such as construction methods and military methods – rather than as part of a separate field of study.​

Beginning in the early 20th century, project management began to take form as an independent discipline. The development of project management started with the development of tools. The Gannt Chart (a chart for ordering and scheduling work) was invented around 1910; in the 1950s, the U.S. Department of Defense, with the help of Booz-Allen & Hamilton, developed the “Project Evaluation and Review Technique” method of representing project events through a diagram; and about the same time DuPont developed the “Critical Path Method” of graphic project representation. Modern iterations of these tools are in common use today.​

The use of specialized tools drew attention to the benefits of using systematic and formal approaches to managing projects. As organizations began to distinguish between their routine activities and projects (e.g., to upgrade the accounting system, to introduce a new product, to merge with another organization, etc.), processes developed around the use of the tools and for the management of other aspects of project life cycle. In 1969, the Project Management Institute (known as “PMI”) was founded. As the leading association of project management professionals, PMI has established a globally-shared lexicon of project management tools and processes. There are now over 400,000 PMI members in over 171 countries.

Key Concepts

Critical Path

The longest duration path of dependent activities in a network diagram. This path determines the anticipated shortest time within which the project can be completed. If any activity on the critical path takes longer than planned, the completion of the project will be delayed. If the rolls are to be fresh from the oven for dinner, and they must be baked for twenty minutes at 350 degrees, then if they are put in the oven ten minutes late, the entire dinner will be delayed by ten minutes. The baking of rolls is on the critical path. Critical path is a useful general concept; whatever part of a project or of routine work is pushing out the time of completion is on the critical path, and it must be done next.

Deliverable

Tangible or intangible major components of a project. Each deliverable represents the sum of a more detailed set of activities. A deliverable in a legal matter might be a draft set of documents for client review or a completed deposition of a potential witness.

Gantt Chart

A scheduling tool that displays project activities as horizontal bars on a time scale. The Gantt chart makes it easy to see when activities are scheduled, but does not depict dependency relationships concretely (if activity A must be performed for activity B to occur, we say that activity B is “dependent” upon activity A). Dependent activities can be executed only in a series, whereas activities that are not dependent can be executed in parallel.

Network Diagram

A tool for visually representing the time-sequence of activities required to complete a project. The diagram shows the sequential and concurrent relationships among activities in a project, including their dependencies. Network diagrams are not unique to projects, and are also used to study routine work.

Project

A temporary endeavor intended to solve a problem, seize an opportunity, or respond to a mandate. Some projects create or change processes, products or services, while others spawn events, product information or tackle crises. Projects differ from the routine activities. Serving coffee and tea at Starbucks is a routine activity. Building a new Starbucks is a project.

Triple Constraint

The interdependency between the three key metrics of a project: time, budget (cost), and scope. Scope (or performance) is defined as the desired qualities of the specified output – size, quality, materials, and the like. Schedule is the time required to complete the work, and budget refers to the cost of resources required to deliver the specified output. Changes in any one of these will impact the others. For example, if the project must be completed earlier than anticipated, doing so will likely require higher costs or the relaxation of the scope of the project. This is a useful concept that applies to routine work as well as to projects; when designing a process by which a routine legal task is performed, considerations of time, cost, and quality always compete.

Work Breakdown Structure

(“WBS”): A hierarchical decomposition of a project into its component tasks, organized as an outline or tree diagram. The WBS organizes and defines the total scope of the project, answering the question: What are all the actions that will be required to make the project happen? At the highest level, WBS is the project; at the lowest level, it is the “work package.” A work package is a subset of the project that can be scheduled, cost estimated, monitored, and controlled. A WBS is a breakdown only to the level such that work can be managed. A further breakdown to minute detail is necessary to analyze and improve the details of how routine work is done.​

Resources

Brown, Karen and Hyer, Nancy Lea, Managing Projects: A Team-Based Approach (Chicago: McGraw-Hill, 2010).

Lewis, Bob. Bare Bones Project Management: What You Can’t Not Do (IS Survivor Publishing, 2006).​

Cook, Curtis. Just Enough Project Management (New York: McGraw Hill, 2005)​

www.pmi.org (Project Management Institute)

  • About
  • Disciplines
  • Contact
  • Operations Fundamentals
  • Lean
  • Project Management
  • Six Sigma
  • Theory of Constraints