pith. sign in

arxiv: 2604.22003 · v1 · submitted 2026-04-23 · 💻 cs.SE

Documentless Assessments Using Nominal Group Interviews

Pith reviewed 2026-05-09 21:00 UTC · model grok-4.3

classification 💻 cs.SE
keywords documentless assessmentnominal group interviewagile practicesCMMIPlanning Pokeruser storiesprocess assessmentcollaboration
0
0 comments X

The pith

A nominal group interview technique enables documentless process assessments while encouraging collaboration among participants.

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

The paper introduces a group interview method for assessing processes without relying on documents. It combines nominal group techniques with agile software development ideas, using user stories to translate abstract practices into specific terms and Planning Poker for gathering and verifying information. This approach was applied in a single consulting project, where it helped participants who had been in disagreement to discuss and align on the key issues. Such a method could make assessments more accessible in situations where documents are unavailable or incomplete.

Core claim

The author establishes that documentless process assessments can be supported by a group interview technique that promotes collaboration, achieved by adapting user stories to represent CMMI specific practices and employing Planning Poker for fact finding and corroboration rather than traditional document reviews and audit-like interviews, as shown by its successful use in one consulting assignment where previously discording participants began talking to each other and agreeing on the issues.

What carries the argument

The adapted nominal group interview process that uses user stories to make CMMI practices concrete and Planning Poker for fact finding and corroboration.

If this is right

  • Assessments can proceed without access to or review of project documents.
  • Participants shift from discord to discussion and mutual agreement on issues.
  • Specific practices from process models such as CMMI become concrete through formulation as user stories.
  • Planning Poker serves as a structured alternative to audit-style interviews for gathering and verifying facts.

Where Pith is reading between the lines

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

  • The method could reduce reliance on formal documentation in small teams or early-stage projects.
  • It might apply to assessments of other structured models beyond CMMI by similar adaptation of practices into stories.
  • Repeated use in different organizational settings would show whether the collaborative benefits hold consistently.

Load-bearing premise

Success observed in one consulting assignment demonstrates the technique's general effectiveness and that the agile adaptations preserve assessment validity without introducing bias or loss of rigor.

What would settle it

Conducting the technique in several additional assessments with varying team conflicts and comparing the resulting agreement levels and assessment outcomes to those from traditional document-based methods would test if the approach works more broadly.

read the original abstract

This paper describes a group interview technique designed to support documentless process assessments while promoting at the same time collaboration among assessment participants. The method was successfully used in one consulting assignment where it got previously discording participants, talking to each other and agreeing on the issues. The technique borrows from agile software development the concept of user stories to cast CMMIs specific practices in concrete terms and the Planning Poker technique, instead of document reviews and audit like interviews, for fact finding and corroboration.

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

1 major / 0 minor

Summary. The manuscript describes a group interview technique for documentless process assessments that adapts agile practices—specifically, user stories to concretize CMMI specific practices and Planning Poker for fact-finding and corroboration instead of document reviews or audit-style interviews. It reports that the technique was successfully applied in a single consulting assignment, where it enabled previously discordant participants to collaborate and reach agreement on assessment issues.

Significance. If the reported outcome holds under further scrutiny, the work provides a practical, collaboration-focused alternative to traditional document-centric assessments in software process improvement. The explicit borrowing of agile techniques for CMMI assessments is a concrete contribution that could interest practitioners and researchers working on lightweight or agile-compatible assessment methods.

major comments (1)
  1. [description of the consulting assignment] The central claim rests on the successful outcome of one consulting assignment, yet the manuscript provides no details on the specific CMMI practices addressed, the nature of the prior discord, the exact process by which agreement was reached, or any observable indicators of success beyond the authors' summary statement. This absence makes the effectiveness claim difficult to evaluate or replicate.

Simulated Author's Rebuttal

1 responses · 0 unresolved

Thank you for your constructive review. We appreciate the feedback highlighting the need for greater detail on the consulting assignment and will address this in our revision.

read point-by-point responses
  1. Referee: The central claim rests on the successful outcome of one consulting assignment, yet the manuscript provides no details on the specific CMMI practices addressed, the nature of the prior discord, the exact process by which agreement was reached, or any observable indicators of success beyond the authors' summary statement. This absence makes the effectiveness claim difficult to evaluate or replicate.

    Authors: We agree that the manuscript currently offers only a high-level summary of the consulting assignment, which limits the ability to fully evaluate or replicate the reported outcome. The paper's primary focus is on describing the nominal group interview technique itself, using the assignment as an illustrative example rather than a comprehensive case study. We will revise the manuscript to expand this section with additional context, including the specific CMMI practices assessed, the general nature of the discord (e.g., differing participant views on process maturity), the step-by-step application of user stories and Planning Poker that led to agreement, and observable indicators such as convergence in estimates and final consensus. These additions will respect confidentiality constraints from the engagement. revision: yes

Circularity Check

0 steps flagged

No circularity; purely descriptive case report

