---
# System prepended metadata

title: Product Process
tags: [liquid]

---

---
tags: liquid
---

# Product Process

#### table of contents https://hackmd.io/zQPqhKiESUuh-6tXREXDaQ

---


Label Explanation:
 
 
1. Issue Size:

General explanation over the work needed to complete the issues.
Uses a linear scale i. e. 2 S issues is equivalent to 1 M issue.
The time required does not need to be really specifically set because shit happens.
Tshirt estimates used for issues size:

* S  - small issues - easy to fix - 2 - 4 hour needed
* M - medium issue - 4 hours - 1 day work
* 
* L  - large issue - 1 - 2 days work
* XL - larges size - more than 2 days of work

2. Issue Type:

Defines the nature of the work required to complete the issue.
Issue types used:

* New Feature - This is a new feature that needs to be added. The work will start from scrach.
* Enhancement - This is an improvement to an already existing feature. i. e. a new capability is added
* Bug - This is a bug present in an component. In certain scenarios an unwanted behaiviour appears.
* Ops - task related to the app deployment or CI/CD pipeline
* org task - everything that does not fit with the other issues, i. e. migrate database information

3. Priority:

Defines how important is an issue to be fixed.
Priority Types used:

* Low - not a priority, can be added to a release if bandwidth is available
* Major - mojor issue, should be included in a release but not neccessary
* Critical - critical issue, should be fixed as soon as possible but it does not block a release if a Critical issue is present
* Blocker - the most important type of issue, a release will be delayed if a blocker issue is present

4. Component:

This describes the different components present in the application

5. Subcomponent:

This describes the subcomponent UI or backend for each component

6. Themes:

Defines the general reason for doing the feature.
Possible values:

* Capabilities - the issue will add a new capability to the user, i. e. I can now have a different type of email
* Usability - the issue will improve a preexisting capability or improve the general user experiance
* Security - the issue will improve the platform security
* Performance - the issue will improve the platform security 