# Project Management

# Creating User Stories

User stories are short, simple descriptions of a feature or bug told from the perspective of the person who desires the new capability, usually a QA tester or client. The following is a typical workflow:

1. A client sends a change or bug request to the project manager.
2. The project manager reviews the request:
   1. Determines if it's valid (can reproduce, client has hours in budget, etc.)
   2. Gather's all details, designs, needed functionality, etc.
   3. If needed, speaks to the developer to find possibilities, get estimates, review requirements
   4. Gather's all needed details:
      1. URL of the request
      2. Screenshot if possible (before/after, design vs. implementation)
      3. Use cases not considered like functionality & interaction states
   5. Parses the request in a short, descriptive user story:
      1. As a type of [type of user], I want [some goal] so that [some reason]
      2. When a [type of user] does [action] on [location], it should [action], instead it [action]
      3. Numbered list of related items such as minor QA issues or content updates
      4. Avoid non-specific requests such as, it looks weird, add more space, should be bigger, etc.
      5. Include layered designs and/or detailed specs such as, font sizes, aspect ratios, etc.

# Assigning Stories

1. Once created, the project manager should determine:
   1. the sprint
   2. priority of the request
   3. link any related or blocking stories
2. If incomplete, awaiting details, or otherwise not ready to be worked on, assign to the project manager
3. If complete, ready to be worked on, assign to the appropriate developer

# Story Workflow & QA

1. Each morning developers should review the assigned stories in the To Do column & make note of any questions/concerns to go over during scrum.
2. Once a developer begins to work on a story, they should move it to the In Progress column in Jira.
3. After completion, the developer should comment on the story with a link/location of the change, then move to the QA / Approval column.
4. The project manager should then review the update, & determine if all is good or needs additional work.
5. If needs additional work, comment with those details and move back to the To Do column.
6. If approved, move to the Approved / Ready for Live column.

# Deploying Stories

Once a batch of stories has been moved to the Approved / Ready for Live column & it's time to deploy those changes:

1. The project manager creates a deploy story, links all approved stories to it & assigns accordingly.
2. Once the deployment has been completed, the developer should comment on the deploy story then move to the QA / Approval column.
3. The project manager should then test the deployed changes & if all looks good moves the deploy & all linked stories to the Done column.