# Payvoicing Grooming

**Disclaimer 1** - These are general guidelines not strict rules
**Disclaimer 2** - I have a "Scrum Master" role defined in the document which I know may be a loaded term with different definitions. In my mind this is just a point of contact for this whole process to keep things moving and organized. I don't see this as a full-time job.

**Motto** - Clear the pipes and keep the sludge moving - Frank Underwood

## Roles

- `SM` - Scrum Master - Point of contact for this process
- `PR` - Product
- `UX` - UX
- `EN` - Engineer
- `QA` - QA

## Ticket Types

- Story - Description of user facing change
- Epic - Collection of stories
- Subtask - Engineering specific tasks

## Status Descriptions

1. [Backlog](https://procoretech.atlassian.net/secure/RapidBoard.jspa?rapidView=545&view=planning)
- Ball-in-court: `PR` or `UX` create stories, `PR` prioritizes stories
- Exit criteria: `SM` pulls story into grooming backlog
2. [Grooming](https://procoretech.atlassian.net/secure/RapidBoard.jspa?rapidView=545)
- **Grooming Backlog**
- Ball-in-court: `SM` prioritizes stories
- Exit criteria: When **In Commenting** clears up
- **In Commenting**
- Ball-in-court: `EN`, `QA` ask clarifying questions and create subtasks | `PR`, `UX` respond to questions and create acceptance criteria
- Exit criteria: Questions answered, subtasks created, acceptance criteria created
- **Needs Pointing**
- Ball-in-court: Everyone
- Exit criteria: Stories pointed
- **Groomed**
- Ball-in-court: No-one
- Exit criteria: Pulled into active sprint via sprint planning
3. [Active Sprint](https://procoretech.atlassian.net/secure/RapidBoard.jspa?rapidView=453&projectKey=CF)
- To Do
- In Progress
- Code Review
- Ready for Testing
- In Testing
- Passed Testing
- Merged
- Done

## Meetings

- Sprint planning
- Every other Fri
- Mid-sprint checkin
- Every other Fri
- Discuss progress of sprint
- Pull tickets in/out as needed
- Grooming
- Scheduled on Ad-hoc basis **subject to change**
- We can make regular meetings if needed