Run Planning Poker estimation sessions natively inside Azure DevOps Boards. Teams can estimate backlog items without leaving the work item context, reveal votes simultaneously, and write final estimates back to the process-specific field.
Highlights
| Capability | Detail |
|---|---|
| Hidden voting | Commit-reveal keeps vote values out of storage until reveal. |
| Native Boards flow | Hub, backlog menu, work item form tab, sprint tab, and dashboard widget. |
| Process-aware write-back | Resolves Story Points, Effort, or Size based on the work item type. |
| Preview-safe release channel | Production and private preview are separate extension IDs. |
Privacy
Planning Poker has no required backend. Session, vote, and result documents live in the Azure DevOps Extension Data Service for the customer's organization. Optional telemetry is consent-gated and must not include vote values, work item content, or user identity.
Vote Secrecy
Before reveal, vote documents contain only an opaque commitment hash. The plaintext vote and nonce are written only after reveal, and every client verifies the revealed value against the original commitment.
Facilitator controls are workflow controls rather than a separate server-enforced authority boundary. Vote secrecy does not depend on facilitator trust; pre-reveal vote values are absent from storage.