Role management

Overview

Every people getting a login / password to connect to theSCRUM will have read-only access on all the content: there is no restriction per project, it then favors transparency across the project and the teams. If this transparency per project becomes an issue to use theSCRUM, then you can either control who has login access; or set up different instances of theSCRUM, to isolate some particular projects.

theSCRUM supports four different roles:

• Administrator, to manage projects and and set up teams
• Product owner, mainly to manage the product backlog. Several product owners can be defined per project: while this is not recommended in the Scrum methodology, this helps dealing with holidays.
• Scrum master, mainly to manage the sprint backlog. Like for product owners, several scrum masters can be defined per project.
• Team member, to manage tasks inside the whiteboard.

Role matrix

Here is a more precise description of each role. “product owner” and “scrum master” roles are quite the same; indeed, through usage, we found out working with the team and using theSCRUM to do the poker planning or sprint planning… it is useful to be able to change the product backlog or the sprint backlog without logging out / logging in.