Pace, Predictability, Impact: Earn the ROI on Your Agile Transformation

An engineering operations approach for regulated teams on Atlassian. Your organisation moved to Atlassian to make agile actually pay off. In a regulated engineering environment, the path from migration to real delivery speed is harder. In this recorded webinar, Rina Nir (RadBee) and Gabriela Nir (Engineering Ops Center) walk through the engineering operations discipline that closes the gap at scale: a continuous cycle of alignment, visibility, and improvement, running on the flow metrics your Jira already produces. Live analysis on a real Jira project from a MedTech engineering team, with two diagnostic stories every regulated engineering leader will recognise. 📌 What you'll learn: What the engineering operations discipline actually is, and why it's the missing layer after an Atlassian migration How to read a Jira sprint report to spot an upstream bottleneck in cycle time How to use Jira custom fields to make invisible constraints (like SDD approval gates) visible and diagnosable How to move from a monolithic to an incremental SDD approach without breaking compliance (referencing AAMI TIR45 guidance) How to analyse a reopen spike in the burndown chart, and the four Jira fields that make reopen data useful How to build a Rovo AI Sprint Analyzer that surfaces root causes in seconds The Definition of Done and Acceptance Criteria interventions that reduced defects and cut QA friction ⏱ Chapters: 00:00 Introduction 01:09 Meet Gabriela Nir and the Engineering Operations Center 06:06 What we'll cover 08:02 What agile really means (the WhatsApp emoji example) 11:30 Engineering operations: an operational view of the whole department 14:29 Success metrics: predictability, pace, impact, quality 17:01 Quality in regulated environments 19:31 The improvement loop: alignment, visibility, improvement 22:06 Case study: enterprise MedTech, renal care device, twice-a-year releases 25:20 The team, the workflow, the SDD gate 27:07 Sprint 1: baseline sprint report and the bottleneck 31:04 Alignment: adding the SDD ID field 33:47 Visibility: 70-80% of stories tied to a single SDD 35:23 Two approaches: incremental SDD vs breaking SDDs into smaller ones 37:52 Regulation is not waterfall (AAMI TIR45) 40:33 Why "done" matters even with twice-a-year releases 42:26 Sprint 2 result: 77% completion 43:18 The burndown chart: overshooting and unstable content 48:09 Reopen spikes and the four Jira fields for reopen analysis 51:19 What the reopen data revealed 53:10 Root cause with a Rovo AI Sprint Analyzer 56:57 Developer interviews and ticket sampling 58:17 The interventions: rework metric, enforced DoD and AC 59:25 Key takeaways 01:00:23 Q&A and close 🎓 About the presenters: Rina Nir is the founder of RadBee. She helps regulated engineering organisations move tooling and data into Atlassian, and build the engineering operations practices that make the new setup deliver at scale. Gabriela Nir is the founder of the Engineering Operations Center, home to Israel's community of around 700 engineering operations practitioners. She teaches on the TPM certification programme run with Hebrew University, consults, and coaches VPs of Engineering and CTOs. Her book on the Center's framework is being translated from Hebrew. (No relation, despite the shared surname.) 🤖 The Rovo Sprint Analyzer prompt As promised in the webinar, here is the prompt used for the Rovo AI Sprint Analyzer agent. Plug it into Rovo, adapt to your team's context, and iterate. ======== You are an Engineering Operations expert who is focused on analyzing our sprints, finding problems in our process and suggest solutions. You purpose is to help the team improve cycle time, impact and predictability. You have the following jobs: 1. Review completed sprints and identify the cases where work items were not processed smoothly into Done (and stayed there) 2. Find repeating patterns of work items that are processed in non smooth ways and identify systemic problems 3. Suggest solutions to the problems you identify 4. Compare between different sprints to see if if there are changes in our performance We are optimizing our processes to achieve these goals: a work item that is included in a sprint will arrive to DONE within the time of the sprint, and will not bounce out of this status. ========= 🔗 Resources: RadBee: https://radbee.com Engineering Ops Center: [URL] AAMI TIR45 guidance on agile in medical device software: [URL] 📺 Related: Previous webinar — Your Legacy Migration to Atlassian Is Simpler Than You Think:   / 7441885642961211394   📩 Connect: Rina Nir on LinkedIn: [URL] Gabriela Nir on LinkedIn: [URL] #EngineeringOperations #Atlassian #Jira #AgileTransformation #MedTech #RegulatedEngineering #Rovo #CycleTime #FlowMetrics #IEC62304