---
# System prepended metadata

title: Velocidi Engineering Guidelines

---

# Velocidi Engineering Guidelines

## Purpose
Define how the engineering team operates.

## Meetings
Every Friday afternoon one of two meetings happens, interchangeably. On one week, we hold the *backlog trimming*, on the other the *sprint planning*. 

### Backlog Trimming
We work with product to break down features into engineering tasks and estimate those tasks. Smaller features can be converted directly into Github issues, larger ones are converted to a Github issue that is marked as an epic and smaller issues associated to it. We then estimate each of these individually.

### Sprint  planning
This meeting has a moderator and goes through three phases: sprint review, prioritization, and sprint planning. 

During the **sprint review**, the moderator asks each member to share details of their sprint, while sharing the planned sprint (filter zenhub by person and milestone). Each member shares their contributions during the sprint. 

During **prioritization**, a stakeholder from product reviews prioritization with the team and defines the product priorities for the upcoming sprint. If a non-estimated feature is prioritized at this time, the team estimates it before moving forward.

Finaly, during the **sprint planning**, the team goes through the process of accepting new work items for the following sprint. We have to decide effort allocation between engineering and product tasks. Product tasks are always accepted by their order of priority, until everyone has their sprint defined.