Good Practices

Good practices in project management are defined as methods, techniques, processes, and behavioral norms that have gained broad acceptance among practitioners because they increase the likelihood of achieving project objectives when applied with sound judgment in appropriate contexts.

This definition is deliberately cautious. Unlike a legal requirement, a good practice does not have to be followed on every project. Unlike a mathematical proof, it is not guaranteed to produce the same result in every setting. The term signals that experienced project professionals have repeatedly found value in a particular approach across a range of projects, and that a competent manager should at least consider it before tailoring it or setting it aside.

Good Practices: Summary of Key Topics

Good Practices Definition and Core Meaning

The good practices definition used in professional project management literature emphasizes general agreement rather than universal mandate.

A good practice is more than a personal habit. It is a structured way of working that has been tested, observed, and shared across enough projects to become a reasonable default. In PMI's lexicon, good practice means there is general agreement that the application of knowledge, skills, tools, or techniques can enhance the chance of success over many projects. That wording matters because it does not promise success on every project and it does not remove the need for professional judgment.

The core meaning also implies a collective dimension. Good practices are not private tricks. They become visible through communities of practice, professional associations, standards bodies, and repeated peer review. When a practice earns the label good, it has already survived scrutiny from people who understand that projects differ in size, complexity, industry, and risk tolerance.

Distinguishing Good Practices from Rules and Standards

A good practice sits between a vague idea and a binding rule. A standard such as a regulatory requirement is mandatory. A good practice is authoritative but not compulsory. A methodology such as PRINCE2 or Scrum provides a more complete set of integrated rules, roles, and artifacts. A good practice can be embedded inside a methodology, but it can also stand alone. This distinction helps project teams decide when to adopt, adapt, or reject a practice.

Why the Term Is Preferred in Project Management

Many other fields use the phrase best practice. Project management bodies often prefer good practice because projects are unique. What works best in one initiative may be mediocre in another. The word good avoids the false implication that there is a single optimal way to manage every project. It also aligns with tailoring, which is a central theme in modern project management frameworks.

Origins and Cross-Industry Context of Good Practices

The origins of good practices in management can be traced to quality improvement and operational reliability movements, though project management gave the term its own cautious meaning.

Manufacturing and quality pioneers showed that standardizing certain work methods could reduce defects and improve predictability. Aviation, medicine, and nuclear power built on that insight by introducing checklists and structured procedures. In those fields, the idea of a good practice often became a required protocol because the cost of failure was high and the environment was stable. Project management borrowed the idea but had to account for the fact that projects are temporary and unique. As a result, the profession adopted the term good practice rather than best practice to reflect that context matters more than in a factory or cockpit.

Military and government programs also influenced early project management. Large defense and aerospace initiatives needed common planning and control techniques to coordinate many contractors. Techniques such as work breakdown structures, earned value management, and configuration control emerged from that environment and later spread to commercial projects. These became recognized good practices because they repeatedly helped large, complex projects stay visible and controllable.

What Is Good Practices in Project Management?

In operational terms, good practices in project management are the shared habits and structured techniques that project teams use to reduce uncertainty, align expectations, and control delivery.

Examples include maintaining a risk register, preparing a project charter, holding regular status reviews, managing changes through a documented control process, and capturing lessons learned. None of these are mandatory in every organization, but they are so widely accepted that a project manager who ignores them without a clear reason is often seen as taking an unnecessary shortcut.

Good practices can be technical, such as using a work breakdown structure to decompose scope. They can also be behavioral, such as engaging stakeholders early and often. Some are visible in templates and reports. Others live in how people run meetings, make decisions, or escalate issues. This breadth is why the term is sometimes hard to define sharply, even though practitioners recognize it when they see it.

How Good Practices Appear Across the Project Lifecycle

At initiation, a good practice is defining the problem and expected benefits before committing resources. During planning, it is breaking work into manageable pieces and identifying dependencies. During execution, it is keeping people focused on agreed deliverables while managing new requests. In monitoring and controlling, it is comparing actual progress against a baseline and acting on variances. At closing, it is documenting what happened and handing over results cleanly. Each stage has its own set of recognized practices that support the project's overall performance.