full rationale

The paper is a descriptive case account of a nominal group interview technique adapted from agile practices and applied in one consulting assignment. No derivation chain, equations, predictions, fitted parameters, or first-principles results exist. The central claim reduces only to the authors' recounting of observed collaboration in that single instance, with no self-referential definitions, statistical extrapolations, or load-bearing self-citations that would create circularity. External agile concepts are cited as sources rather than as unverified self-justification.

Axiom & Free-Parameter Ledger

0 free parameters · 1 axioms · 0 invented entities

The central claim depends on the untested transferability of agile practices to formal process assessment and on the representativeness of one consulting experience; no free parameters, new entities, or additional axioms beyond standard domain assumptions about group dynamics are introduced.

axioms (1)
  • domain assumption User stories and Planning Poker can be directly repurposed for CMMI specific practices without compromising assessment objectivity or introducing systematic bias.
    Invoked implicitly when the abstract states the technique borrows these concepts for fact finding and corroboration.

pith-pipeline@v0.9.0 · 5353 in / 1272 out tokens · 28873 ms · 2026-05-09T21:00:37.498041+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

17 extracted references · 17 canonical work pages

  1. [1]

    Adept: A Unified Assessment Method for Small Software Companies,

    F. Mc Caffery, P. Taylor and G. Coleman, "Adept: A Unified Assessment Method for Small Software Companies," IEEE Software, vol. 24, no. 1, pp. 24-31, 2007

  2. [2]

    A modular software process mini - assessment method,

    K. Wiegers and D. Sturzenberger, "A modular software process mini - assessment method," Ieee software , vol. 17, no. 1, pp. 62-69, 2000

  3. [3]

    Cohn, User stories applied: For agile software development, Addison - Wesley Professional, 2004

    M. Cohn, User stories applied: For agile software development, Addison - Wesley Professional, 2004

  4. [4]

    Essential XP: Card, Conversation, Confirmation,

    R. Jeffry, "Essential XP: Card, Conversation, Confirmation," 30 August 2001. http://ronjeffries.com/xprog/articles/expcardconversationconfirmation/ Accessed: 7 October 2016

  5. [5]

    Delbecq, A

    A. Delbecq, A. Van de Ven and A. Gustafson, Group Techniques for Program Planning: A guide to nominal group and Delphi processes, Glenview: Scott, Foresman and Company, 1975

  6. [6]

    Planing Poker or How to avoid analysis paralysis while release planning,

    J. Grenning, "Planing Poker or How to avoid analysis paralysis while release planning," 2002

  7. [7]

    Cohn, Agile Estimating and Planning, Stoughton: Prentice Hall, 2005

    M. Cohn, Agile Estimating and Planning, Stoughton: Prentice Hall, 2005

  8. [8]

    Standard CMMI Appraisal Method for Process Improvement (SCAMPI) A, Version 1.3: Method Definition Document,

    SCAMPI Upgrade Team, "Standard CMMI Appraisal Method for Process Improvement (SCAMPI) A, Version 1.3: Method Definition Document," Software Engineering Institute, Pittsburgh, 2011

  9. [9]

    Appraisal Requirements for CMMI Version 1.3,

    S. U. Team, "Appraisal Requirements for CMMI Version 1.3," Software Engineering Institute, Pittsburgh, 2011

  10. [10]

    Selling Issues to Top Management,

    J. Dutton and S. Ashford, "Selling Issues to Top Management," Academy of Management Review, vol. 18, no. 3, pp. 397-428, 1993

  11. [11]

    Project Assessments: Supporting Commitment, Participation, and Learning in Software Process Improvement,

    J. I. J. Arent, "Project Assessments: Supporting Commitment, Participation, and Learning in Software Process Improvement," in Proceedings of the 33rd Annual Hawaii International Conference on Systems Sciences, Hawaii, 2000

  12. [12]

    Flesch, The Art of Clear Thinking, New York: Collier Books , 1962

    R. Flesch, The Art of Clear Thinking, New York: Collier Books , 1962

  13. [13]

    Kulpa and K

    M. Kulpa and K. Johnson, Interpreting the CMMI: A Process Improvement Approach, 2nd., Boca Raton: CRC, 2008

  14. [14]

    Expressed Satisfaction with the Nominal Group Technique Among Change Actors,

    J. Gresham, "Expressed Satisfaction with the Nominal Group Technique Among Change Actors," Texas A&M University, 1986

  15. [15]

    An Empirical Study of Using Planning Poker for User Story Estimation,

    N. Haugen, "An Empirical Study of Using Planning Poker for User Story Estimation," in AGILE’06, 2006

  16. [16]

    An Introductory Overview to ITIL 2011,

    e. a. Cartlidge A, "An Introductory Overview to ITIL 2011," itSmf, London, 2011

  17. [17]

    CMMI for Development, Version 1.3,

    CMMI Product Team, "CMMI for Development, Version 1.3," Software Egineering Institute, Pittsburgh, 2010