pith. sign in

arxiv: 2607.01562 · v1 · pith:GSXBYZA7new · submitted 2026-07-02 · 💻 cs.SE

A Capacity-Aware Parr Model for Agile Projects

Pedro E. Colla This is my paper

Pith reviewed 2026-07-03 00:30 UTC · model grok-4.3

classification 💻 cs.SE
keywords Parr modelagile projectseffort forecastingcapacity awaresoftware project managementScrumeffort distributionproject completion prediction
0
0 comments X

The pith

A normalized Parr curve overlaid on actual team capacity forecasts agile project completion and resource gaps without assuming fixed activity paths.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The paper refactors the classical Parr effort distribution model into a capacity-aware version suited to agile settings where team size is fixed or externally constrained. It treats the Parr shape as a latent effort demand curve that is then combined with the observed or planned capacity trajectory to generate forecasts of progress, completion time, deficit, and slack. This approach deliberately avoids modeling changes in internal activity paths when resources are limited. Calibration uses ordinary Scrum records and includes a rolling-origin validation against simple baselines.

Core claim

A normalized Parr shaped latent effort demand is combined with an observed or planned capacity trajectory. The resulting model forecasts aggregate progress, completion time, capacity deficit, and capacity slack without assuming that the same internal activity path is followed under resource restriction. The model uses a small parameter set including total effort K, a Parr shape parameter, an origin constant c, and the capacity trajectory, with a discrete sprint formulation and calibration from Scrum records.

What carries the argument

The normalized Parr-shaped latent effort demand overlaid with an observed capacity trajectory, which serves as the forecasting layer that separates latent work distribution from actual staffing constraints.

If this is right

  • Aggregate forecasts of progress and completion become possible from standard Scrum data without detailed task-level activity modeling.
  • Capacity deficit and slack can be quantified directly from the mismatch between the latent curve and the capacity trajectory.
  • A discrete formulation supports sprint-by-sprint updates and rolling validation against management baselines.
  • The model remains compact, requiring only total effort, shape parameter, origin offset, and capacity data.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • Teams could use early capacity mismatches to adjust scope or staffing before completion dates slip.
  • If the Parr shape holds across multiple projects, the same latent curve might serve as a reusable template for similar agile initiatives.
  • The approach might extend to other effort-distribution families if Parr proves insufficient for certain project types.

Load-bearing premise

A normalized Parr-shaped latent effort demand remains a valid description of required work even when actual staffing deviates from the unconstrained curve.

What would settle it

In a set of completed agile projects with constrained capacity, the actual cumulative effort distribution deviates from the normalized Parr shape in a way that causes the overlay model to produce completion-time errors larger than those from a simple linear burn-down baseline.

Figures

Figures reproduced from arXiv: 2607.01562 by Pedro E. Colla.

Figure 1
Figure 1. Figure 1: Comparison effort forecast vs. actual [PITH_FULL_IMAGE:figures/full_fig_p007_1.png] view at source ↗
Figure 2
Figure 2. Figure 2: Evaluated RMS as a percent between actual and forecasted effort [PITH_FULL_IMAGE:figures/full_fig_p007_2.png] view at source ↗
Figure 3
Figure 3. Figure 3: Sensitivity of the forecasted effort to variations in the model [PITH_FULL_IMAGE:figures/full_fig_p008_3.png] view at source ↗
Figure 4
Figure 4. Figure 4: Sensitivity of the forecasted effort to the capacity and variations in [PITH_FULL_IMAGE:figures/full_fig_p008_4.png] view at source ↗
read the original abstract

