Requirements Toolbox Tool
Wideband Delphi
Introduction
Key details of how to use
the technique
Situations in which the
technique best applies
Strengths
Possible Gotchas
Where to go for further
information
© 2003-2007 Construx Software Builders, Inc. All Rights Reserved
Builds on the principle that multiple heads are better than one.
Developed at the Rand Corporation in 1948, the Delphi estimation
method asks a small team of experts to anonymously generate individual
estimates from a problem description and reach consensus on a final set
of estimates through iteration.
You can use the technique to prioritize requirements by having the team
focus on the value or cost side of the priority function.
Identify a coordinator and a group of three to five experts
together who understand the application domain.
Coordinator presents each expert with a specification and an
estimation form.
Coordinator calls a group meeting in which the experts discuss
estimation issues with the coordinator and each other.
Experts fill out forms anonymously
Coordinator prepares and distributes a summary of the estimates
on an iteration form.
Coordinator calls a group meeting, specifically focusing on
having the experts discuss points where their estimates varied
widely.
The experts review the summary and submit another anonymous
estimate on the form.
The last three steps are repeated until a consensus is reached.
Particularly useful for high – mid level “initial” estimates – at the
beginning or early phases of a project
Helps get buy-in from the stakeholders
Ways to use it incorrectly
• Allowing people to game the system.
Situations to which it is a bad match
• When you already have a defined, objective way to prioritize
requirements
• When the stakeholders have competing agendas that would
preclude them from reaching consensus
Steve McConnell, Software Estimation: Demystifying the Black Art,
Microsoft Press, 2006
Construx seminar: Software Estimation in Depth
Page 1
. Version 1