Planning Poker

as donto believed on

From Dontopedia, the open, paraconsistent wiki. (Last updated 2026-06-10.)

Planning Poker is A consensus-based technique for estimating effort for tasks..

44 facts·20 predicates·5 sources·8 in dispute

Mostly:rdf:type(6), purpose(4), has step(4)

Inbound mentions (7)

Other subjects in dontopedia point AT this entity as a value. These are inverse relationships — e.g. "X motherOf this subject" — and answer questions the forward facts can't. Grouped by predicate.

`achievedBy`Achieved by(1)

Consensusex:consensus

`containsMethod`Contains Method(1)

Example Implementationex:example-implementation

`precedes`Precedes(1)

Task Breakdownex:task-breakdown

`relatedTo`Related to(1)

Agile Estimationex:agile-estimation

`usedIn`Used in(1)

Predefined Scaleex:predefined-scale

`usesTechnique`Uses Technique(1)

Expert Judgmentex:expert-judgment

`utilizes`Utilizes(1)

Agile Estimationex:agile-estimation

Other facts (40)

The long tail: predicates that appear too rarely to warrant their own section. Filter or scroll to find a specific one. Each row links to its source.

40 facts

Predicate	Value	Ref
Rdf:type	Estimation Technique	[1]
Rdf:type	Technique	[2]
Rdf:type	Estimation Technique	[3]
Rdf:type	Estimation Method	[4]
Rdf:type	Agile Technique	[5]
Rdf:type	Relative Estimation Technique	[5]
Purpose	estimating effort	[1]
Purpose	Reach Consensus on Estimates	[2]
Purpose	Reach Consensus	[2]
Purpose	helps teams reach a shared understanding of the effort required	[3]
Has Step	Gather the Team	[3]
Has Step	Discuss Each Task	[3]
Has Step	Vote on Effort	[3]
Has Step	Reach Consensus	[3]
Action	gather the team	[4]
Action	discuss each task	[4]
Action	vote on effort using predefined scale	[4]
Action	reach consensus on estimate	[4]
Has Sub Action	Gather Team	[4]
Has Sub Action	Discuss Tasks	[4]
Has Sub Action	Vote Effort	[4]
Has Sub Action	Reach Consensus	[4]
Process Step	team member selects card representing estimate	[1]
Process Step	team discusses until consensus	[1]
Uses	cards	[1]
Uses	Predefined Scale	[4]
Used by	Expert Judgment	[2]
Used by	Agile Estimation	[5]
Characteristic	consensus-based technique	[1]
Goal	Consensus on Estimates	[2]
Description	A consensus-based technique for estimating effort for tasks.	[3]
Participant	the team	[4]
Precedes	Time Tracking	[4]
Aims for	Consensus	[4]
Requires	Team Participation	[4]
Involves	Team Discussion	[4]
Ensures	Team Alignment	[4]
Part of	Agile Estimation	[5]
Type of	Agile Technique	[5]
Member of	Agile Technique	[5]

Timeline axis is valid_time — when each source says the fact was true in the world, not when Dontopedia learned about it. Retracted rows are kept for provenance; coloured stripes indicate the context kind.

44 undated

—

typebeam/c9d960cb-aa02-4bdf-b443-4ca984bddd08

ex:EstimationTechnique

—

labelbeam/c9d960cb-aa02-4bdf-b443-4ca984bddd08

Planning Poker

—

characteristicbeam/c9d960cb-aa02-4bdf-b443-4ca984bddd08

consensus-based technique

—

purposebeam/c9d960cb-aa02-4bdf-b443-4ca984bddd08

estimating effort

—

processStepbeam/c9d960cb-aa02-4bdf-b443-4ca984bddd08

team member selects card representing estimate

—

processStepbeam/c9d960cb-aa02-4bdf-b443-4ca984bddd08

team discusses until consensus

—

usesbeam/c9d960cb-aa02-4bdf-b443-4ca984bddd08

cards

—

typebeam/660d7675-0559-4ede-9710-d2339b11e624

ex:Technique

—

labelbeam/660d7675-0559-4ede-9710-d2339b11e624

Planning Poker

—

purposebeam/660d7675-0559-4ede-9710-d2339b11e624

ex:reach-consensus-on-estimates

—

purposebeam/660d7675-0559-4ede-9710-d2339b11e624

ex:reach-consensus

—

usedBybeam/660d7675-0559-4ede-9710-d2339b11e624

ex:expert-judgment

—

goalbeam/660d7675-0559-4ede-9710-d2339b11e624

ex:consensus-on-estimates

—

typebeam/6b8b9a15-7aa3-4347-a535-e53eb3097e79

ex:EstimationTechnique

—

labelbeam/6b8b9a15-7aa3-4347-a535-e53eb3097e79

Planning Poker

—

descriptionbeam/6b8b9a15-7aa3-4347-a535-e53eb3097e79

A consensus-based technique for estimating effort for tasks.

—

purposebeam/6b8b9a15-7aa3-4347-a535-e53eb3097e79

helps teams reach a shared understanding of the effort required

—

hasStepbeam/6b8b9a15-7aa3-4347-a535-e53eb3097e79

ex:gather-the-team

—

hasStepbeam/6b8b9a15-7aa3-4347-a535-e53eb3097e79

