Use Cases for Project & Delivery Managers
Delivery managers rely on SLA Time and Report to track deadlines, monitor performance, and ensure predictability across distributed teams.
Key Metrics and Tasks
Start SLA to the Due Date:
Instead of starting from issue creation, configure the SLA to count backwards from the due date. Useful for release milestones and delivery checkpoints.
Working with Negotiated Date:
Use this field to reflect officially shifted deadlines. The app recalculates SLA automatically if the Negotiated Date changes.
SLA Configs for Global Teams:
SLA conditions may use multiple operational hours for a single issue.
For example, the Lisbon team + Melbourne team are working sequentially.
SLA Goals as Escalations:
Used for delivery control: when the issue approaches its deadline, it automatically escalates to the Scrum Master or Delivery Manager.
Practical Tips for Project & Delivery Managers
Use Met vs Exceeded per Criteria Charts to track delivery performance by team, component, sprint, or release.
Create SLA rules for "Time in Review" or "Time in QA" to track bottlenecks inside the SDLC.
Build dashboards with multiple SLA gadgets to monitor at a glance which tasks are at risk.
Always configure multiple working calendars for distributed teams to avoid inaccurate time tracking.
Below are pages with different use cases that may be useful for you:
If you need help or want to ask questions, please contact us through SaaSJet Support or via email support@saasjet.atlassian.net
Haven't used this add-on yet, then try it now!