What can a Scrum Master/Team Coach recommend to a team that is showing signs of burnout, not addressing increasing technical debt, and acting out of…

A constructive IP Iteration is one of the recommended practices for Scrum Masters/Team Coaches to

help teams avoid burnout, address technical debt, and foster innovation. An IP Iteration is a unique,

dedicated iteration that occurs every PI and provides an estimating buffer for meeting PI Objectives

and dedicated time for innovation, continuing education, PI Planning, and Inspect and Adapt events.

During the IP Iteration, teams can work on activities such as hackathons, research and design, spikes,

refactoring, automation, training, and other improvement initiatives that are difficult to fit into a

continuous, incremental value delivery pattern. An IP Iteration also allows teams to prepare for and

participate in the PI Planning and Inspect and Adapt events, which are essential for alignment,

collaboration, and learning across the ART. A constructive IP Iteration can improve the predictability

and flow of value delivery, increase employee engagement and satisfaction, enhance the agility and

resilience of the teams, and create a competitive advantage for the enterprise. (Must be taken from

SAFe 6 Scrum Master resources)

Reference:

Innovation and Planning Iteration - Scaled Agile Framework

The CALMR Approach to DevOps [Complete Guide] - KnowledgeHut

SAFe Scrum Master Course Outline