ver 4.0.5 (July 17, 2009) :: ScrumDesk – scrum project management tool

ver 4.0.5 (July 17, 2009)

Posted on 29, Sep 2010

Version 4.0.5 is focused on top critical problems, few new features and performance optimization.

We are using .NET 3.5 platform now!
Download it from here.

Version 4.0 is not upgrading previous ScrumDesk installations!
You have to uninstall previous versions and install v.4.0.5.

Offline license mode for 29 days

We’ve changed our policy and let users to run ScrumDesk in offline mode not just for 5 days, but for 29 days. You must ScrumDesk let connects to our licensing server at least once per 30 days.

Logic to access licensing server has been simplified to prevent problems.

Note: If you are using proxy, don’t forget to set credentials in Login window!

Non-working days

Saturday and Sunday were skipped as non-working days. Based on requests (mostly from Arabic countries) we’ve implemented possibility to configure which days are non-working days in a project level.

Non-working days are going to be skipped in reports and charts.

Go to Project/Settings/Calendar to configure non-working days.

Operator is changed to logged team member

To save click during interaction with the application, ScrumDesk automatically assigns changed items to logged user. This way you don’t have to care if you’ve updated your name in touched items.

This interaction model is sometimes not usable. If you are using model when only scrum master (BTW. is this Scrum?) is updating common taskboard. In this case Scrum Master should un-check Re-assign story/task… check box. Scrum master can still assign story or task to himself in Detail window.

Change of Effort

ScrumDesk provides validation of correct usage of Scrum. Effort was allowed to change only before the sprint has been started. Some companies are using different usage model and based on it we’ve allowed to change effort by scrum master anytime.

Keep Window State

ScrumDesk was starting maximized every time has been started. Since this version, ScrumDesk remembers the size and the last position so you will find it exactly as you closed it.

Release completeness %

Release is currently tracked by percentage of completeness. The number is calculated  using formula 
# of completed stories/
# of all release stories.

Product owners have an easy access to check this metric in Reports page.

Color of team member name to indicate role

Previous version display role under Project name and the name of logged team member in a tooltip. Now name of team member is preferred to be displayed, color indicates its role.

Minor changes

  • SideView
    • Question before sprint is started – do you want to start sprint and it is estimated? This is prevention to have burn down charts accurate/
    • SideView/Project – buttons Call, Email, Web were not visible sometimes
  • Reports
    • Project Status Pie chart not updated
    • Absences are accessible in Reports
    • Impediments are accessible in Reports
  • Fixes
    • Filter by Tags not working sometimes
    • Concurrency message – message warning user that someone else has changed story/task was displayed as an error. It is warning now.
    • Error message box is displayed in case of connectivity error so error could be sent to our support
    • Team member in Login window – renamed User name label in Login window to distinguish it from user name used to connect to database
    • Filter – Highlight my items was forgetting its setting. Fixed.
    • Performance optimization