ex:discuss-each-task

—

hasStepbeam/6b8b9a15-7aa3-4347-a535-e53eb3097e79

ex:vote-on-effort

—

hasStepbeam/6b8b9a15-7aa3-4347-a535-e53eb3097e79

ex:reach-consensus

—

typebeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

ex:estimation-method

—

actionbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

gather the team

—

actionbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

discuss each task

—

actionbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

vote on effort using predefined scale

—

actionbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

reach consensus on estimate

—

participantbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

the team

—

hasSubActionbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

ex:gather-team

—

hasSubActionbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

ex:discuss-tasks

—

hasSubActionbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

ex:vote-effort

—

hasSubActionbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

ex:reach-consensus

—

precedesbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

ex:time-tracking

—

usesbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

ex:predefined-scale

—

aimsForbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

ex:consensus

—

requiresbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

ex:team-participation

—

involvesbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

ex:team-discussion

—

ensuresbeam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9

ex:team-alignment

—

typebeam/0471c7b9-a895-4aee-836e-b8f1e83b31e0

ex:AgileTechnique

—

labelbeam/0471c7b9-a895-4aee-836e-b8f1e83b31e0

Planning Poker

—

partOfbeam/0471c7b9-a895-4aee-836e-b8f1e83b31e0

ex:agile-estimation

—

typeOfbeam/0471c7b9-a895-4aee-836e-b8f1e83b31e0

ex:agile-technique

—

memberOfbeam/0471c7b9-a895-4aee-836e-b8f1e83b31e0

ex:agile-technique

—

typebeam/0471c7b9-a895-4aee-836e-b8f1e83b31e0

ex:RelativeEstimationTechnique

—

usedBybeam/0471c7b9-a895-4aee-836e-b8f1e83b31e0

ex:agile-estimation

References (5)

5 references

[1]C9d960cb Aa02 4bdf B443 4ca984bddd087 facts
ctx:claims/beam/c9d960cb-aa02-4bdf-b443-4ca984bddd08
- full textbeam-chunk
  text/plain1 KBdoc:beam/c9d960cb-aa02-4bdf-b443-4ca984bddd08
  Show excerpt
  - **Hours**: Absolute time estimates can be useful if you have a good understanding of the tasks and how long they typically take. ### 5. **Apply the Fibonacci Sequence for Story Points** If you choose to use story points, consider using …
[2]660d7675 0559 4ede 9710 D2339b11e6246 facts
ctx:claims/beam/660d7675-0559-4ede-9710-d2339b11e624
- full textbeam-chunk
  text/plain1 KBdoc:beam/660d7675-0559-4ede-9710-d2339b11e624
  Show excerpt
  #### Step 1: Define Tasks and Requirements 1. **List Tasks:** - Create a detailed list of the 50 tasks. - Include task descriptions, dependencies, and any special requirements. 2. **Break Down Tasks:** - Break down larger tasks i…
[3]6b8b9a15 7aa3 4347 A535 E53eb3097e798 facts
ctx:claims/beam/6b8b9a15-7aa3-4347-a535-e53eb3097e79
- full textbeam-chunk
  text/plain1 KBdoc:beam/6b8b9a15-7aa3-4347-a535-e53eb3097e79
  Show excerpt
  1. **Identify Subtasks**: Break down each large task into smaller subtasks. 2. **Estimate Subtasks**: Estimate the time required for each subtask individually. 3. **Sum Up**: Add up the time estimates for all subtasks to get the total estim…
[4]4e5f84e6 B0fe 42b1 A4e7 2bc072d6a7a916 facts
ctx:claims/beam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9
- full textbeam-chunk
  text/plain1 KBdoc:beam/4e5f84e6-b0fe-42b1-a4e7-2bc072d6a7a9
  Show excerpt
  2. **Compare Estimates**: At the end of the sprint, compare the estimated time with the actual time spent. 3. **Adjust Future Estimates**: Use this comparison to adjust your estimation strategy for future sprints. ### Example Implementatio…
[5]0471c7b9 A895 4aee 836e B8f1e83b31e07 facts
ctx:claims/beam/0471c7b9-a895-4aee-836e-b8f1e83b31e0
- full textbeam-chunk
  text/plain1 KBdoc:beam/0471c7b9-a895-4aee-836e-b8f1e83b31e0
  Show excerpt
  Breaking down the task into smaller, more manageable subtasks can help you estimate the time required for each part more accurately. Once you have a detailed breakdown, you can sum up the estimated times for each subtask to get a total esti…

Keep researching

Missing something or suspicious of what's here? Kick off a research session — a Claude agent will investigate, cite its sources, and file new facts into a dedicated context you can review before accepting into the shared view.

Planning Poker

Inbound mentions (7)

achievedByAchieved by(1)

containsMethodContains Method(1)

precedesPrecedes(1)

relatedToRelated to(1)

usedInUsed in(1)

usesTechniqueUses Technique(1)

utilizesUtilizes(1)

Other facts (40)

Timeline

References (5)

See also

Keep researching

`achievedBy`Achieved by(1)

`containsMethod`Contains Method(1)

`precedes`Precedes(1)

`relatedTo`Related to(1)

`usedIn`Used in(1)

`usesTechnique`Uses Technique(1)

`utilizes`Utilizes(1)