2021 Talks

Calling Your Shots: Creating Safety, Accountability and Orchestrating Change at Scale

Brian Sondergaard
Brian Sondergaard
1 of 30

About The Talk

Change doesn’t happen by accident. Change must get planned, orchestrated, and held accountable. Many organizations have a Project Management Office responsible for setting standards, providing resources, managing work, and making sure the organization’s work is visible. We need to discover a similar mechanism for orchestrating an Agile Transformation, an Agile Transformation Office, if you will. If such an office were to exist, what might it look like? What might it be responsible for? How would that office ensure the Transformation was on track? And what would it do once the Transformation was over?

This talk will explore some of the more common elements of an Agile Transformation Office. How you create one. What services it offers. And its overarching responsibility to responsibly lead change. We will look at how it selects and supports pilots and develops Transformation roadmaps. We will explore the role of Agile playbooks, Agile tooling, metrics, and assessments. We will explore how training and coaching fits in and what you do with the rest of the organization when it’s excited to go but isn’t on the near-term roadmap. Finally, we will explore the relationship between the Agile Transformation Office and the Office of the CIO and what it looks like once the Transformation is complete.

Topic Areas:

Download Slides

Up Next

Agile. The Past 20 Years

Agile. The Past 20 Years

This year the Agile Manifesto celebrates its 20th anniversary. As a document, it’s challenging to find an approach or philosophy, or way of thinking that has more deeply captured the imagination of the world of software development. The Manifesto articulated four values and twelve principles that empowered small teams of engineers working side-by-side with their customers to deliver products early and often to get maximum feedback, maximum value, and strong attention to software craftsmanship and technical excellence.

Mike Cottmeyer
Mike Cottmeyer
Agile Transformation and Delivery Systems at Scale

Agile Transformation and Delivery Systems at Scale

Small teams dominated the early days of Agile, often collocated and working side-by-side with onsite customers. With autonomy over their technology stack and the ability to do push button changes into production at a moment’s notice. The core organizing principle was that we had dedicated teams, working off a clearly articulated backlog of requirements, producing an increment of working-tested software at regular intervals.

Anita Lessard
Anita Lessard
Lockheed Martin Experience Report

Lockheed Martin Experience Report

Discover how Lockheed Martin is using Agile principles to generate disruptive innovation. In this talk, John and John will cover how Lockheed Martin is improving their processes, technology, and tools to drive Agile responsiveness and provide data-driven insights to their customers. Over the course of the talk they’ll tell you about some of the practices they put in place and the results they began to see.

John Markowski
John Markowski
John McLoughlin
John McLoughlin
Establishing a Reliable System You Can Delegate Into

Establishing a Reliable System You Can Delegate Into

For years, the Agile community has taken the approach that an Agile Transformation was about teaching people the principles, practices, and mindset of an Agile organization. While principles, practices, and mindset are incredibly important, they are insufficient for successfully orchestrating a transformation at scale. Everything about agile assumes that you have complete cross-functional teams, clearly articulated and strategically aligned backlogs, and the ability to produce a working, tested increment of software at the end of every sprint. This begs the question; what do you do if you don’t?

Melissa Oberg
Melissa Oberg
Understanding the Whole: Why Changing the System of Delivery is Insufficient

Understanding the Whole: Why Changing the System of Delivery is Insufficient

Most organizations view Agile as a way the delivery teams produce working software. Even when we get agile working well at the team or workgroup level, we often fail to consider how the rest of the organization will need to change to exploit this new delivery capability. Once we have a trustworthy system, one we can delegate into that does what it says it will do, when it says it will do it, what has to change companywide for true business agility?

Dennis Stevens
Dennis Stevens
Engaging the Enterprise at Scale: How to Get Everyone Else to Change

Engaging the Enterprise at Scale: How to Get Everyone Else to Change

One of the challenges of introducing Agile into an organizational ecosystem is that the principles, practices, mindsets, organizational structure, governance, and metrics are orthogonal to how most corporations do business. Agile gets installed in the small and is instantly at odds with the current operating model. It is incongruent with how work is funded and approved and how it handles compliance and corporate governance. To even have a chance, agile is granted exceptions to these control frameworks. Still, in the end, these frameworks will limit our ability to make progress and achieve true business agility.

Chris Beale
Chris Beale
Ford Motor Company Experience Report

Ford Motor Company Experience Report

In this talk, Amy tells you about her experiences at Ford Automotive and how they used Agile principles to evolve so they could focus on services, experiences, and technology to build a better world where every person is free to move and pursue their dreams.

Amy Palazzolo
Amy Palazzolo
Calling Your Shots: Creating Safety, Accountability and Orchestrating Change at Scale

Calling Your Shots: Creating Safety, Accountability and Orchestrating Change at Scale

Change doesn’t happen by accident. Change must get planned, orchestrated, and held accountable. Many organizations have a Project Management Office responsible for setting standards, providing resources, managing work, and making sure the organization’s work is visible. We need to discover a similar mechanism for orchestrating an Agile Transformation, an Agile Transformation Office, if you will. If such an office were to exist, what might it look like? What might it be responsible for? How would that office ensure the Transformation was on track? And what would it do once the Transformation was over?

Brian Sondergaard
Brian Sondergaard
Executive Panel Discussion

Executive Panel Discussion

In this panel discussion, four executives sit down to explore some of the key concepts and common threads covered in the Elevate Agile talks. Together, they discuss some of the history that’s led us to this point in the Agile industry and share real-world examples and stories to illustrate how they’ve elevated Agile in some of the largest companies in the world.

Mike Cottmeyer
Mike Cottmeyer
Chris Beale
Chris Beale
Dennis Stevens
Dennis Stevens
Brian Sondergaard
Brian Sondergaard

Please Sign In

Sign in using the email from your Elevate Agile Registration

Email not Found