UC: Agile Estimation Board
Logo | |
---|---|
Use Case | Agile Estimation Board |
Category | Estimation |
Company/Team Managed Projects | Both |
Summary | Practice based on experiences to improve the relativity problem of Planning Poker technique |
The paragraphs below outlines the specific use case. For more details about advanced features and complementary functionality we suggest to review Board dynamics section of this documentation.
Detailed overview
How to create?
(1) Go to “My Boards“ section. If you do not have any active boards this going to be your default page.
Otherwise (if you already have one or few boards created) click on menu icon in top left corner to select “Manage Boards“
(2) Click on “Create board“, choose “Agile Estimation Board“ and Next.
(3) On the initial configuration screen please specify
Name of the board
Projects to pool Jira issues from
Story points field that’s in use
JQL to filter out the issues (default is issuetype in (epic, story))
Depending on configuration of the Jira Project different fields could be used for Story Points, namely
Story Points for “Classic“ projects
Story point estimate for “Next Gen“ projects
If you try to use the wrong one an appropriate error message will be shown.
(4) Click “Create“
How to use?
(1) You will receive a board with pre-configured columns for Story Points Estimation.
(2) Drag and drop issues between column to assign new / change existing estimate. All the changes to estimates are applied automatically and you do not need to commit it after.
(3) To Edit column value, Change title, Add or Remove one move mouse to selected column and you will receive a tooltip with all the available options:
e.g. let’s click on Edit
How to configure?
(1) Click settings icon in top right corner ..
.. to open “Board configuration“ screen.
(2) on “General” Tab you can amend
Name of the board
Projects to pool Jira issues from
JQL to filter out the issues (default is issuetype in (epic, story))
(3) on “Columns and Swimlanes“ tab you can change configuration of fields used respectively for Columns and Swimlanes. Swimlanes are optional. To remove them choose “-- none -- “ in popup.
Depending on configuration of the Jira Project different fields could be used for Story Points, namely
Story Points for “Classic“ projects
Story point estimate for “Next Gen“ projects
If you try to use the wrong one an appropriate error message will be shown.
For Agile Estimation Board we suggest to try out the following swimlanes:
Sprints to put story in appropriate sprint along side estimation
Assignees to assign story to selected team member along side estimation
References
While creating this template we got the inspiration from the following articles:
Other related Use-Cases
Check out other Agile Boards