Zum Ende des Banners springen
Zum Anfang des Banners springen

Overview & quick start

Zum Ende der Metadaten springen
Zum Anfang der Metadaten

Sie zeigen eine alte Version dieser Seite an. Zeigen Sie die aktuelle Version an.

Unterschiede anzeigen Seitenhistorie anzeigen

« Vorherige Version anzeigen Version 13 Nächste Version anzeigen »

This guide covers the following highlights

  1. Sum up estimates for tasks and / or sub-tasks!
  2. Switch between an issue and assignee based list!
  3. Detect deviations from original estimates easily!

Kanban project support

At the moment we support only sprints as containers to get the included issues. A workaround for the moment would be to use a Scrum project which also has a Kanban board, but in the end you will have to use a sprint to see your aggregations for now. However Kanban support is on our backlog.

(Click to enlarge)

The Agile Planning Popup is integrated on the JIRA Agile Board and can be accessed where you need it during sprint planning, dailies or sprint review meetings. 

1: Open the popup in menu 'Agile Planning' and 'show aggregation'.

2: You can select different view modes:

  • Parent Issues only: Estimations of Backlog entries will be summed up (like in JIRA standard).
  • Sub Tasks first: Estimations of sub tasks will be summed up, if they exist. Otherwise the estimation of the parent issues will be added. (Default)
  • Sub Tasks only: Estimations of sub tasks will be summed up, if they exist. Estimations on parent issue level will be ignored at all with this method.
  • Both: Estimations of the parent issue AND the subtasks are summed up.

(Glühbirne) Check out example below!

3: Aggregation mode is by task now. You can toggle between by task and by assignee.

4: Select the sprint, you would like to see. Default is the currently active sprint.

 

Estimations in JIRA Agile Board (Backlog) on an user story

Estimations in JIRA Agile Board (Active sprints), sub-tasks for user story

(Click to enlarge)

Let's find out what the view mode is all about by this example for the different methods:
  • Parent Issues only: Result is 1 week as just estimation of parent issue (Backlog entry) is estimated.
  • Sub Tasks first: Result is 1 week 3 days as subtasks exists for this parent issue, so subtasks will be summed up and parent estimation is ignored.
  • Sub Tasks only: Result is 1 week 3 days as only subtasks are summed up.
  • Both: Result is 2 week 3 days as estimations of the parent issue AND the subtasks are summed up.

(Click to enlarge)

Let's have a closer look at the columns for the issue based list.

  • Icon: Represents the type of the issue. If the ticket contains sub-tasks the icon for sub-tasks is shown for each view mode to highlight that they exist.
  • Name: A link represents the parent issue.
  • Issues: Counts the relevant tickets that are summed up accorfing to the selected view mode. 
    (Glühbirne) 1 parent and 2 sub-tasks for 'sub-task first' view mode count is 2. For view mode 'parent issues only' count is 1.
  • Orig. estimate: Shows the original estimate summed up according to the selected view mode.
  • Rem. estimate: Shows the remaining estimate summed up according to the selected view mode.
  • Logged work: Sums up the logged work time of the issues according to the selected view mode.
  • Difference: Shows deviations - difference = orig. estimate - rem. estimate - logged work
    (Glühbirne) Check out example below!

(Click to enlarge)

Detect deviations from original estimates easily!

If a sprint is started and the team would raise remaining estimates this is highlighted in column difference. The team can check and discuss these cases in dailies for example.

  • Keine Stichwörter