Key Components and Characteristics of Good Practices

Understanding the key components of good practices helps project managers avoid treating them as empty slogans.

First, a good practice is generally accepted. It has been used in enough contexts to generate confidence. Second, it is repeatable. It can be described clearly enough that different teams can apply it in similar ways. Third, it is adaptable. It can be scaled up or simplified depending on project size and complexity. Fourth, it is evidence-informed. It may come from empirical results, lessons learned, or professional consensus, rather than a single opinion.

A practice also has two sides. There is the visible artifact or technique, such as a risk register or a burn-down chart. Then there is the underlying intent, such as continuing to identify and respond to uncertainty. Teams that copy the artifact without understanding the intent often get little benefit. That is a recurring failure mode in organizations that adopt project management templates without changing how decisions are made.

Categories of Good Practices

Good practices can be grouped into governance practices, delivery practices, and interpersonal practices. Governance practices include clear decision rights, stage gates, and change control. Delivery practices include scheduling, estimating, quality reviews, and performance measurement. Interpersonal practices include stakeholder communication, conflict resolution, and team development. These categories overlap, but the distinction helps because a project may be strong in one area and weak in another.

Good Practices and Organizational Context

No good practice exists in a vacuum. An organization's culture, maturity, and risk appetite determine whether a practice is useful, burdensome, or irrelevant. A formal change control board may be a good practice on a large infrastructure project but become friction on a small internal software update. This context dependence is not a weakness of the concept. It is the reason the phrase includes the word good rather than guaranteed.

Good Practices in PMBOK and PRINCE2

Within the PMBOK Guide, good practices in PMBOK are woven through process groups, knowledge areas, and principles as generally recognized ways of working that require tailoring.

The PMBOK Perspective

The sixth edition of the PMBOK Guide organized project management into five process groups and ten knowledge areas. In that structure, good practices appeared as the inputs, tools and techniques, and outputs described for each process. For example, the practice of identifying risks, analyzing their probability and impact, and planning responses was presented as a recognized approach for managing risk. The guide did not instruct every project to perform every process. Instead, it expected a project manager to determine which processes and practices were appropriate for the project at hand.

The seventh edition shifted from process-based rules to twelve project management principles. In this newer view, good practices are more explicitly tied to tailoring and value delivery. A practice is good when it supports principles such as stewardship, stakeholder engagement, risk management, and continuous improvement. This evolution is significant because it makes the reasoning behind a practice more important than the form.

The PRINCE2 Perspective

PRINCE2 describes itself as a structured project management method based on proven best practices. It uses seven principles, seven themes, and seven processes to create a controlled environment. Within PRINCE2, good practices include continued business justification, defined roles and responsibilities, managing by stages, and learning from experience. These are not optional suggestions inside the method. They form the minimum requirements for a PRINCE2 project. Still, PRINCE2 encourages tailoring, so even its mandatory principles can be adapted in how they are implemented.

The difference between PMBOK and PRINCE2 is not that one is right and the other wrong. PMBOK is a guide to the body of knowledge, while PRINCE2 is a prescriptive method. In both, good practices provide a reliable starting point that experienced practitioners then adjust to their environment.

Good Practices in Agile, Hybrid, and BVOP Environments

Agile frameworks contribute their own set of good practices in Agile delivery, many of which emphasize short feedback loops and empirical control.

Agile Good Practices

In Scrum, timeboxed sprints, daily standups, sprint reviews, and retrospectives are recognized practices that support inspection and adaptation. In Kanban, limiting work in progress and visualizing workflow are good practices for improving flow. Extreme Programming adds technical practices such as pair programming, test-driven development, and continuous integration. These practices are not mandated by an external authority, but they have become accepted because they work in many software development contexts.

Agile good practices often look different from predictive ones. A fixed risk register may be less important than a well-run retrospective where the team surfaces risks and decides what to do about them. The underlying goal remains the same: reduce uncertainty and deliver value. The form changes because the delivery rhythm is different.

Hybrid and Emerging Frameworks

