Lesson 3: Team and Technical Agility

Agile Team

A cross-functional group of ten or fewer people with all the skills needed to define, build, test, and deliver value.

Scrum Master / Team Coach

Facilitates team events, removes impediments, supports flow, and helps the team improve.

Product Owner

Connects with customers, prioritizes the team backlog, and ensures the team delivers valuable increments.

Agile Team Responsibilities

Planning work, delivering value, getting feedback, connecting with customers, and improving continuously.

SAFe Scrum

A structured approach using iterations, backlog refinement, reviews, and retrospectives to deliver value in small batches.

Team Kanban

A visual system that manages flow, limits work-in-process, reduces delays, and ensures continuous delivery.

Agile Teams Focus on Value

Agile teams optimize for continuous delivery of customer value through small batch work and fast feedback loops.

Agile Teams Visualize Flow

Teams visualize work from start to finish, revealing bottlenecks and opportunities to improve throughput.

Agile Release Train (ART)

A team of Agile teams (50–125+ people) aligned to a shared mission, working on a common cadence.

Cross‑Functional ART

ARTs combine roles across business, product, hardware, software, testing, compliance, and security.

Planning Interval (PI)

A timebox of 8–12 weeks during which ARTs plan, commit, develop, and deliver value.

ART Backlog

A prioritized list of features, enablers, and nonfunctional requirements that guide the ART’s work.

Release Train Engineer (RTE)

The chief Scrum Master for the ART, enabling coordination, removing impediments, and coaching the organization.

System Architect

Provides architectural and technical direction across teams to ensure alignment and solution integrity.

Product Management

Owns, defines, and prioritizes the ART backlog to ensure features align with customer and business needs.

Business Owners

Key stakeholders who assign business value, give direction, and approve outcomes in the PI.

System Team

Provides tooling, infrastructure, and integration support so teams can test and validate early and often.

Shared Services

Specialists (security, legal, UX, compliance) who support the ART but are not dedicated full-time.

Built‑In Quality

A foundational SAFe practice ensuring quality is maintained at every step of development.

Shift Learning Left

Finding and fixing issues earlier in development to reduce cost and improve quality.

Pairing and Peer Review

Collaboration techniques that improve quality, knowledge sharing, and design accuracy.

Collective Ownership and T‑Shaped Skills

Teams share responsibility for work and broaden skills to eliminate bottlenecks.

Definition of Done (DoD)

A clear and consistent standard for when work is complete and meets quality expectations.

Workflow Automation

Automating repetitive work to reduce errors, support small batches, and improve delivery speed.

Domains of Built‑In Quality

Includes software quality, hardware quality, cyber‑physical quality, business quality, and Agile quality practices.

AI as a Quality Accelerator

AI supports earlier detection, increased review capacity, consistent checks, and fewer manual errors.

DevOps Purpose

Combines development and operations to achieve speed, stability, and high-quality delivery.

Continuous Delivery Pipeline (CDP)

The workflow of continuous exploration, integration, deployment, and releasing on demand.

Continuous Exploration

Understanding customer needs, exploring options, and preparing work for execution.

Continuous Integration

Teams frequently integrate and validate their work to reduce feedback times and improve quality.

Continuous Deployment

Deploying validated code to staging or production environments automatically and frequently.

Release on Demand

Releasing functionality when the business determines the timing will produce the most value.

Decouple Deploy from Release

Deploy continuously but release features strategically, often using feature toggles.

IP Iteration

A final PI iteration dedicated to innovation, planning, learning, and providing a buffer for leftover work.

System Demo

A full demonstration of completed work across the entire ART to show integrated progress.

Without IP Iteration Consequences

Increased burnout, rising technical debt, unpredictability, and less innovation.

Inspect and Adapt

A structured PI event including a system demo, measurement review, and a problem‑solving workshop.

ART Events

Key events such as PI Planning, ART Sync, System Demos, and Inspect and Adapt that maintain cadence and alignment.

ART Sync

Provides visibility into ART progress, risks, and priorities and brings stakeholders together to adjust course.

Coach Sync

Scrum Masters and Team Coaches review team-level risks, dependencies, and coordination needs.

PO Sync

Product Owners align on progress, priorities, and any needed adjustments to the team or ART backlogs.