Kubestro

# Workflows

The Kubestro project’s workflow is strongly inspired by Agile and SCRUM methodologies. Although we don’t run Sprints or engage in daily or weekly planning, our issue management practices are still heavily shaped by these principles.

For clarification, here is the list of the different types of issues:

* **Epic**: This is the highest level. It can be split into smaller *User Stories*. It is often defined by a business objective or a functional capability.

  For example: "Billing management" or "Notification system". An *Epic* can live upon multiple versions.

* **Feature**: Sometimes a *feature* can be equivalent to an *epic* (a functional scope), other times it locates between the *User Story* and the *Epic*: it describes

  a feature that still requires multiples *User Stories* to be implemented.

  For example, in an *epic* "Billing management", a feature could be "Billing through credit card".

* **User Stories**: This is the work unit the most used in Scrum. It is expressed from a user perspective, often using the following template:

  "As a [role], I would like [action], in order to [gains]". The story has to be small enough to be finished in a short time (a single *sprint*).

  For example: "As a customer, I would like to be able to save my credit card details so that I don't have to enter them every time I make a purchase."

* **Sub-Tasks**: This is the finest level. A *user story* is often split in multiple *sub-tasks* when it requires several distinct technical actions: "Create

  API endpoints", "Implement client-side validation", "Write Unit Tests", etc.

  *Sub-Tasks* are generally assigned to individual developers and aren't supposed to be planned independently. They are bound to their parent *User Stories*.