Hybrid approaches mix predictive and Agile practices. A project may use a formal business case and charter at the start, then deliver in timeboxed iterations with a product backlog. The good practices from each side are blended rather than forced into a single mold. This is increasingly common in organizations that need both governance and adaptability.

Business Value-Oriented Project Management, or BVOPM, also contributes a value-focused perspective. It treats employee-created tools and open-source software as formal products and emphasizes cross-functional teams as a core success factor. In that context, good practices are those that reduce waste and connect daily work to business value rather than simply following a process for its own sake.

Purpose and Importance of Good Practices

The importance of good practices lies in their ability to create a shared baseline of professional behavior while leaving room for judgment.

When good practices are widely understood, teams spend less time debating basic mechanics and more time solving the actual problems of the project. A risk register, for example, gives people a familiar place to record and review threats. A change control process gives stakeholders a predictable way to evaluate new requests. A project charter gives a sponsor and project manager a common understanding of what was agreed. These small consistencies reduce cognitive load and make projects easier to govern.

Good practices also support organizational learning. When a company standardizes certain practices, it can compare outcomes across projects more easily. It can identify which practices add value in which situations. Over time, the organization refines its own body of good practices and passes those lessons to new project managers. Without that shared foundation, every project starts from scratch and repeats known mistakes.

Value Across the Project Lifecycle

At the beginning of a project, good practices help establish clarity. At the middle of a project, they help maintain control and adapt to changes. At the end, they help close work cleanly and capture knowledge. Their value is not glamorous. It comes from avoiding predictable failures such as scope creep, communication gaps, hidden risks, and uncontrolled changes. This is why experienced practitioners often describe good practices as boring but essential.

Key Insights on Good Practice Foundations

Shared Baseline of Behavior

A shared baseline of professional conduct gives teams consistent expectations without removing the discretion needed to respond to the specific conditions of each project.

Less Debate, More Progress

When risk registers, change control processes, and project charters become familiar routines, teams spend less cognitive effort on administrative mechanics and more on substantive project challenges.

Organizational Learning Over Time

Standardized practices enable an organization to compare results across projects, systematically refine its internal knowledge base, and transfer proven lessons to incoming project managers.

Good Practices vs Best Practices

The distinction between good practices vs best practices is more than semantics; it reflects a core assumption about project uniqueness.

A best practice implies that one method is superior to all others in a given situation. That may be true in regulated or highly stable domains. In project management, however, context changes constantly. A communication plan that works for a five-person co-located team may fail for a five-hundred-person multi-contractor program. Calling something a best practice can create pressure to copy it without question, even when local conditions differ.

A good practice, by contrast, is a strong candidate rather than a final answer. It says this approach has worked well in many similar settings, so consider it first. It invites tailoring. This distinction is especially important for project sponsors and executives who may expect a universal recipe. Practitioners often spend as much time explaining why a standard practice should be adapted as they do actually adapting it.

Why Some Fields Still Use Best Practices

Fields with high regulation and low variability, such as aviation maintenance or pharmaceutical manufacturing, can reasonably use the term best practice because the conditions are tightly controlled. Project management borrows from those fields but cannot always match their level of predictability. This is why professional bodies such as PMI deliberately move toward good practice language. It is not a sign of weakness. It is a recognition that managing a project involves navigating people, uncertainty, and trade-offs.

Common Misconceptions and Limitations of Good Practices

Several misconceptions about good practices cause project teams to misuse the concept or dismiss it too quickly.

One misconception is that good practices are mandatory. They are not. A good practice is a default option, not a compliance requirement. Another misconception is that following good practices guarantees success. No process can guarantee a positive outcome in a complex project. A third misconception is that good practices are static. In reality, they evolve as tools, technologies, and workplace norms change.

There is also a misconception that more good practices are always better. Teams sometimes stack practices on top of each other until the process becomes heavier than the work itself. That is often called process burden or zombie project management. The value of a good practice depends on whether it improves decision making or delivery, not on how many templates are filled in.

Limitations and When to Avoid a Good Practice

