Game configuration (DC)

Overview

A Planning Poker game allows teams to cast their votes in story points, T-shirt sizes, or time estimates. This fosters active discussions and consensus-building among team members.

You can easily manage your game's backlog, invite teammates, view and edit task details or comments during estimation, and save the estimates in a designated Jira field. Additionally, you can estimate on your preferred device, host private or password-protected sessions, and fine-tune your game using advanced settings.

Requirements

• Before you start your very first Planning Poker game you should provide the app with content to estimate. To do this, you have to:

  • Create at least one Jira project.

  • Create at least one issue that you want to estimate in any Jira project.

• Ensure all team members can participate simultaneously.

How to start a Planning Poker game

Step 1: Start a game

If you have a project with issues to estimate, you can start your game.

If you haven’t created any games yet:	From the Planning Poker app dashboard:

If you haven’t created any games yet:	From the Planning Poker app dashboard:
Your dashboard will look like this: Open Simply click New game to start configuring your game.	Open the app dashboard by clicking Planning Poker from the Jira navigation bar, click New Game. Open

Step 2: Configure the Planning Poker game

After selecting to create a game, Planning Poker will navigate you to the game configuration menu, which is divided into three sections: Game basics, Game administration, and Game flow. It will help you customize the game, making estimations as close to your project's traits as possible.

Here you need to enter the most essential parameters of your game. This includes:

1. Game name – Name your session. Be creative to avoid confusion when viewing the game list in the Planning Poker Dashboard.

2. Export estimates to – Select a field from the issue object where the estimated points value will be stored once the issue is estimated. We show you both the field name and its ID, making it easy to distinguish between default fields and fields you've created yourself. You can use the following fields:

   • Story Points: This field stores integers and is suitable for saving numerical estimations like Fibonacci deck-type cards or custom numerical deck cards.

   • Comments: This field stores string values, making it ideal for abstract estimations such as t-shirt sizes or custom deck non-numerical estimation values.

   • Original Estimate: This field stores time units like 1h, 30m, 5m, etc. It works well with an hours deck type or a custom deck containing cards with time unit estimation values.

   • Remaining Estimate: This field stores time units representing the remaining effort required to complete the task, e.g., 1h, 30m, 5m, etc.

   • Custom fields:

3. Card deck – Choose the front values on cards that players will use to vote when estimating an issue. You can select from predefined card deck templates or customize them as needed. You can also employ labels to conceal specific values, allowing you to focus on relative sizes rather than fixating on exact numerical values during estimation.

   • Fibonacci: Includes cards with values 1, 2, 3, 5, 8, 13, 21, 34, and 55.

   • T-shirt: Features cards labeled as XXS, XS, S, M, L, XL, and XXL.

   • Labeled T-Shirt: Combines labels with values, such as XXS=0.5, XS=1, S=2, M=3, L=5, XL=8, and XXL=13.

   • Hours: Consists of cards marked as 1h, 2h, 3h, 4h, 5h, 6h, 7h, 8h, 9h, 10h, 11h, and 12h.

   • Custom: Whenever you customize a card deck template using special input, it switches itself to a Custom card deck. When you customize the card deck, use commas to separate different values. This tells you what type of card it is and how many of them there are. If you put in three values separated by commas, players get only three cards for estimating issues in the game.

4. Add "?" and "coffee" cards to the deck – If enabled, this adds two extra cards to your deck:

   • "?" – Allows a player to express uncertainty when estimating the current issue.

   • "coffee" – Allows a player to inform other game participants that they need a break.

      

5. Round autostart – If enabled, the game's next round will start automatically once the current issue's estimation is successfully saved or if the issue is skipped. The next issue to estimate will be automatically selected from the top of the game backlog.

6. Notify participants – Here you select the participants of the game and you can send invites from the Edit game screen after the game is created.

7. Show advanced configuration – Once you've covered the basics, you can click Next: Edit backlog to start editing the game backlog. Or you can click this option to continue configuring with further advanced settings.

Step 3: Switch to advanced configuration (Optional)

8. Game description – Describe your game to make its purpose clear to all estimation participants.

    

9. Private game – If checked, your game will be hidden on the Planning Poker Dashboard for all project participants, except the game administrator. You will be able to add users to a private game only by sending them an email notification with the game’s URL, as described in the #6 “Notify participants” section.

10. Multiple admins – By default, the game creator has full administrative control. Here you can also add multiple game admins by simply selecting their names from the dropdown. This list will also display users who currently have administrative privileges regarding the game. To take away their admin privileges, simply click the cross icon next to the user's name.

11. Admin password – The admin can add more admins by editing the #10 “Multiple admins” section or the Add additional game admin button in the game's top bar. However, there may be instances when the current admin is unavailable. This feature allows other players to become additional game admins if they know the password set here, even if the current admin is unavailable. If the Admin Password field is not empty, a "Become Game Admin" button will appear in the game's top bar. By clicking it and entering the admin password, the user becomes a game administrator.

     

