Agile Devlopment 2.0 Products/Stories/Epics/Themes

[davidsmith]

Hello,

We are starting to make extensive use of the Agile module in ServiceNow. We have two teams that are using the module. I am curious to see how other have setup their Agile module. At the moment we have given most of our user the scrum_admin and scrum_master roles. We are starting to pair access rights back to the bare minimum. 

In our scenario we have Team1 with a set of products/stoires amd Team2 with a set of products/stories. At the moment each team can see each others products. How do you restrict access in this way?

Thanks in advance.

David

[Bradley Ross]

We use lots of teams with lots of products and letting everyone see everyone else's products hasn't been a problem. The way the agile boards work, they filter down the list of stories so you only see the stuff assigned to your own team. Further, personal backlogs can be used to filter the list of stories to just the few products you care about seeing. 

On the product (application model) record, you can edit the related list of groups. This will limit the choice of assignment groups available on a story record after you select a product, but that is the reverse of what you're looking for. Many of our scrum masters use record templates to quickly fill in the product field, the assignment group field, and some other custom fields on our story records. That saves them from browsing a long list of products or groups. 

I guess I'm only answering your first question to say that we have had good success with the out-of-the-box functionality. Perhaps others will have good ideas about your second question about limiting the access to other stories, perhaps with a scripted ACL.

[davidsmith · Accepted solution]

Dear Bradley,

Thanks so much for your response. It is good to hear how others are using the Agile module. Our teams are from different departments but they are essentially doing simliar work so I can't see it being a problem if other peope see each other's products. There will have to be a common consensus between department heads that thety can see each others products but don't touch. As you say mpost people will hopefully make use of the Agile Board to see their own work. What we might also do is to give individual limited access (so if they onbly need to use Enhancements, just give them access to those).

One question I would like to ask is how you make use the the scrum_admin and scrum_master roles?

Kind regards

David 

[Bradley Ross]

We give the scrum_admin role to all our product/service managers and all our scrum masters (which we call agile coaches). Everybody else gets scrum_team_member. The only thing I don't like about this arrangement is the triage boards aren't accessible to team members. Thus, only one of the people with a higher role can triage in an incident record to the story board.