Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  Permission-Based Roles in User Stories
Previous Previous
 
Next Next
New Post 6/19/2016 8:16 PM
Unresolved
User is offline Mister Octopus
1 posts
No Ranking


Permission-Based Roles in User Stories 

Hi there. Forgive me for a potentially newbish question (I'm just starting out in the world of analysis):

With user stories, I know that it's good practice to give your "As a user..." section a specific role or persona to help explain the context of the user story. I'm currently writing user stories for a system where we have a handful of different roles who all have different viewing/editing permissions throughout the system. Most of these permissions cross over between the roles, so I'm wondering how to approach the user stories. Obviously, I don't want something that looks like:

"As an administrator, team manager or operator, I want to be able to..."

What is the best way to approach this? Do I just repeat the same story for each role? Do I use a generic "As a user with the correct permissions, I want..."?

Currently I have these stories simplified to "As a user, I want..." and then I have a final story that says:

"As the system, I must only allow users to perform actions as defined by their role permissions."

Is this an acceptable way to go about this, or am I approaching this whole concept wrong?

Thanks in advance!

 
New Post 6/20/2016 2:54 PM
User is offline NitWitNick
259 posts
5th Level Poster


Re: Permission-Based Roles in User Stories 
A User Story Alone Is Really Not Enough ...


A User Story quickly states what the user wants to do with the system at a high level ... So, "As a user...", is a very short description of a feature needed by a user.

And

A User story Does NOT replace Detailed requirements. A user story is basically used as pointer to those detailed requirements ... and it is hard to define both functional and non-functional details by just a user story.


Don't Get Hung Up On Thinking You Will Just Write User Stories ... You Need Detailed Stuff To Develop From ...

 

As I stated Before ... I do consulting and have Never seen a 100% Waterfall or a 100% Agile environment ... most are a Hybrid of various stuff.

 
New Post 3/2/2017 4:17 AM
User is offline sutnarcha
7 posts
10th Level Poster


Re: Permission-Based Roles in User Stories 

Agreeing with NitWitNick by-and-large, I want to add the below...

I always write user stories like "As a user with permission to xxxx...", and who has permission or what role has permission to xxxx... is a different reference document.

 
New Post 4/17/2017 7:26 AM
User is offline Patrick Schmöllerl
5 posts
10th Level Poster


Re: Permission-Based Roles in User Stories 

As you have already guessed, it is not always wise to describe everything in a user-story-like fashion. Every method has its use and purpose.

In a way it depends on the set-up of your project and your responsibilities, but what I like to do when describing the more detailed impact of permissions and roles is these 3 steps:

- Describe the user-story in a way: "As an administrator, I want ... " so the idea of who should be allowed to do what is commonly understood.
- Add a more detailed description for development in the form of: "IF the user does NOT have the permission xyz, THEN ..."
- Add a very seperate and standardized work-item for the user-administration or whoever does that in your organisation: "Add permission X to role Y. Add permission X to role Z. And in case the set-up allows it: Add role Y to user Patrick", etc.

 

 
New Post 5/10/2017 11:38 PM
User is offline Kimbo
438 posts
5th Level Poster


Re: Permission-Based Roles in User Stories 

Dear Occy

Another suggestion: write your user story 'As a user I want etc'. Then in your acceptance criteria write a series of scenarios for each role. I use gherkin from the BDD camp to specify scenarios for acceptance criteria. Works well

Kimbo

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  Permission-Based Roles in User Stories

Community Blog - Latest Posts

Dan Tasker
Dan Tasker
  In Part 1 of this series it was stated that the overall objective of these articles is to improve the quality of requirements produced by business analysts. Following the adage that “Context is Everything” it established that a number of different contexts...
4 Responses
Alice Bolingeryn
Alice Bolingeryn
Clearly, the most important step in getting a job is being selected for an interview, and a key part in that process is having a resume that stands out from others.   For many people, creating a good enough resume is an obstacle in achieving this, and so one way to address this problem may be to get a professional to create one for you. J...
0 Responses
Arash
Arash
It may sound routine, but the importance of operational decisions cannot be underestimated. After all, not a day goes by without even the smallest business making dozens, if not hundreds of operational decisions that may affect the bottom line. Elevate these to large scale companies and we are talking thousands, if not millions of actions that impa...
0 Responses




Latest Articles

Copyright 2006-2019 by Modern Analyst Media LLC