12. Permission by group – Here you can restrict the game for any user group.

13. Custom fields above – Add extra custom fields to appear above the issue description during the game for quick reference.

     

14. Custom fields above – Add more custom fields to appear below the issue description.

     

15. Timer autostart – When enabled, this feature initiates the countdown for the round timer at the start of the voting phase. If the timer reaches its limit, the voting phase concludes, regardless of whether all users have submitted their cards. The default timer duration is 45 seconds.

16. Timer sound – When enabled, there will be sound notifications at the start and end of the timer.

17. Timer duration – Change the round timer duration from the default 45 seconds to any other value. This will affect both the timer autostart (if enabled by the above option) and the timer started by the admin's actions.

18. Labels (Estimated, Skipped, Removed) –

    • Estimated – To tag estimated issues, just enter the label you want. When you save the estimation, the label will be added to the issue.

    • Skipped – To tag issues that are postponed or canceled, enter the desired label. The label will be added to an issue when the admin clicks either the "Skip and postpone" or "Skip and remove" button.

    • Removed – To remove a label from an estimated issue, enter the label values you want to remove. The label will be removed from the issue after the estimation is saved successfully.

19. Estimation context – This powerful feature in Planning Poker helps you make better estimations in a Scrum approach. When the voting phase starts and you hover over a card with a value (e.g., 3), Planning Poker will search for all previous issues in the project that were estimated as 3. This helps you see how similar issues were estimated in the past:

Here you can control the context to fit your needs. For example, you could set the Estimation context to only display issues with specific labels, like “design” and “UX”, by entering the following JQL query into the Estimation context settings input: "labels IN (design, UX)".

20. Issue status estimated – Here you can choose a state (To Do, In Progress, etc.) to transition the issue after estimating it. Enter the "transition name" to the needed state.

21. Issue status removed – Here you can choose a state (To Do, In Progress, etc.) to transition the issue after it’s removed or skipped from the estimation.

22. Move to Sprint – You can move an issue to a specific sprint by selecting the board and then the sprint.

Click Next: Edit Backlog to move to the next step.

Step 4: Configure backlog

Here the admin searches for specific issues within Jira projects, add them to the game's backlog, and arrange them in the desired order. The filter options are:

1. Project – Choose specific Jira projects from which the issues will be sourced for estimation. Once you click on a project, all the issues in it will be added to the game.

2. Type – Filter issues based on their type, such as Change, Incident, Bug, Epic, Problem, Service request, and more.

3. Status – Select issues based on their current status within the workflow. Options could include Authorize, Draft, Awaiting approval, and more.

4. Assignee – Select issues based on their current assignee.

5. Fields – Use this dropdown to add additional filters to your filter bar. Once the filter is selected in the dropdown, it will be added to your filters bar and you will be able to use it along with the default filters.

6. My Filters – You can also use your own custom filters. For more information on creating custom filters, refer to the Jira documentation.

7. Search board and then sprint… – Here you can select a board and also a sprint. Keep in mind that this section and the JQL are not synchronized, so we recommend using either these filters or the ones that come before them on their own.

8. JQL – This section displays the Jira Query Language (JQL) translation of your selected filters and offers a way to create more complex and customized queries. If you're a seasoned Jira user, you can write your own JQL query into input to find issues you want to add to your Planning Poker game. Building a custom JQL query is a flexible approach to commence search in your Jira projects, but to master it you have to know how to deal with operators, expressions, and other features of JQL. Feel free to surf Jira tutorials to learn more about JQL.

9. Columns – Use this dropdown to add extra columns to your backlog.

10. Checkbox column – To further filter the issues, use this column. To remove any issues that you don’t want to have in the game, check the boxes next to them and remove the selected ones, or simply click the trash icon next to the issue.

Once you've added all the issues you want to include in your Planning Poker game, it's time to arrange them in the desired order. The order of the issues is important not only for keeping the game organized but also for when the next round starts automatically (if #5 “Roud autostart” is enabled) as it selects the top issue from the backlog list. Here's how you can edit your backlog:

• Drag & Drop – This is the old-fashioned way: Just click and hold the issue you want to move, drag it to the place you want it in the list, and drop it.

• Order by Columns – You can also order issues by columns, ascending or descending. To do so, just pick a header of a column you want your issues to be ordered by and click it. Once clicked your issues will be ordered by a chosen column, ascending. If the same column is clicked once more, the order will be switched to descending, and so on.

  • You can easily add other columns to order your backlog by clicking the Columns button and selecting the column(s) you want.

Step 5: Start the game

Once you have tailored your backlog to best suit your needs, click Next: Start game to start the Planning Poker session. A breakdown of the game process is provided in Game Flow chapter of this documentation.

Next Steps

Once you've completed configuring your game, refer to the following documentation to assist you during gameplay: