Retrospectives

Retrospective Sessions

Does your team like the retrospective format and use it even for non-retro brainstorming workshops?

Create a retrospective session to keep all session ideas in one place. Every session might have a retrospective theme assigned so the team knows what to focus on in their brainstorming.

Retrospective session

Retrospective filters

Great agile teams are able to provide hundreds of ideas after a couple of sessions. Scrum Masters and team members usually work further with retro ideas thus orient might not be easy over time.

ScrumDesk enables to filter ideas either based on the retro idea implementation status, assigned person, or based on votes provided by the team in sessions.

Retrospective ideas filter

Retrospective idea tags & history

Now you can mark retro ideas with tags to further categorize them maybe by team, role, location, project, business unit, or by customer.

Sometimes it is also good to see who changed what, therefore retro idea changes are tracked too.

Objectives & Key Results editor

Objectives and Key Results method works very well with Agile practices for the development of great products. OKR editor in ScrumDesk application help connect objectives and key results to other project assets and provides a continuous overview of the project progress.

The latest ScrumDesk edition gives product owners control over tracking of objectives status (To do, In progress, Completed, Accepted, Rejected, Canceled).

Even the objective is in progress, the objective confidence of the team members can indicate the achievability of objectives early.

Objectives and key results status and confidence

Progress calculation

Progress in ScrumDesk was calculated as a combination of the progress of related items and the key results. The real-life shown the necessity of multiple scenarios for the progress calculation.

Therefore in the latest version user can choose the best scenario that fit the business model:

  • Progress based on the progress of the key result and all relations.
  • Progress based on relations only that fit the agile product development where key results follow the progress of related epics automatically.
  • Progress based on key result progress only where backlog items can be connected to the objective, but the progress is tracked manually.

Maximum value that the team should achieve can be requested as precise or at least.

ScrumDesk OKR progress algorithm

We also added ‘increase by’ and ‘reduce by’ to the list for key result maximum value.

Root Cause Analysis Desk improvements

Many users use ScrumDesk RCADesk to draw mindmaps or use the tool in brainstorming sessions to track ideas and analyze them deeper.

This version enables to draw multiple arrows in case of multiple relation types and also set start and end arrow type to distinguish them in more complex diagrams.

Additionally, fonts can be set for links.

ScrumDesk Root cause analysis arrows types

Login via GitLab, GitHub, BitBucket

With this update, your team members are able to sign-up and login via popular development tools including GitLab, GitHub and BitBucket.

Login to ScrumDesk via GitLab, GitHub, BitBucket

Timesheet report

We added new options to filter timesheet by theme, backlog item type, or task type that were referenced in the work log records evidenced by team members.

Now you can also display the previous or next month easy by click on < or > arrows displayed near dates.

ScrumDesk timesheet report filters

The summary information includes billable vs non-billable comparison for every group and total summary.

Based on users’ feedbacks we also have hidden team members without any work log in a given period.

Minor changes

New functionalities

  1. STORY MAP
    1. Display Unassigned panel epic only when necessary
    2. Add epics from the map directly, removed + toolbar button
    3. Waiting flag for epics.
  2. Project settings
    1. Use SPLIT and CLONE prefixes
    2. Multiline string custom field type
    3. Sorted GROUP BY and SORT By values
    4. Billable flag in the Templates
    5. Minor styling changes of the Projects list
  3. General
    1. Share a link to a work-log record
    2. Share the link to a comment
    3. Direct open of comment via URL
  4. Objectives & Key Results
    1. Archived OKR is not displayed in the OKR Overview Chart
    2. Add additional Key Result and Remove Key Result commands added to the local toolbar
  5. PLAN
    1. Click any sprint information to access the full sprint details panel
  6. Sprint Report
    1. Don’t display guests on the list
    2. Removed ‘_’ in roles titles
    3. Display sprint details on click on the header
    4. Display backlog item details on click anywhere on the table row
    5. Indicated backlog item types

Fixes

  1. Retrospective ideas don’t load.
  2. The capacity planner doesn’t display.
  3. Picture thumbnail not displayed upon upload for subtasks.
  4. Files view displaying hundreds of images was loaded for a very long time.
  5. Product ownership reports are not displayed in Firefox.
  6. Slack: subtasks not always added from the Slack channel.
  7. Empty tag cloud in the filter.
  8. Set up the backlog item type after the conversion of a subtask.
  9. Long theme title breaks UX.
  10. Cloned task displayed after refresh only.
  11. Export button visible only partially in the Story Map.
  12. Dark local menus for a few charts where they should be displayed in the light scheme.
  13. Sprint Report: Hours (Spent) to Spent (hours)
  14. Worklog by backlog item types doesn’t show always properly in the backlog item details.
  15. Retrospectives: loading of retro techniques was not successful in all cases.