Classical software effort distribution models, including the PNR family and Parr alter native curve, were designed to describe the time distribution of development effort under an implied staffing pattern. Their direct use in agile environments is limited when team capacity is fixed, partially fixed, or externally constrained, the original curve may prescribe a staff demand that the organization cannot allocate. This paper proposes a compact refactoring of Parr model as a capacity-aware forecasting layer for agile projects. The contribution is deliberately narrower than a full causal theory of project dynamics. A normalized Parr shaped latent effort demand is combined with an observed or planned capacity trajectory. The resulting model forecasts aggregate progress, completion time, capacity deficit, and capacity slack without assuming that the same internal activity path is followed under resource restriction. The model uses a small parameter set such as total effort K, a Parr shape parameter, an origin constant c that can match nonzero initial staffing, and the capacity trajectory. A discrete sprint formulation is provided, together with a calibration method from ordinary Scrum records and a rolling origin validation protocol against simple management baselines.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

2 major / 1 minor

Summary. The paper proposes a capacity-aware refactoring of the Parr model as a forecasting layer for agile projects. A normalized Parr-shaped latent effort demand (with parameters total effort K, shape parameter, and origin constant c) is combined with an observed or planned capacity trajectory to produce forecasts of aggregate progress, completion time, capacity deficit, and slack. The approach includes a discrete sprint formulation, calibration from ordinary Scrum records, and a rolling-origin validation protocol, while explicitly disclaiming any assumption that the same internal activity path is followed under resource restriction.

Significance. If the invariance of the Parr shape under capacity constraints holds and is validated, the model would supply a compact, low-parameter forecasting method suited to agile settings where staffing is fixed or externally constrained. The practical calibration from Scrum records and the rolling validation protocol against management baselines are concrete strengths that could make the approach usable without requiring a full causal theory of project dynamics.

major comments (2)
  1. [Abstract] Abstract: The central construction normalizes a Parr-shaped latent effort demand and overlays it with a capacity trajectory to generate forecasts without assuming unchanged internal paths, yet supplies no derivation showing why the Parr form itself remains valid when realized staffing deviates from the unconstrained curve. This invariance is load-bearing for the forecasting claims but is presented without argument or test.
  2. [Abstract] Abstract: No derivation steps, data, error analysis, or validation results are provided, so the soundness of the forecasts (including whether they reduce to fitted parameters by construction) cannot be evaluated from the given text.
minor comments (1)
  1. The abstract mentions a discrete sprint formulation and calibration method but does not indicate where in the manuscript the explicit equations or pseudocode appear, which would aid readability.

Simulated Author's Rebuttal

2 responses · 0 unresolved

We thank the referee for the positive summary of the contribution and for the constructive major comments. We respond point by point below, clarifying that the model deliberately refrains from claiming invariance of the Parr shape under capacity constraints.

read point-by-point responses

  1. Referee: [Abstract] Abstract: The central construction normalizes a Parr-shaped latent effort demand and overlays it with a capacity trajectory to generate forecasts without assuming unchanged internal paths, yet supplies no derivation showing why the Parr form itself remains valid when realized staffing deviates from the unconstrained curve. This invariance is load-bearing for the forecasting claims but is presented without argument or test.

    Authors: The manuscript does not claim or rely on invariance of the Parr form under capacity constraints. The abstract states explicitly that forecasts are produced 'without assuming that the same internal activity path is followed under resource restriction.' The Parr shape is introduced solely as the functional form of the latent effort demand; the capacity trajectory is then overlaid as an independent constraint. Because no invariance is asserted, no derivation or test of invariance is required. The forecasting claims rest only on the combination of the two inputs. revision: no

  2. Referee: [Abstract] Abstract: No derivation steps, data, error analysis, or validation results are provided, so the soundness of the forecasts (including whether they reduce to fitted parameters by construction) cannot be evaluated from the given text.

    Authors: The quoted text is the abstract, which is written at a summary level. The full manuscript supplies the normalization derivation, the discrete sprint formulation, the calibration procedure from ordinary Scrum records, and the rolling-origin validation protocol together with error metrics against management baselines. These sections demonstrate that the forecasts incorporate the capacity trajectory explicitly and are not reducible to the fitted parameters alone. revision: no

Circularity Check

0 steps flagged

No circularity: model is an explicit overlay construction with stated assumptions

full rationale

