Do you have Scrum/Kanban teams frequently releasing high-value, quality product updates?
Usually, such Business Agility doesn’t last. As time goes on, features start taking longer to build, changes become riskier to make, and quality gets more difficult to maintain. This predictable situation is due to low Technical Agility.
The fact is, it matters how developers approach work, and that, it turns out, depends heavily on their engagement with product and with management.
In this session, we’ll see how Technical Agility is much more than dev practices, how it influences product managers’ requirements and responsibilities, and how all parties can engage with each other and maintain mutual commitment to Technical Agility to enable Business Agility.
Gil Broza helps companies increase organizational agility and team performance with minimal risk and thrashing. Dozens of companies seeking transformations, makeovers, or improvements have relied on his pragmatic, modern, and respectful support for customizing Agile in their contexts. These days, several of the world’s largest organizations are having him train hundreds of their managers in technology and business (up to SVP/CIO level) on practical Agile leadership.
Gil is the author of two acclaimed books The Human Side of Agile, The Agile Mind-Set, and his most recent new Agile for Non-Software Teams.
Get a taste of his approach at OnTheWayToAgile.com
Copyright Toronto Product Management Association (TPMA) © 2019