Frequently Asked: Story points in team of experts

Should you use story points for a team of developers developing multiple systems? The situation This question was asked by scrum masters who's teams are not ideal agile teams as the company introduces agile in multiple steps. Their team typically consists of experts focused on web, ledger, back- ends PHP / Java. They are [...]

ScrumDesk 6.29.1: Improved Root Cause Analysis Editor + Kanban

Root Cause Analysis Editor We are glad to see more and more (and especially experienced) agile teams use the Root Cause Analysis editor to build a shared understanding of the reasons for their impediments. This way agile teams can focus on the true cause of the problem instead of solving some indicators. In this [...]

De-bugize! Plan bug fixing in Scrum

Are you distressed by the huge amount of defects in the product? In this article, you will learn about what practical possibilities you have in agile teams and managing error correction. One of the first questions that pop up whilst introducing agile is how to deal with errors. Too often I hear an immediate answer: [...]

ScrumDesk 3.5: Instant Tasks Sync, Cumulative Flow for Kanban, Work logs, History

Instant synchronization of tasks The board is alive finally. Adding new tasks, changing them, moving, cloning, or deleting them will update the Kanban boards of all team members in seconds. Just change them and everybody sees the same. Cumulative Flow Chart The Cumulative Flow Chart enables Scrum Masters to identify gaps in the process. Teams [...]

ScrumDesk for Windows: API Attachments Limits

REST API is in Microsoft Information Server configured by default to transfer binary data of maximum size of 65KB. The size is configurable by parameter maxReceivedMessageSize in web.config file located in API directory. <standardEndpoints> <!--Defines a standard endpoint with a fixed <webHttpBinding> binding that automatically adds the <webHttp> behavior. Use this endpoint when writing a [...]

Scrum Glossary: Scrum Roles

Pig & chicken Metaphor that helps to distinguish people actively involved in development of the product and people who should not interrupt the team in an iteration. Product Owner Father of the product. Responsible for product success. Provides a vision to the team. Communication channel between the team, stakeholders and customers. Responsible for: product [...]