Bucket Sizing session type by Agile Poker for Jira Cloud is a widely used feature. It is based on the Swimlane Sizing card game and similar to the Relative session, but with a fixed number of buckets and their values.
Bucket Sizing is recommended for seasoned teams with proven estimation patterns and it is the fastest session type in Agile Poker. Here is the general gist of the session:
A moderator starts the Bucket Sizing session and selects issues to be estimated.
The moderator invites participants to the session via a sharable link. Alternatively, the moderator shares the screen with participants and interacts on their behalf.
The last step is to assign estimation values corresponding to each column (usually with the Fibonacci sequence).
The moderator saves the assigned values for the issues.
Check the detailed explanation below or see how it works for the similar Relative session here:
Onсe launched from the Classic or Next-Gen project menu, the Bucket Sizing session is configured in 3 quick steps:
Once ready, click the Start session button to proceed.
Session scope can be also re-configured from the main Bucket Sizing session window using Add issue, Create issue and Remove from the session (appears during card dragging process) options:
Once the session starts, you can share the session link with your team by copying it from the address bar, the breadcrumbs section, or from the participants management screen; click Participants button in the top right corner to open it:
The participant management menu can also be used for removing inactive team members from the session. Inactive participants have a grey indicator next to their avatars while active have a green one:
In the Manage participants screen, the moderator role can be assigned. It gives the user several privileges comparing to a regular participant:
The moderator has a crown icon next to their pointer and avatar.
If there is no moderator assigned (default state), all participants have equal access to all the features. Please note that the moderator's role in a public session doesn't have an exclusive power to manage participants; every participant has full access to participants and moderator management settings. While for private sessions participants are managed by moderators only.
While in the session page, drag the issues from the deck (left side of the screen) to one of the buckets on the virtual board (right side of the screen):
Continue dragging cards from the deck to the board till no more user stories left.
The moderator can activate the voting option and ask participants to vote for a "column" for a specific issue or all the issue from the session scope.
In order to enable the voting option the moderator has to expand the Voting panel using the arrow icon:
When enabled, the Automatic issue pickup for voting option will place the next issue from the session scope list to the voting area once the final vote for the current issue has been cast. When disabled, the moderator will manually control issues to vote for.
Drag and drop a user story to the voting area.
Now participants can vote for the issue. The personal voting process options are:
Once personal votes are revealed, the following options are available:
Depending on a team and a flow, different session scenarios are possible, like voting for an issue or for the whole session scope.
When happy with what you see, you can click 'Save estimates' button (bottom right) to conclude the session and update the issues' respective estimation field.
NOTE: all the estimations are saved to:
an estimation field specified in Board Settings for Scrum boards of Company Managed (Classic) projects;
Then click on 'Save' to confirm the action:
That’s it! Now you can go to the board, or get back to the estimation session:
In case of using the 'Finish session' button, the session will be discharged for all the participants without saving the progress.
Current implementation stores the session state in the browser local storage. This has the following implications:
Check out other estimation sessions offered by Agile Poker for Cloud:
Please let us know if this article was helpful, your feedback is appreciated: firstname.lastname@example.org