The paper presents an explicit modeling choice: a normalized Parr-shaped latent demand (with parameters K, shape, c) is defined as an input assumption and then combined with an observed capacity trajectory to produce forecasts. No equation or step reduces a forecast quantity back to a fitted parameter by construction, nor does any load-bearing claim rest on self-citation, imported uniqueness theorems, or ansatz smuggling. The abstract explicitly narrows the contribution to this overlay without claiming to derive the Parr invariance from capacity data or internal paths. Calibration from Scrum records is described as a fitting procedure whose outputs are then used for forward projection, which is standard model usage rather than a circular redefinition. The derivation chain is therefore self-contained as a proposed refactoring rather than a tautological reduction.

Axiom & Free-Parameter Ledger

4 free parameters · 2 axioms · 0 invented entities

Abstract-only review; ledger populated from stated parameters and modeling choices. The central claim rests on the validity of the Parr shape as latent demand and the assumption that capacity overlay does not require re-deriving internal activity paths.

free parameters (4)
  • total effort K
    Core scale parameter of the Parr model, required to normalize the latent demand curve.
  • Parr shape parameter
    Controls the curvature of the latent effort demand; fitted or chosen to match project characteristics.
  • origin constant c
    Allows nonzero initial staffing; introduced to match observed starting conditions.
  • capacity trajectory
    Observed or planned staffing schedule used as external input to the overlay.
axioms (2)
  • domain assumption A normalized Parr-shaped curve remains a meaningful description of latent effort demand even under capacity constraints.
    Invoked when the paper states the model combines latent demand with capacity without assuming unchanged internal activity paths.
  • domain assumption Ordinary Scrum records contain sufficient information to calibrate the model parameters.
    Stated in the description of the calibration method.

pith-pipeline@v0.9.1-grok · 5702 in / 1515 out tokens · 22683 ms · 2026-07-03T00:30:04.799421+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Reference graph

Works this paper leans on

