Group Voting
Group voting is one of EstimateQuest’s most powerful features for cross-functional teams.
The Problem
Section titled “The Problem”In a typical sprint planning session, a frontend developer and a backend developer might have wildly different estimates for the same ticket — not because they disagree, but because they’re estimating different work. The frontend work might be a simple UI change (2 points), while the backend needs a complex API refactor (13 points).
Traditional Planning Poker forces a single estimate, which either overfits one team’s perspective or gets averaged into a meaningless number.
The Solution: Group Voting
Section titled “The Solution: Group Voting”EstimateQuest lets you assign one or more groups to each ticket:
- Frontend (blue)
- Backend (green)
- Mobile (purple)
- QA (orange)
When a ticket comes up for voting:
- Only voters in assigned groups see their cards and can vote
- Votes are tracked per group in the summary
- The moderator sets separate estimates per group
- An overall final estimate captures the combined picture
Example Workflow
Section titled “Example Workflow”A “User Authentication” ticket assigned to Frontend + Backend:
- Frontend voters estimate the login form UI → mostly “3”
- Backend voters estimate the auth API → mostly “8”
- After reveal, the moderator sees:
- Frontend consensus: 3
- Backend average: 8 (with one outlier at 13)
- The moderator sets Frontend = 3, Backend = 8, Final = 8
The backend estimate drives the final number since it’s the larger effort — but both perspectives are captured and recorded.
When to Use Group Voting
Section titled “When to Use Group Voting”| Scenario | Recommendation |
|---|---|
| Full-stack feature | Assign Frontend + Backend |
| Mobile-specific bug | Assign Mobile only |
| Cross-platform feature | Assign Frontend + Mobile |
| Testing effort | Assign QA |
| Infrastructure task | Assign Backend only |
| Team-wide discussion | Assign all groups |
Not-Your-Turn State
Section titled “Not-Your-Turn State”When the current ticket doesn’t include your group, you’ll see a “not your turn” indicator instead of voting cards. You can still follow the discussion and see the results after reveal — you just can’t vote on work that doesn’t involve your team.
For how the moderator manages group estimates after reveal, see Group Voting (Moderator Guide).