SLA for Software Teams
The standard SLA module in Jira Service Management doesn't allow measuring time to resolution in Jira Software projects. This is a pain point to many scrum masters and project managers, who can't precisely calculate the time spent on development. This can be sometimes worked around using heavy scripting, but it's neither convenient nor reliable.
The Challenge
There's a software delivery team working in a Scrum methodology. This team divides its work into epics (which stand for features) and stories. The Scrum Master wants to know how long it takes to deliver an epic (and therefore add a new feature to the app). Independently, the Scrum Master wants to measure how fast is a single story delivered.
The Solution
Thanks to SLA PowerBox we configure two separate SLA Clocks - for Epics (measuring the time from creation until implementation) and for Stories (from defining to resolving). The Scrum Master also sees a Due Date clock, showing when an Epic is close to 1, 2 or 3-month delivery date, depending on priority setting.
| Incident Priority | Time to first response | Time to resolution | Root Cause fix time |
|---|---|---|---|
| Critical | |||
| High | |||
| Medium | |||
| Low | |||
| 1st Line Support | |||
| 2nd Line Support | |||
| 3rd Line Support | |||
Please describe some usecases of SLA PowerBox
give examples of configuration and expected behaviour of the metric U can use demo conf but please use also
https://confluence2.promity.pl/display/SLAPLUGIN/Time+to+implementation
so we will have 3 in total
During software development, workflows may undergo changes, and therefore, the SLA should be updated accordingly to align with the project's reality. The update process can be executed seamlessly by adhering to some recommended guidelines.