1.2.4: Defined Process vs Empirical Process

Agile Project Management · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    Read aloud

    How

    Speed: 1×
    Light up
    Highlight

    Symbols: Mulberry Symbols, © 2018–2026 Steve Lee, CC BY-SA 4.0 (licence, the set), the site's own copies.

    From LibreTexts, under CC BY 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    1.2.4: Defined Process vs Empirical Process

    Agile and Empirical Process Control

    A defined process works best when the steps are clear, repeatable, and predictable. If you follow the process correctly, you can expect a consistent result. Manufacturing is often used as an example. If a machine is configured properly and the inputs are controlled, the output should be predictable.

    Agile is based on empirical process control: make the work visible, inspect frequently, and adapt based on learning. When the work is uncertain, the best plan is not a perfect prediction. The best plan is a system for learning quickly.

    To truly understand why Agile works, you must understand the difference between a defined process and an empirical process.

    To understand why Agile works, it helps to compare a defined process with an empirical process. A defined process works best when the steps are clear, repeatable, and predictable. If the process is followed correctly, the result should be consistent.

    Empirical Process Control

    Agile is based on empirical process control: make the work visible, inspect frequently, and adapt based on learning. When the work is uncertain, the best plan is not a perfect prediction. The best plan is a system for learning quickly.

    This works well when the work is stable, variation is low, and the outcome can be understood in advance.

    Defined Process vs. Empirical Process

    A defined process assumes that the work can be planned upfront. It depends on predictability and stability. Manufacturing is often used as an example: if the machine is configured correctly and the inputs are controlled, the output should be predictable.

    An empirical process is used when the work contains uncertainty and cannot be fully predicted at the beginning. Knowledge work, product development, and technology projects often involve unclear customer needs, changing requirements, technical risks, stakeholder disagreements, and shifting market conditions. In these environments, pretending that everything can be planned upfront creates false confidence.

    Transparency, Inspection, and Adaptation

    Empirical process control has three pillars: transparency, inspection, and adaptation. Transparency means the real state of the work is visible, including progress, problems, risks, and impediments. Inspection means the team frequently examines the product, process, and progress through reviews, demos, testing, retrospectives, backlog refinement, and customer feedback. Adaptation means the team changes direction based on what it learns.

    Key Takeaways
    • Transparency means the real state of the work is visible. The team, Product Owner, Scrum Master, stakeholders, and leaders should be able to see progress, problems, risks, and impediments. Without transparency, people make decisions based on fantasy instead of reality.
    • Inspection means the team frequently examines the product, process, and progress. Reviews, demos, retrospectives, backlog refinement, testing, and customer feedback all support inspection. Inspection helps the team discover whether it is building the right thing in the right way.
    • Adaptation means the team changes direction based on what it learns. Adaptation may involve reprioritizing the backlog, changing a design, improving team practices, adjusting release expectations, or removing an impediment.

    A simple way to remember this is: a defined process says, “Plan the work, then follow the plan.” An empirical process says, “Make the work visible, inspect frequently, and adapt based on learning.” For PMI-ACP, when a question includes uncertainty, changing requirements, unclear customer needs, or experimental product development, the best answer usually reflects empirical thinking.


    This page titled 1.2.4: Defined Process vs Empirical Process was last modified on Sun, 07 Jun 2026 23:29:22 GMT and is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Guharaman Janakiraman.