1. What users most need ASAP
2. A word on Roles and User Stories

1. What users most need ASAP

Due to popular demand, the following user story will be moved up to top priority along with the need to easily and conveniently visualize all content created in a project:

A Product Owner can invite people via e-mail to become Team Members of a Project

This will be automated via a custom form: if you provide the email of an individual, that person will become a Team Member of your project. You will also be able to promote any Team Member to Team Leader.

The word "owner" has been confusing for some of you. When editing a User Story, one feels the need to assign it to an owner since that field is first in the form. However, the concept of ownership of user stories is only for when a User Story is being implemented and has been assigned to a Team Member, with the idea that there should always be someone responsible for a User Story while it is being implemented. There is no need to assign the User Story to anyone while the Product Owner (that's you) is writing the User Story.

2. A word on Roles and User Stories

Once you have created your roles, and have exhausted (for now) the list of all possible kinds of people who may interact with your website application, the next step is to create, for each role, all the possible ways that class of individual may interact with the system. That is, to create all the possible user stories for each role.

When you have finished doing that, you have covered all requirements! And no other tasks (how are we going to implement the news feed aggregator) should even be thought about (much) until this task of tasks is done with.

The best way to do this is to add user stories to roles as you think of them, instead of obliging yourself to sequentially tackle each role in turn. Of course, once you start, it is only natural that for any given role you are going to add two or three user stories at any given time.

You are most likely going to follow these steps:

1. Go to the main project page.
2. Check out the list of roles you see there.
3. Click on one you want to work on.
4. In the Link target section, click on the big blue MAKE TARGET button.
   Now, whichever user stories you write can be linked to this role.
5. While creating the new user story, be sure to select the checkbox linking it to the parent role.

On the one hand, this is clearly a pain in the... neck. On the other, it does make you conscious of which role you are working with, and which context you are working within.