Planning poker for Azure DevOps: a practical workflow

A standalone poker room can reach consensus, but someone still has to find each work item, read its acceptance criteria, and copy the final estimate into Azure Boards. That administrative gap is where mistakes and stale values appear.

PookieRetro’s Azure DevOps connection lets a facilitator find and import work items for the room, run hidden live or async voting, select the final estimate, and push that value back to the configured story-point field.

Start with stories that meet your team’s definition of ready. Confirm the problem, acceptance criteria, dependencies, and open technical questions before anyone reaches for a card.

A batch of five to ten well-formed stories usually creates a better conversation than a backlog dump. Large items and unclear items should be split or returned for refinement rather than forced into a number.

In the poker room, connect the Azure DevOps organization and project, then search for the work items the team prepared. PookieRetro stores integration credentials encrypted at rest and uses the connection to read candidate work and update the chosen estimate.

The current integration authenticates with an Azure DevOps personal access token rather than Microsoft Entra OAuth. Teams with policies that prohibit PAT-based integrations should use an approved native extension or another Entra-compatible workflow.

Importing the work item keeps its title and context beside the vote. The team can stay in one estimation flow instead of asking a screen-sharing facilitator to shuttle between tabs.

Choose Fibonacci, Modified Fibonacci, T-shirt sizes, Five Fingers, Powers of Two, or a custom deck. Each teammate votes privately. PookieRetro exposes voter status before reveal but keeps the actual card values in a separate server query until the room reveals them.

When cards turn over, ask the highest and lowest voters to explain assumptions before taking another round. The useful output is shared understanding; the number is only its compact record.

Async voting works when the story context can stand on its own. Open the room for a defined window, ask teammates to leave questions in the room, and reveal only after the expected voters have responded.

Do not use async mode to hide unresolved ambiguity. If estimates spread widely, schedule the smallest possible live conversation and preserve the disagreement in the meeting result.

After discussion, choose the agreed estimate and send it back to Azure DevOps. Confirm the work item shows the new value before moving to the next story.

Then share PookieRetro’s read-only results page or export the session as Markdown, CSV, or JSON. Azure Boards remains the source of truth for the estimate; the results page records how the team reached it and helps absent stakeholders catch up.

Keep the mechanics consistent so the conversation can focus on uncertainty.