Aligning Your People, Processes, and Technology to Customers

Preconditions for Adopting Agile

In this section, the speaker discusses the necessary preconditions to adopt agile and how to create those conditions over time.

Creating Necessary Preconditions

• To adopt agile, whole complete teams with minimal dependencies are necessary.

• Backlogs and the ability to produce working-testine incremental software are also essential.

• The fundamental question is how to create these conditions over time by aligning people with the business and minimizing dependencies.

Orchestration of Dependencies in Agile

• Dependencies between teams require orchestration mechanisms.

• Heavy design dependencies are difficult to resolve during a sprint.

• Safe is an approach used to orchestrate dependencies across teams.

Dependencies in Agile

In this section, the speaker explores the idea of dependencies in agile and how they can be managed.

Managing Dependencies

• Teams in agile consist of six to eight people who have some amount of autonomy over their technology stack.

• Dependencies between teams require orchestration mechanisms.

• Occasional dependencies can be resolved during a sprint by asking someone for help, but heavy design dependencies are difficult to resolve during a sprint.

Business Architecture and Domain-driven Design

In this section, the speaker talks about business architecture and domain-driven design as ways of achieving alignment between business, technology, and people.

Achieving Alignment

• The intersection between business architecture and domain-driven design can help achieve alignment between business, technology, and people.

• Encapsulated release trains and value streams can help achieve alignment within scrum teams.

• A product-driven organization is fundamentally aligned with its product as it represents value.

Composable Enterprise

In this section, the speaker talks about composable enterprise as an approach that builds reusable components.

Composable Enterprise

• A composable enterprise is an agile open digital kind of enterprise built of reusable components.

• The idea of a composable enterprise is similar to what the agile community has been hunting for.

• Creating a culture of agility requires changing organizational structure and teaming strategies.

Product Driven Organizations

In this section, the speaker discusses the idea of product-driven organizations and how to align teams with business goals.

Encapsulation and Orchestration

• Encapsulation and orchestration are fundamental to creating a product-driven organization.

• The agile community needs to help companies create these kinds of teams and organizations.

• To achieve the benefits of an agile, open digital, composable enterprise, or product-driven organization world, we need to fundamentally rethink our systems' architecture.

Challenges in Creating Product-Driven Organizations

• It is difficult to see past current constraints when trying to create a product-driven organization.

• Agile coaches argue that if an organization cannot see past its current constraints, it will struggle to make progress.

• Companies often try new software or processes without addressing underlying problems.

Orchestrating Change

• Senior leaders may delegate change programs without understanding what needs changing.

• Executives must understand that creating a product-driven organization requires rethinking their systems' architecture and business capability modeling.

• Many organizations struggle to launch structured and disciplined change programs.

Leading Agile's Approach

• Leading Agile helps organizations adopt agile by identifying necessary preconditions for adoption.

Agile and Cloud Migration

In this section, the speaker discusses the similarities between adopting agile methodologies and migrating to the cloud. He explains that both require a fundamental precondition of breaking down existing systems and rebuilding them in a new way.

Legacy Monoliths and Cloud Migration

• The speaker compares legacy monoliths to software that needs to be migrated to the cloud.

• There is a difference between being "cloud-enabled" and being "cloud-native." To fully exploit the benefits of the cloud, software needs to be pulled apart, made more services-oriented, containerized, wrapped in APIs, and tested.

• Migrating to the cloud requires thinking about it in terms of encapsulation, orchestration, minimizing dependencies.

Digital Transformation

• The speaker mentions that digital transformation has been treated as a technology problem but is really a people and process problem. It requires organizational design and governance changes.

• New technologies or processes alone cannot solve digital transformation problems. Instead, organizations need to align people with business goals while minimizing dependencies.

Composable Enterprise

• The speaker introduces the concept of a composable enterprise as an umbrella term for marrying systems view, technology view, and people view into one cohesive organization.