Your management is concerned that your team does not have a complete set of user stories. The first problem is low recall, i.e., the team is not capturing all the user stories the customer needs. The second problem is that without not enough work, the organization will have to let some of the team members go cut everybody's pay.
The customer met with their team and returned with a list of potential user-story titles. These possible new user stories fall into one of the following categories:
| Code | Description |
|---|---|
| A | Already have as a user story |
| N | Not a user story title |
| P | New, but needs to be converted from plural to singular |
| S | New, but needs to be split into multiple stories |
| X | Not part of the description |
On the provided sheet, code each of the user stories into one of these categories.
Create a new user story, or multiple user stories, for each of these valid potential user stories. This includes fixing any title issues and adding a description. Also, take this time to fix any existing user stories.
Each team member will turn in both of the following:
If you have any additional time, then create more estimates. As you did before, keep track of details for the next team meeting.