18 extracted references · 14 canonical work pages

  1. [1]

    B. W. Boehm,Software Engineering Economics. Englewood Cliffs, NJ, USA: Prentice-Hall, 1981

    1981

  2. [2]

    A general empirical solution to the macro software sizing and estimating problem,

    L. H. Putnam, “A general empirical solution to the macro software sizing and estimating problem,”IEEE Transactions on Software Engineering, vol. SE-4, no. 4, pp. 345–361, Jul. 1978, doi: 10.1109/TSE.1978.231521

    work page doi:10.1109/tse.1978.231521 1978

  3. [3]

    An alternative to the Rayleigh curve model for software de- velopment effort,

    F. N. Parr, “An alternative to the Rayleigh curve model for software de- velopment effort,”IEEE Transactions on Software Engineering, vol. SE- 6, no. 3, pp. 291–296, May 1980, doi: 10.1109/TSE.1980.230475

    work page doi:10.1109/tse.1980.230475 1980

  4. [4]

    Can the Parr curve help with manpower distribution and resource estimation problems?,

    V . R. Basili and J. N. Beane, “Can the Parr curve help with manpower distribution and resource estimation problems?,”Journal of Systems and Software, vol. 2, no. 1, pp. 59–69, 1981, doi: 10.1016/0164- 1212(81)90047-9

    work page doi:10.1016/0164- 1981

  5. [5]

    Schwaber and J

    K. Schwaber and J. Sutherland,The Scrum Guide: The Definitive Guide to Scrum: The Rules of the Game. Nov. 2020. [Online]. Available: https://scrumguides.org/scrum-guide.html

    2020

  6. [6]

    Cohn,Agile Estimating and Planning

    M. Cohn,Agile Estimating and Planning. Upper Saddle River, NJ, USA: Prentice Hall PTR, 2005

    2005

  7. [7]

    An update on effort estimation in agile software development: A systematic literature review,

    M. Fernandez-Diego, E. R. Mendez, F. Gonzalez-Ladron-de-Guevara, S. Abrahao, and E. Insfran, “An update on effort estimation in agile software development: A systematic literature review,”IEEE Access, vol. 8, pp. 166768–166800, 2020, doi: 10.1109/ACCESS.2020.3021664

    work page doi:10.1109/access.2020.3021664 2020

  8. [8]

    A systematic lit- erature review on reasons and approaches for accurate effort estimations in agile,

    J. Pasuksmit, P. Thongtanunam, and S. Karunasekera, “A systematic lit- erature review on reasons and approaches for accurate effort estimations in agile,”ACM Computing Surveys, vol. 56, no. 11, pp. 1–37, 2024, doi: 10.1145/3663365

    work page doi:10.1145/3663365 2024

  9. [9]

    Agile effort estimation: Have we solved the problem yet? Insights from a replication study,

    V . Tawosi, R. Moussa, and F. Sarro, “Agile effort estimation: Have we solved the problem yet? Insights from a replication study,”IEEE Transactions on Software Engineering, vol. 49, no. 4, pp. 2677–2697, Apr. 2023, doi: 10.1109/TSE.2022.3228739

    work page doi:10.1109/tse.2022.3228739 2023

  10. [10]

    Effort estimation in agile and DevOps: A systematic literature review of stakeholder dissatisfaction,

    S. A. Ruk, Y . Mahmood, A. Azmi, N. Firdaus Mohd Azmi, and S. Gul, “Effort estimation in agile and DevOps: A systematic literature review of stakeholder dissatisfaction,”IEEE Access, vol. 13, pp. 167925–167941, 2025, doi: 10.1109/ACCESS.2025.3600321

    work page doi:10.1109/access.2025.3600321 2025

  11. [11]

    Another systematic review? A critical analysis of systematic literature reviews on agile effort and cost estimation,

    H. Edison and N. Ali, “Another systematic review? A critical analysis of systematic literature reviews on agile effort and cost estimation,” arXiv:2601.20893, 2026. 10

    work page arXiv 2026

  12. [12]

    On the nature of the function expressive of the law of human mortality, and on a new mode of determining the value of life contingencies,

    B. Gompertz, “On the nature of the function expressive of the law of human mortality, and on a new mode of determining the value of life contingencies,”Philosophical Transactions of the Royal Society of London, vol. 115, pp. 513–583, 1825, doi: 10.1098/rstl.1825.0026

    work page doi:10.1098/rstl.1825.0026

  13. [13]

    A flexible growth function for empirical use,

    F. J. Richards, “A flexible growth function for empirical use,”Journal of Experimental Botany, vol. 10, no. 2, pp. 290–301, Jun. 1959, doi: 10.1093/jxb/10.2.290

    work page doi:10.1093/jxb/10.2.290 1959

  14. [14]

    A systematic review of soft- ware development cost estimation studies,

    M. Jørgensen and M. Shepperd, “A systematic review of soft- ware development cost estimation studies,”IEEE Transactions on Software Engineering, vol. 33, no. 1, pp. 33–53, Jan. 2007, doi: 10.1109/TSE.2007.256943

    work page doi:10.1109/tse.2007.256943 2007

  15. [15]

    Software development effort estima- tion: Formal models or expert judgment?,

    M. Jørgensen and B. W. Boehm, “Software development effort estima- tion: Formal models or expert judgment?,”IEEE Software, vol. 26, no. 2, pp. 14–19, Mar./Apr. 2009, doi: 10.1109/MS.2009.47

    work page doi:10.1109/ms.2009.47 2009

  16. [16]

    T. K. Abdel-Hamid and S. E. Madnick,Software Project Dynamics: An Integrated Approach. Englewood Cliffs, NJ, USA: Prentice-Hall, 1991

    1991

  17. [17]

    R. J. Madachy,Software Process Dynamics. Hoboken, NJ, USA: Wiley- IEEE Press, 2008, doi: 10.1002/9780470192719

    work page doi:10.1002/9780470192719 2008

  18. [18]

    ACM SIGSOFT empirical standards,

    P. Ralphet al., “ACM SIGSOFT empirical standards,” arXiv:2010.03525, 2020

    work page arXiv 2010