After installation the Jira home
Image Removed
Image Removed
Starting a game
There are two ways to start a game — from Planning Poker dashboard or from Jira Backlog View.
Starting a game from Planning Poker dashboard
Image Removed
Starting a game from Jira Backlog View
Image Removed
Configuring a game
It is totally okay to start a game without any configuration (you don't even have to name it) Expand |
---|
|
Jira top menu Apps > Planning Poker | Project sidebar |
---|
Image Added | Image Added |
|
Expand |
---|
|
Jira navigation bar | Project sidebar |
---|
Image Added | Image Added |
|
1. Starting/Joining a Game
Before diving into Planning Poker, let's acquaint you with the Dashboard — an essential hub for navigating and managing your estimation sessions. The Dashboard provides a comprehensive overview of ongoing and finished games, allowing you to swiftly access and orchestrate your estimation process. It can be accessed by clicking the entry points above.
On the Dashboard, you can use filters or the search feature to easily locate a game, and perform actions like copying an existing session with all its settings.
Panel |
---|
panelIconId | 1f464 |
---|
panelIcon | :bust_in_silhouette: |
---|
panelIconText | 👤 |
---|
bgColor | #F4F5F7 |
---|
|
For Admins: Your role is to configure the game and manage the estimation process. Begin by creating a new game and inviting participants using an invitation link. You can start a game even without any configuration, but it would be better to make sure that some basic settings are in place.
|
Here's an overview of the basic configuration.Basic game configuration
Image Removed
- Game name is displayed in the dashboard to make it distinguishable, e.g. "Sprint 14 — team Alpha"
- Game description is for participants as a reminder of the scope
- Export estimates to — which field should be used to save estimates after each round
- Deck type — can be anything from Story Points, T-Shirts and time to your custom values
Next step is to define the scope of estimation session. You can do this by defining a JQL search (or you could simply reuse your existing Jira filter, which is our recommended way).
Editing game backlog
Image Removed
After this step your game is ready and will appear in the dashboard list. You can now tell others to join this game. Once everyone's in, you can Panel |
---|
panelIconId | dc3852db-f543-44d3-a1f7-bed908a30255 |
---|
panelIcon | :user: |
---|
panelIconText | :user: |
---|
bgColor | #F4F5F7 |
---|
|
For Participants: |
2. Estimation Process
Planning Poker involves organized rounds, each focusing on estimating an issue. These rounds consist of three phases: Backlog, Discussion, Voting, and Final Estimate Submission.
In summary, the Backlog phase marks the beginning of the game, initiated by the game administrator. After the admin chooses an issue, the Discussion phase begins, during which the Product Owner presents the details of the issue, and participants ask questions to clarify. Once everyone is clear about the issue, the Voting phase starts. After voting, the Final Estimate Submission phase begins, where the Scrum master analyzes the results and ensures a consensus on the estimation value. This phase concludes when the Scrum master saves the estimation value. Subsequently, the game either reverts to the Backlog phase or proceeds directly to the Voting phase if the round auto-start feature (Cloud, DC) is enabled.
a. Backlog Phase
Panel |
---|
panelIconId | 1f464 |
---|
panelIcon | :bust_in_silhouette: |
---|
panelIconText | 👤 |
---|
bgColor | #F4F5F7 |
---|
|
For Admins: |
"" story Image RemovedPlaying a game
Game flow consists of the following phases:
- Backlog phase
- Estimation phase
- Discussion phase
Backlog phase is where game administrator starts the game. Once a story is selected, Estimation phase is triggered where each player is casting their cards. When all players have cast their votes, the cards are flipped and the discussion phase comes becomes active — this is where the Scrum master has to analyse results and make sure that everyone agrees on the same estimation value. Discussion phase is finished when Scrum master saves the estimation value. After that the game either goes back to Backlog phase or straight to Estimation phase (if round auto-start is enabled).
Backlog phase
Image Removed
Estimation phase
Image Removed
Discussion phase
Image Added Panel |
---|
panelIconId | dc3852db-f543-44d3-a1f7-bed908a30255 |
---|
panelIcon | :user: |
---|
panelIconText | :user: |
---|
bgColor | #F4F5F7 |
---|
|
For Participants: |
Panel |
---|
panelIconId | 1f464 |
---|
panelIcon | :bust_in_silhouette: |
---|
panelIconText | 👤 |
---|
bgColor | #F4F5F7 |
---|
|
For Admins: Present the details of the issue with clarity and precision. Your comprehensive presentation sets the stage for an informed discussion and facilitates a more accurate estimation. When everyone is clear about the issue, move the team to the Voting phase.
|
Panel |
---|
panelIconId | dc3852db-f543-44d3-a1f7-bed908a30255 |
---|
panelIcon | :user: |
---|
panelIconText | :user: |
---|
bgColor | #F4F5F7 |
---|
|
For Participants: |
Panel |
---|
panelIconId | 1f464 |
---|
panelIcon | :bust_in_silhouette: |
---|
panelIconText | 👤 |
---|
bgColor | #F4F5F7 |
---|
|
For Admins: |
Image Added Panel |
---|
panelIconId | dc3852db-f543-44d3-a1f7-bed908a30255 |
---|
panelIcon | :user: |
---|
panelIconText | :user: |
---|
bgColor | #F4F5F7 |
---|
|
For Participants: |
d. Final Estimate Submission
Panel |
---|
panelIconId | 1f464 |
---|
panelIcon | :bust_in_silhouette: |
---|
panelIconText | 👤 |
---|
bgColor | #F4F5F7 |
---|
|
For Admins: |
Image Added Panel |
---|
panelIconId | dc3852db-f543-44d3-a1f7-bed908a30255 |
---|
panelIcon | :user: |
---|
panelIconText | :user: |
---|
bgColor | #F4F5F7 |
---|
|
For Participants: |
For a detailed description of the game flow and the controls used by participants and the admin, check out these documents: Game Flow, Game Controls.
3. Ending the Game
A game concludes when all issues are estimated, or the admin chooses to finish it. Finished games can be reopened if needed.
Panel |
---|
panelIconId | atlassian-note |
---|
panelIcon | :note: |
---|
bgColor | #F4F5F7 |
---|
|
For distributed teams that cannot conduct an “on-line” session, Planning Poker offers an Async mode to estimate each Jira issue individually. This mode doesn't follow a unified "session" concept, but participants can estimate in the issues directly through the Async mode tab. To learn more about it, click here. |
Effective communication and collaboration are pivotal for successful estimations in Planning Poker. Let's kick off your first game!