Skip to content
    Delivery & qualityChapter 17

    Project and Product Management

    How to distinguish a project, product, and process and choose a management approach that fits the uncertainty and outcome.

    Book summaryworking40 minevolving · reviewed Aug 13, 2026
    Tech Lead
    Engineering Manager
    Chapter outline

    The Art of Project Management

    Authors: Scott Berkun
    Publisher: O'Reilly Media; Питер (русское издание)
    Length:

    How to distinguish a project, product, and process and choose a management approach that fits the uncertainty and outcome.

    The Art of Project Management — original coverOriginal
    The Art of Project Management — translated coverTranslation

    Brief

    The essential idea

    Projects, products, and processes are different operating modes. A project is a temporary initiative with a unique outcome and constraints; a product continuously learns and creates value through hypotheses and iterations; a process is repeatable activity optimized for stability, execution quality, and efficiency.

    The management system must match the mode. Projects benefit from baselines, change control, stages, risks, and frameworks such as PMI/PMBOK, IPMA, or PRINCE2; products need stable teams, variable scope, discovery-delivery-learning loops, and outcome measures; processes need explicit flow, SLA, variation control, and operational feedback into strategy.

    Decision lens

    Key takeaways

    Project, product, and process are distinct management modes, not interchangeable labels.

    Projects optimize a bounded delivery against constraints; products optimize continuing value and learning.

    In product work, time and team are often fixed while scope changes as evidence arrives.

    The higher the uncertainty, the more valuable short feedback loops and adaptive control become.

    Programs coordinate related projects, while portfolios allocate investment against strategic priorities.

    Treating a product as a fixed-scope project creates brittle plans, output metrics, and conflict over expectations.

    Workplace experiment

    Apply it at work

    1. 1

      Classify the initiative as a project, product, or process using its end date, team model, planning style, delivery pattern, and success criterion.

    2. 2

      For a project, define the baseline, change-control rules, stages, stakeholders, and risk checkpoints.

    3. 3

      For a product, express goals as user value and create a discovery-to-delivery-to-learning loop.

    4. 4

      Select metrics that fit the mode and review whether the initiative has evolved into a different mode.

    Choose one action, define the observable effect, and keep the first test small enough to reverse.

    Evidence

    Sources and further reading

    Additional sources

    Channel, aggregator, and commentary links confirm the work; they are not the primary source.

    Previous chapterSquad Health Check Compared with DORA, SPACE, and DevExNext chapterMaking Work Visible — Short Summary