Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Join a game as a player by clicking Join.

  • Share or join the game by using the copy link option.

    Image Removedimage-20240731-170005.pngImage Added
  1. Via Invitation Email

...

👤 Game Admin

The admin's main task in this phase is selecting an issue for estimation, but can can perform many other specific actions:

Image Removedimage-20240731-173451.pngImage Added
  1. Estimate the first backlog issue – The admin can select a specific issue or simply click here to start estimating from the first backlog issue.

  2. Quick add – The admin can add an issue to the game backlog by typing its key (e.g., JRCS-10) and clicking Quick add. The added issue is placed at the top of the backlog list.

  3. Re-import backlog for current JQL – The admin can search Jira projects for issues using JQL and add them to the game's backlog. The JQL-query, used to filter and add issues, is saved as a game parameter. If issues were added or removed during the game, the admin can restore the initial backlog list using this feature. This feature can be used without affecting any issues that have already been estimated in the game, regardless of whether they were quick-added during the game or not.

  4. Estimate now – The admin can select issues to estimate in any order. Clicking this button initiates the voting phase for the selected issue.

The backlog list is accessible to the game admin throughout all phases. In addition to providing a quick overview of issue details, the backlog enables the admin to swiftly estimate an issue by clicking on it and selecting Estimate now. Clicking this button concludes the current round and initiates the voting phase for the new round to estimate the selected issue. The current issue is then moved to the top of the game's backlog list.

Image Removedimage-20240731-173737.pngImage Added

Additionally, the estimated items archive allows game admins to review estimation history and make changes to the game's backlog. When you click on an issue in the archive, a window appears showing its estimation history and two buttons:

Image Removedimage-20240731-175046.pngImage Added
  1. Estimate now – Clicking this ends the current round and starts a new round's voting phase immediately. The selected issue is moved to the top of the game's backlog for re-estimation.

  2. Delete – Clicking this removes the issue from the estimated issues archive. It doesn't impact the current round, but the issue will no longer be in the archive. The deleted issue's estimation value is subtracted from the estimated points displayed in the sidebar.

...

👤 Game Admin

Admins estimate the issue just like estimators but have additional responsibilities. They are provided with a group of additional controls, available to them during the voting phase. These controls allow the game admin to commit the following actions:

Image RemovedImage Added
  1. Reveal cards – Instantly reveal played cards, concluding the voting phase and initiating the discussion phase. Estimations from participants who haven't played their cards won't be considered during the discussion.

  2. Skip & postpone – Admins can decide to postpone the current issue for later estimation rounds without initiating the discussion phase. The issue being voted on will be moved to the bottom of the game backlog list.

  3. Skip & remove – Admins have the authority to skip and remove the current issue from the game backlog. If it's the last issue to estimate, the game ends. When an issue is removed from the game backlog, it remains in the Jira backlog. The removed issue can be brought back to the game backlog by re-importing JQL.

...

👤 Game Admin

In this phase, estimations by participants are organized based on the game's deck type and serve as active controls for the game admin. Hovering over an estimation button triggers the estimation context section. They are provided with a group of additional controls, available to them during the voting phase. These controls allow the game admin to commit the following actions:

Image RemovedImage Added
  1. Save – Enter and save the final estimation value during the discussion phase—the key action in the game. All participants need to agree on the estimation value for the current issue. Once an estimation value is entered and this button is clicked, it becomes a parameter for that issue and moves the game to the next round if there are more issues in the backlog. If an estimation value is saved for the last unestimated issue, the game ends.

    • Suggested/Average – You can use this overview to simplify decision-making. It presents the estimation value chosen by most players and an average estimation value based on all estimations from the round's voting phase.

Panel
panelIconIdatlassian-warning
panelIcon:warning:
bgColor#F4F5F7

Keep in mind that you need to match your deck type with a storage field. To accurately save an estimation, understanding the data type is crucial for proper storage within the designated Jira issue field. Ensure that the export field in your game's configuration matches the data type of the deck you intend to use. If there's a mismatch between the deck type and the export field's data type, be sure to configure a suitable deck mapping.

  1. Replay – Admins can restart the voting phase of the current round, discarding all participants' estimations for that round.

  2. Skip & postone/remove – These buttons function similarly to how they did during the voting phase..

...

When the game is finished, you can export it to CSV format with summarised estimation data through the dashboard.

...

🚀 Next article

Panel
panelIconId1f3ae
panelIcon:video_game:
panelIconText🎮
bgColor#F4F5F7

Game controls (DC)