Wideband delphi

Wideband delphi

The Wideband Delphi estimation method is a consensus-based estimation technique for estimating effort. It was developed in the 1940s at the RAND Corporation as a forecasting tool. It has since been adapted across many industries to estimate many kinds of tasks, ranging from statistical data collection results to sales and marketing forecasts.

Wideband Delphi Process

Barry Boehm and John A. Farquhar originated the Wideband variant of the Delphi method in the 1970s. They called it "wideband" because, compared to the existing delphi method, the new method involved greater interaction and more communication between those participating. The method was popularized by Boehm's book "Software Engineering Economics" (1981). Boehm's original steps from this book were:

# 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
# Coordinator calls a group meeting, specifically focusing on having the experts discuss points where their estimates vary widely
# Experts fill out forms, again anonymously, and steps 4 to 6 are iterated for as many rounds as appropriate.

A variant of Wideband Delphi was developed by Neil Potter and Mary Sakry of [http://www.processgroup.com/ The Process Group] . In this process, a project manager selects a moderator and an estimation team with three to seven members. The Delphi process consists of two meetings run by the moderator. The first meeting is the kickoff meeting, during which the estimation team creates a work breakdown structure (WBS) and discusses assumptions. After the meeting, each team member creates an effort estimate for each task. The second meeting is the estimation session, in which the team revises the estimates as a group and achieves consensus. After the estimation session, the project manager summarizes the results and reviews them with the team, at which point they are ready to be used as the basis for planning the project.
* Choose the team. The project manager selects the estimation team and a moderator. The team should consist of 3 to 7 project team members. The team should include representatives from every engineering group that will be involved in the development of the work product being estimated.
* Kickoff meeting. The moderator prepares the team and leads a discussion to brainstorm assumptions, generate a WBS and decide on the units of estimation.
* Individual preparation. After the kickoff meeting, each team member individually generates the initial estimates for each task in the WBS, documenting any changes to the WBS and missing assumptions.
* Estimation session. The moderator leads the team through a series of iterative steps to gain consensus on the estimates. At the start of the iteration, the moderator charts the estimates on the whiteboard so the estimators can see the range of estimates. The team resolves issues and revises estimates without revealing specific numbers. The cycle repeats until either no estimator wants to change his or her estimate, the estimators agree that the range is acceptable or two hours have elapsed.
* Assemble tasks. The project manager works with the team to collect the estimates from the team members at the end of the meeting and compiles the final task list, estimates and assumptions.
* Review results. The project manager reviews the final task list with the estimation team.

ee also

* The Wisdom of Crowds
* Delphi method
* Planning poker

Further reading

* cite book
author = Andrew Stellman and Jennifer Greene
authorlink =
year = 2005
title = Applied Software Project Management
edition =
publisher = O'Reilly Media
location = Sebastopol, MA
id = ISBN 0-596-00948-8
url = http://www.stellman-greene.com

External links

* [http://www.stellman-greene.com/aspm/content/view/23/38/ Wideband Delphi Estimation Process]
* [http://www.ddj.com/architect/184414570 Stop Promising Miracles by Karl Wiegers]


Wikimedia Foundation. 2010.

Игры ⚽ Нужно решить контрольную?

Look at other dictionaries:

  • Delphi method — The Delphi method (  /ˈdɛl …   Wikipedia

  • Barry Boehm — 2006 Barry W. Boehm (* 16. Mai 1935 in Santa Monica, Kalifornien) ist ein US amerikanischer Softwareingenieur, der durch seine Kostenbetrachtungen von großen Softwareprojekten bekannt wurde. Er sah Software als den primären Kostenfaktor für… …   Deutsch Wikipedia

  • Barry W. Boehm — Barry Boehm 2006 Barry W. Boehm (* 16. Mai 1935 in Santa Monica, Kalifornien) ist ein US amerikanischer Softwareingenieur, der durch seine Kostenbetrachtungen von großen Softwareprojekten bekannt wurde. Er sah Software als den primären… …   Deutsch Wikipedia

  • Barry Boehm — Barry W. Boehm is known for his many contributions to software engineering.He was the first to identify software as the primary expense of future computer systems, he developed COCOMO, the spiral model, wideband delphi, and many more… …   Wikipedia

  • Estimation (project management) — For estimation in general, see Estimation.In project management (i.e., for engineering), accurate estimates are the basis of sound project planning. Many process which have been developed to aid engineers in making accurate estimates, such as… …   Wikipedia

  • The Wisdom of Crowds — The Wisdom of Crowds: Why the Many Are Smarter Than the Few and How Collective Wisdom Shapes Business, Economies, Societies and Nations , first published in 2004, is a book written by James Surowiecki about the aggregation of information in… …   Wikipedia

  • Покер планирования — Разработка программного обеспечения Процесс разработки ПО Шаги процесса Анализ • Проектирование • Программирование • Докумен …   Википедия

  • Schedule (project management) — In project management, a schedule consists of a list of a project s terminal elements with intended start and finish dates.Creating a project scheduleBefore a project schedule can be created, a project manager should typically have a work… …   Wikipedia

  • Estimation in software engineering — The ability to accurately estimate the time and/or cost taken for a project to come in to its successful conclusion is a serious problem for software engineers. The use of a repeatable, clearly defined and well understood software development… …   Wikipedia

  • Planning poker — is a consensus based estimation technique for estimating, mostly used to estimate effort or relative size of tasks in software development. It is a variation of the Wideband Delphi method. It is most commonly used in agile software development,… …   Wikipedia

Share the article and excerpts

Direct link
Do a right-click on the link above
and select “Copy Link”