Agile Scrum Roles & Permissions

[Stephen Lynch]

I am looking for a detailed description of each of the agile scrum roles and what permissions each of them have at a detailed level. Where would I find this information?

[Rick Kuijpers]

Since the scrum_user role is automatically assigned to users who are made members of an Agile Group (sys_user_group record of type Agile), I was expecting this, as you described. However, in my PDI and in my client's instance, the scrum_user role only gives Read-permissions to agile tasks (stories, epics, ...). This is confirmed by the documentation: 
A scrum user can view all elements of agile, but cannot create, edit, or manage records of any type.

With the scrum_team_member role, the user is permitted to create and edit agile tasks. As the documentation states for this role:

• Users with this role are the scrum users who work on a story in a sprint.
• A team member can create a scrum task, perform updates to a story, and log enhancement requests or defect reports.
  

I verified in my PDI, the roles work as documented. With only the scrum_story_editor role, a user cannot create stories, but they can edit existing stories. They can also not create or edit other agile tasks like epics.

With the scrum_story_creator role, a user can create and edit stories, epics and tasks.

So in short: the documentation is correct 😄

https://docs.servicenow.com/bundle/tokyo-it-business-management/page/product/agile-development/refer...

I could not find clear documentation stating that, and why, a newly create Agile Group is only assigned the read-only scrum_user role. To me it would make more sense for an Agile Group, which could be a Scrum development team, to be allowed to at least edit stories while they are working on them.

But with the granularity of the different roles it's easy to assign privileges to different groups according to your needs.

[KV_CTS]

Correct and FYI - Latest update (as of Yokohama release) - Components installed with Agile Development 2.0

[marilynfrancisc]

Hello All! I have a related question and I was wondering whether anyone is familiar with the role specific to editing the Visual Task board, where it allows you to move Scrum Tasks from one Status to another. I tried ALL Scrum roles but nothing works. 

[phil bool]

When you make an edit to a record via a Visual Task Board, it's the same as if you'd made the changes directly to the record.  If something is preventing you making those changes, then it may be that you're changing more values than you realise when you move the record from column to column.  
If your columns are determined by the record's state, for example, have a look to see if there are constraints on who can change state and when.  For example, if someone is trying to move a Story to the column that represents the Ready state but the Assessment Criteria isn't populated on that story, that change will fail regardless of the user's roles.