If you didn't find what you were looking for, try a new search!
Self-organized teams are fundamental to the success of agile approaches. But what does self-organization means? 5-6 years ago we started to introduce agile to CxO of multiple clients. I remember that the most unbelievable for them was a term self-organized teams. Well, it was unimaginable to see people working without any Mr. Commander. Without [...]
Prioritization by Business Value Prioritization in Agile is considered from the customer's perspective with help of MoSCoW. This is not enough for the commercial company. You need to survive, to pay bills, to pay the next sprints. You have to think about features from the perspective of the company as well. Business perspective This prioritization is [...]
The first blog post about prioritization was focused on MoSCoW - prioritization of the backlog from the perspective of customers. This is not enough for the products development of the commercial company. You need to survive, to pay bills, to pay the next sprints. You have to think about features from the perspective of the [...]
MoSCoW backlog prioritization Prioritization is probably the most discussed part of development processes. Product backlogs are often quite complex with hundreds of requirements. How to find user stories in your story map which you should start developing first? Traditional approach The approach of traditional processes is simple. You have high, medium, low priorities. Ok, [...]
Account Settings Every organization using ScrumDesk has its own organization account. Details about the organization are used for the billing process so please fill them up accordingly. Account details are accessible from the menu item Account settings are displayed by clicking on the user avatar in the left menu. As your user account can [...]
How to deal with complex tasks In Agile there are multiple approaches how to dealing with the complexity of software development. Some companies prefer to break down user stories into subtasks. Such companies are more focused on creative work where Scrum is very helpful. The type of subtasks is even predefined in some Definition of [...]
This version fixes v.5.5 published the last week: Burn-down charts were not displayed correctly in some cases (i.e. sprint backlog contains stories with a long history). Fixes of the synchronization in five different cases (the first update in a day, update of a story in case tasks are changed, etc.). Minor visual improvements of [...]
We published new ScrumDesk update that brings: Improved synchronization of story tasks [Fix] Cards are not displayed for newly created tasks [Fix] Negative values in burn down charts
Thanks to all our customers who sent us very positive feedback on the last version supporting simultaneous editing of tasks. And thanks to customers who informed us about issues we did not identify. In the newest version 5.4.12, we continuously focused on improvements of background synchronization. Sync interval shortened to 1 second, changes are [...]
Scrum is a framework typically adopted by every company. ScrumDesk allows customizing it according to needs. Customization Release types allows defining how important is the release and where will be deployed Release statuses. Companies track the status of the releases, therefore, they need to define statuses to be used. Story types. A story in [...]
