There is a lot of reluctance within organisations to place ScrumMasters, let alone to spend money to hire them. Surely this role can be done by one of the developers, right? After all, it’s only a minor role, isn’t it? Far from it! The ScrumMaster is a full-time role. Without it, who can take care of the agile process on behalf of a busy Scrum team?
One way to help teams and management understand the value of the ScrumMaster’s role is to show them the volume and importance of tasks a ScrumMaster can fulfil, and the consequences of what happens if nobody takes care of these tasks. This session not only presents the 42 tasks of a ScrumMaster’s role but will clearly show that every Scrum team needs a ScrumMaster.