Game roles

Following Jira architecture and Scrum plot, Planning Poker divides users into different roles. Brief overview of each of these roles is located below, going from roles with narrow privileges to roles with wider ones.

Spectator is the user, with rights which derive plainly from this role's name. Spectator can only spectate the flow of the game by viewing all the round phases, but not taking part in them. Spectator can't cast cards to estimate issues. Spectator is not considered as the participant of the game. User can join the game in the role of spectator from its very beginning, but can become the participant anytime during the course of the round.

Player is the user, who to the extent of the spectator's rights is also able to make active actions during the round phases. Main user capability is to play cards during round's voting phase, to estimate issues. User is considered as the participant of the game. Player can become the spectator by going AFK anytime during the course of the round.

Administrator is the user with all the rights of the spectator and the player roles, combined with vast privileges to control the course of the game. Game administrator is responsible for configuring all the game options and editing game's backlog. Admin is considered as the participant of the game. The user, who started the game becomes its administrator initially. Additional game admins can be added any time during the game by editing game's configuration, sharing admin's privileges or by entering admin's password (if the last is enabled). Admin can become the spectator by going AFK anytime during the course of the round, but once he returns from AFK he is regaining all the capacity of administrative rights.