The reason to improve the SDLC is to speed up value delivery end to end, from entering the sprint up to delivery ready for certification, if applicable. The scope that does not require the certification testing is supposed to be delivered fully to production.
Ultimately, we want to deliver the pre-agreed value at the end of each sprint.
Sprint completion ≥ 80%.
Sprint completion is calculated as the number last 6 sprints that have delivered the sprint value.
Sprint value is a Story chosen at each sprint planning meeting by the team, labeled by the “goal” label in Jira.
The goal is to simplify and unify the ticketing flow in Jira for both discovery and delivery phase, starting with delivery:
Classification of work is important for greater transparency of what is needed to deliver continuous engineering quality.
Issue types used by Engineering are summarized in the table below:
| Issue type | Description | Examples |
|---|---|---|
| Story | Stories represent user-centric features or functionalities. They are typically written from an end-user perspective and describe a piece of work that adds value to the product. | Implementing a new login mechanism for improved user security. Implementing delivery location pin on both backend and frontend as this can be achieved in a single sprint. |
| Task | Tasks are smaller units of work that contribute to the completion of a story or a larger goal. They are usually more technical and specific than stories. | Configuring a server to support the new login mechanism. Implementing enabling early delivery in order tracking. |
| Research | Research work involves investigating and gathering information to make informed decisions. It is often performed before starting a new project or when facing technical challenges. | Researching the best encryption algorithms for data security. Design solution for switch between summer and winter time for slot-management. |
| Defect | Defect work involves identifying, troubleshooting, and fixing issues or bugs in the system. It is reactive and aims to resolve problems discovered through testing. Defekt i related to issue to tested feature and should not occur on production. Production issues are Incident | Fixing a bug that causes the application to crash under specific conditions found during testing |
| Incident | Issue, bug or a problem in general occurring in production. | Disfunctional product detail link. |
| Operations | Maintenance work involves the ongoing tasks required to keep the system running smoothly. It includes routine updates, bug fixes, and general support. | Optimizing database queries for faster response times. |
| Problem/Postmortem Followup | If an issue is a followup raised based on a postmortem, it should be marked with this label so that we ensure timely resolution. |
A big initiative spanning multiple months, usually tied to roadmap or OKRs using the roadmap label, ie. 2024Q4. A collection of epics.