1. Once a request is submitted, it will go into our request backlog.
2. Every so often, we review our backlog to triage and refine requests. We do this to make sure requests are actionable, can be delivered in a timely fashion, and contain expected requirements.
3. After a request has been refined, it is ready for work. Note this is NOT a promise to work on it.
4. Every so often, we review our queue in order to plan our roadmap.
5. If we have available capacity, your request is ready, and aligns with an OKR, then we will place the request into our accepted queue.
6. After the project is in our accepted queue, we still need to assign resources to work on it. Once resources are assigned, we can begin work.
7. The issue will then be reviewed by a stakeholder, a reviewer, and iterated upon until approved.
8. When a request has been completed, it will be marked as Done and show up on ‣.

Why can't you work on a small request right away?

1. Unfortunately we get multiple of these requests every day. When we do unplanned work, then we cannot deliver all of the work we planned. That said, it doesn't hurt to ask. We might have availability.
2. Your request might only take a few minutes to implement, but there is additional overhead in context switching, creating issues + merge requests + branches, testing procedures, reviewing, and verifying releases.
3. If you have an emergency then please do let us know. Please be aware that whenever new work is brought into a sprint, other work is negatively impacted. Your request might be important, but we still need to weigh the importance against other projects.