Module 2 - User Roles

When you define groups of users who share common behaviors and system expectations you are defining:?

• Users
• Users Roles
• User Situations
• User Qualities

Which of the following criteria are important to consider when creating user roles?<br />

• Physical Environment in which the user will interact with the product<br />
• Complexity of work the user role will perform<br />
• How often the user will interact with the product<br />
• Requirements for the user role to have a successful user experience<br />

Once the group has brainstormed an initial set of user roles, what’s next?<br />

• Refine - eliminate unimportant roles<br />
• Organize - Re-arrange so that similar roles are together<br />
• Consolidate - Look for roles that can be combined<br />
• Define - Fill in additional details for a role<br />

When is it appropriate to write a story from the perspective of the system or development team members?

• Occasionally. Use them cautiously and first attempt to frame the story as a user request<br />
• Always. This perspective makes it a lot easier for developers to meet its requirements <br />

You’ve written a story describing how the system behaves when members log in. Now you need to account for forgetful users who need a password reminder. What is the recommended approach?

• Add a forgetful user role in your user role model and write a story about this role
• Add the word “Forgetful” to your member role just in the login story but do not create a new role
• Add a note to the member story explaining in some cases that the user will need a password reminder