Planning Poker Template
API Design Estimation
Estimate API endpoint complexity before the sprint kicks off
A focused planning poker session for engineering teams designing and building REST or GraphQL APIs. Fibonacci sizing accounts for endpoint complexity, auth requirements, data validation, and downstream service dependencies. Simultaneous reveal surfaces cases where one engineer knows about a gnarly edge case that everyone else missed, preventing scope creep mid-sprint.
Deck type
fibonacci
Duration
45 minutes
Team size
3–7 engineers
Estimation focus
Endpoint complexity and dependencies
Steps
- 01List the API endpoints or mutations to be built
- 02Describe the contract: inputs, outputs, auth, and edge cases
- 03Vote on complexity — consider validation, error handling, and dependencies
- 04Reveal and discuss any wide spreads in the votes
- 05Agree on a final point value and note open questions
- 06Move to the next endpoint
When to use
When designing a new service, a public API, or a set of internal endpoints that multiple teams will consume. Best run after the API contract is sketched but before implementation begins.
Related templates
Open this template in a room
Create a free Plandeck room pre-configured with this template. No signup required.