A good practice can be a poor choice when the project is highly unusual, when the team is experienced enough to use a better local approach, or when the practice creates a false sense of control. Overly detailed risk registers on a small exploratory project can bury important signals in noise. Formal stage gates can slow down an urgent response project. In these cases, the right decision may be to skip or simplify the practice. That is not rejecting project management. It is applying professional judgment.

Relationship to Other Project Management Concepts

Understanding the relationship to other project management concepts clarifies where good practices fit in the broader ecosystem.

A standard defines what should be done. A methodology defines how things are done in a specific integrated way. A tool or technique is a narrower mechanism, such as a Gantt chart or a Monte Carlo simulation. A good practice can be expressed through a standard, embedded in a methodology, or supported by a tool. For example, quantitative risk analysis is a technique, while the broader habit of regularly reviewing risk is a good practice.

Good practices are closely related to organizational process assets, which include policies, procedures, templates, and lessons learned. When a lesson learned shows that a certain approach improved outcomes, that approach may be promoted to a good practice within the organization. Tailoring is the process of deciding which good practices fit a specific project. Without tailoring, good practices can become blind compliance.

Good Practices and Project Governance

Governance bodies often rely on good practices to guide oversight. They may require a business case, a risk register, or status reports because those practices make project health visible. But governance should not confuse the presence of an artifact with effective management. A risk register that is never reviewed is not a good practice in action. The practice includes the recurring behavior, not just the document.

Evolution and Current Thinking on Good Practices

The evolution of good practices reflects a broader shift from rigid process compliance to principle-based and value-driven project management.

In early project management, the emphasis was often on standardized work breakdown structures, critical path schedules, and formal documentation. The underlying assumption was that if you followed the right steps, the project would succeed. Over time, practitioners learned that projects fail for human reasons too, such as poor stakeholder alignment, hidden risks, and weak sponsorship. This led to a more balanced view. Good practices became less about filling in forms and more about creating conditions for honest communication and timely decisions.

The recent rise of Agile has accelerated this evolution. Agile did not abandon good practices. It replaced some heavyweight practices with lighter ones and moved the focus from predictive control to empirical learning. A daily standup is a good practice, just as a weekly status report is. The difference is the frequency, the audience, and the learning loop. Current thinking accepts that multiple sets of good practices can coexist, and the most important skill is knowing when each applies.

Debates and Open Questions

There is still debate about whether some practices deserve to be called good at all. For example, detailed upfront planning remains valuable in construction and aerospace, but it is often seen as waste in exploratory software product development. Similarly, stage gates help mature organizations control investment, but they can frustrate teams that need rapid experimentation. These debates are healthy because they prevent any practice from hardening into dogma. The most current guidance, including PMBOK 7 and PRINCE2 7, emphasizes tailoring, co-creation, and value as the context in which good practices should be evaluated.

Key Takeaways on Evolving Good Practices

From Compliance to Principles

Good practice has evolved from enforcing rigid process compliance, standardized work breakdown structures, and formal documentation toward principle-based, value-driven project management that emphasizes adaptive delivery and measurable outcomes.

Human Factors Cause Failure

Project failures are now widely understood to stem as much from human dynamics as from technical shortcomings, with poor stakeholder alignment, hidden risks, and weak sponsorship among the most common causes; effective practice therefore prioritizes candid communication and timely decision-making.

Tailoring Practices to Context

Current guidance such as PMBOK 7 and PRINCE2 7 acknowledges that multiple sets of good practices can coexist, making contextual judgment the core skill, since detailed upfront planning suits construction and exploratory software work favors empirical learning.

Good Practices Explained: A Practical Summary

For practitioners seeking a single frame, good practices explained simply means using approaches that experienced professionals have found effective, while never surrendering judgment to the template.

Good practices are not guaranteed wins. They are accumulated wisdom made available for the next project. A project manager who understands the intent behind a risk register will use it as a tool for conversation, not as a weekly chore. A sponsor who understands the purpose of a business case will ask harder questions about value, not just read a formatted document. This is the real texture of the concept. It lives in the space between formal guidance and human judgment.

The most effective project environments treat good practices as a reusable toolkit, not a checklist of obligations. That attitude protects teams from both extremes: ignoring hard-won knowledge or obeying it thoughtlessly.