Adapting Agile User Stories to role based application design

15 Mar 2011 - 8:27am
3 years ago
1 reply
1424 reads
Powers
2008

How do you handle writing user stories for system that contain numerous roles that have different permissions? It seem that when adding roles to system, the number of user stories is multiplied by the number of roles to address differences in every interaction. 

Comments

15 Mar 2011 - 9:53am
holger_maassen
2010

I prefer to use interaction diagrams when I want to look at the behavior of several users, several roles and several objects within my project / application development processes.

Interaction diagrams are good at showing collaborations among the circumstances and tiny elements - they are not so good at precise definition of the behavior.

If you want to look at the behavior of a single object across many use cases, use a state diagram. If you want to look at behavior across many use cases or many threads, consider an activity diagram. On the other hand if I have to consider various situations local, mobile or offline I like to use swimlane diagrams.

And I love working with personas - eighter very easy and rough one or detailed one.

Perhaps these articles might be helpful ...

http://ux4dotcom.blogspot.com/2009/10/why-personas-matter.html

http://ux4dotcom.blogspot.com/2010/08/walk-while-in-someone-elses-shoes.html

http://www.boxesandarrows.com/view/ux-design-planning

Syndicate content Get the feed