Do you have Scrum/Kanban teams frequently releasing high-value, quality product updates? Unfortunately, such agility usually doesn’t last, with features starting to take longer to build, changes becoming riskier to make, and quality getting more difficult to maintain. In short: the *cost of change* increases, and the *safety* to make it decreases. One element of preventing this threat to agility is for the team to have good *Technical Agility*. However, the most common strategy to achieving that – expecting developers to use “technical practices” – rarely makes a lasting, noticeable difference. That’s because developers’ actual behaviors depend heavily on how product and management engage with them. In this session we’ll explore Technical Agility from a mindset standpoint, identify its influence on product choices and outcomes, and identify how all parties should engage with each other to achieve a level of Technical Agility that enables actual product and business Agility.