Uploaded by Roderick Capili

Study Notes day3

© Scaled Agile. Inc.
The 10 SAFe Lean-Agile Principles:
Take an economic approach
Apply systems thinking
Assume variability; preserve
Build incrementally w/ fast,
integrated learning cycles
Base milestones on objective
evaluation of working systems
Make value flow w/out
Apply cadence, synchronize with
cross-domain planning
Unlock the intrinsic motivation of
knowledge workers
Decentralize decision-making
Organize around value
Best value and quality for people and society in the shortest sustainable lead time
“Deliver early and often”
Applied to the system under development, as well as to the organization that
builds the system “But optimizing a component does not optimize the system”
Empirical data is used to narrow the focus, resulting in a design that creates
optimum economic outcomes
Developing solutions incrementally in a series of short iterations allows for faster
customer feedback and mitigates risk
Regular evaluation provides the financial, technical, and fitness-for-purpose
governance needed
Provides specific recommendations for eliminating impediments to flow
“Identifying delays”
Cadence creates predictability and provides a rhythm for development.
Synchronization causes multiple perspectives to be understood, resolved, and
integrated at the same time
Providing autonomy and purpose, minimizing constraints, creating an
environment of mutual influence, and better understanding the role of
compensation are keys to higher levels of employee engagement
Creating a reliable decision-making framework is a critical step in empowering
employees and ensuring a fast flow of value “Reduces Delays”
Business Agility demands that enterprises organize around value to deliver more
SAFe Implementation Roadmap
Portfolio Vision – future
Portfolio Canvas – Current
Reaching the Tipping Point
Train Lean-Agile Change Agents
Create a Lean-Agile Center of Excellence
Train Executives, Managers, and Leaders
Lead in the Digital Age
Organize Around Value
Create the Implementation Plan
Prepare for ART Launch
Train Teams and Launch Art
Coach Art Execution
Launch More ARTs and Value Streams
Enhance the Portfolio
Kotter’s 8-step process for leading change
1. Create a sense of urgency
2. Pull together the guiding team
3. Develop the change vision and strategy
4. Communicate for understanding and buy-in
5. Empower others to act
6. Produce short-term wins
7. Don’t let up
8. Institute change
“Strategic Themes influence Guardrails.”
Three components of the Continuous Delivery Pipeline
1) Continuous Exploration
2) Continuous Integration
3) Continuous Deployment
Lean thinking
Precisely specify value by product
Identify the value stream for each product
Make value flow without interruptions
Let the customer pull value from the producer
Pursue perfection
Guardrail 1: Guiding Investments by Horizon
Guardrail 2: Apply Capacity Allocation
Guardrail 3: Approving Significant Initiatives
Guardrail 4: Continuous Business Owner Engagement
Agile Manifesto Values
Individuals and interactions over processes and tools
Working Software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
© Scaled Agile. Inc.
Four Core Values
1) Alignment
Communicate the vision, mission, and strategy
Connect strategy to execution
Speak with a common language
Constantly check for understanding
Understand your customer
3) Respect for People
Hold precious what it is to be human
Value diversity of people and opinions
Grow people through coaching and mentoring
Embrace ‘your customer is whoever consumes your work
Build long-term partnerships based on mutual benefit
2) Transparency
Create a trust-based environment
Communicate directly, openly, and honestly
Turn mistakes into learning moments
Visualize work
Provide ready access to needed information
4) Relentless Improvement
Create a constant sense of urgency
Build a problem-solving culture
Reflect and adapt frequently
Let facts guide improvements
Provide time and space for innovation
The Seven Core Competencies of Business Agility
Organizational Agility
► Create an enterprise-wide Lean-Agile mindset (Lean-Thinking People & Agile Teams)
► Map and continuously improve business processes (Lean Business Operations)
► Respond quickly to opportunities and threats (Strategy Agility)
2) Lean Portfolio Management
► Align strategy, funding, and execution (Agile Portfolio Operations)
► Optimize operations across the portfolio (Strategy & Investment Funding)
► Lightweight governance empowers decentralized decision-making (Lean Governance)
3) Enterprise Solution Delivery (Execution)
► Apply Lean systems engineering practices to build really big systems (Lean Systems Engineering)
► Coordinate and align the full supply chain (Coordinate Trains and Suppliers)
► Continue to enhance value after release (Continually Evolve Live Systems)
4) Agile Product Delivery (Execution)
► The Customer is the center of the product strategy (Customer Centricity & Design Thinking)
► Decouple the release of value from the development cadence (Develop on Cadence, Release on Demand)
► Continuously explore, integrate, deploy, and release (DevOps and the Continuous Pipeline)
5) Team and Technical Agility (Execution)
► High-performing, cross-functional Agile Teams (Agile Teams)
► Teams of business and technical teams build Solutions (Teams of Agile Teams)
► Quality business Solutions delight Customers (Built-in Quality)
6) Lean-Agile Leadership
► Inspire others by modeling desired behaviors (Leading by example)
► Align mindset, words, and actions to Lean-Agile values and principles (Mindset & Principles)
► Actively lead the change and guide others to the new way of working (Leading Change)
7) Continuous Learning Culture
► Everyone in the organization learns and grows together (Learning Organization)
► Exploration and creativity are part of the organization's DNA (Innovation Culture)
► Continuously improving Solutions, services, and processes is everyone's responsibility (Relentless Improvement)
© Scaled Agile. Inc.
The RTE is the servant leader and coach for the ART
► Guides people in problem identification and decision-making
► Creates an environment of mutual influence
► Empathizes with others
► Encourages the personal development of teams
► Persuades rather than uses authority
► Applies systems thinking
► Supports the commitments made by the teams
Responsibilities of the RTE include:
Responsibility areas of the RTE
► Managing and optimizing the flow of value through the ART
► Fostering collaboration between teams and ART stakeholders
► Facilitating PI (Planning Interval) Planning readiness and the event itself
► Tracking and communicating key ART execution Metrics
► Escalating and tracking ART impediments
► Facilitating relentless improvement for the ART
Improving Relentlessly
Facilitating PI Planning
Supporting PI Execution
Optimizing Flow
Coaching the ART
Why do RTEs need the SAFe Principles?
► RTEs must understand why practices work; it’s part of ‘knowing what they must do’
► If a practice needs to change, understanding the Principles ensures that the change moves the ART in the right direction
► A shared understanding of the Principles helps decentralize decision-making within the teams and roles on the ART
Moving to Continuous Deployment and Release on Demand
► Organizations often migrate from component teams to other team types (usually stream-aligned teams) as the ART matures
► Over time, organizations build the cross-functional skills required for stream-aligned teams through cross-training and pair
► As skills advance, carefully rotate team members between different component teams to spread knowledge
► Create Enablers to architect for deploying and releasing more frequently
ART Roles:
Release Train Engineer is a coach for the ART.
System Architect provides architectural guidance and technical enablement to the teams on the train.
Business Owners are key stakeholders on the ART.
Product Management owns, defines, and prioritizes the ART Backlog
The System Team provides processes and tools to integrate and evaluate assets early and often.
Key ART roles: (ART leadership is collaboratively handled by the three key ART roles, each focusing on one area.)
ART Execution: The RTE facilitates optimizing the flow of value through the ART.
Content Management: Product Management is the internal voice of the customer on the ART.
Design Authority: The System Architect defines the overall architecture for the system.
ARTs (Team specifications): ARTs are cross-functional “Optimized for communication and delivery of value.”
A virtual organization of 5–12 teams (50–125+ individuals)
Synchronized on a common cadence (a PI)
Aligned to a common mission via a single ART Backlog
Teams on the ART are organized for flow:
Stream-aligned team – Organized around the flow of work and can deliver value directly to the Customer or end user.
Complicated subsystem team – Organized around specific subsystems that require deep specialty skills and expertise.
Platform team – Organized around the development and support of platforms that provide services to other teams.
Enabling team – Organized to assist other teams with specialized capabilities and help them become proficient in new tech.
© Scaled Agile. Inc.
Business Agility Value Stream
Business opportunity emerges
Sense opportunity
Fund MVP
Organize around value
Connect to customer
Deliver MVP
Pivot or Persevere
Deliver Value Continuously
Learn and Adapt
Business opportunity leveraged
Business Owners responsibility areas
Sponsoring Relentless Improvement
Leading by Example
Engaging with Lean Portfolio Management
Aligning Priorities & PI Planning
Realizing Business Outcomes
System Team (The teams on the ART are collectively responsible for delivering larger system and Solution value.)
To support this work, a System Team is often formed to:
► Create and maintain infrastructure, including Continuous Integration, automated builds, and automated build verification
► Perform end-to-end system integration and Solution performance testing
► Assist in staging System Demos
► Support DevOps and CDP activities, including Release on Demand
System Team responsibility areas
Facilitating Releases
Building Development Infrastructure
Supporting Solutions Integration
Assisting with End-to-End Testing
Supporting System and Solution Demos
Balancing responsibilities (The System Team can never be the entire solution to the integration challenge.)
Maximizing ART velocity requires a sense of balance between Agile Teams and the System Team. Best practices include:
► Shared non-functional requirement (NFR) testing across other teams and the System Team
► Shared understanding of infrastructure and tooling across the teams on the ART
► Shared necessity to avoid turning the System Team into a bottleneck
© Scaled Agile. Inc.
Preparing the ART Backlog for PI Planning
In the weeks before PI Planning, Product Management does the final ART Backlog preparation with System Architects and ART
► RTEs will be more active in coaching a new ART when preparing the backlog
► Over time, the Product Management and the System Architect should be able to handle most of this preparation work
► The RTE will be one of the backlog stakeholders, often focused on infrastructure Enablers and improvement items
Features represent the work for the Agile Release Train
► Feature benefit hypothesis justifies development costs and provides a business perspective for decision-making
► Acceptance criteria are typically defined during ART Backlog refinement
► Reflect functional and non-functional requirements
► Typically sized to fit into a single PI
Enablers build the Architectural Runway
Enablers define the existing code, hardware components, marketing guidelines, and other variables that enable near-term
business Features.
► Enablers also build up the runway, including exploration, architecture, infrastructure, and compliance
► Features consume the runway
► The Architectural Runway must be continuously maintained
► Capacity allocation (a percentage of the train’s overall capacity in a PI) is used for Enablers that extend the runway
Product integrity through capacity allocation
► At each PI boundary, agree on a healthy balance between each work type
► Establish policies to determine how work is performed
► The System Architect has design authority and prioritizes architectural work
► Product Management prioritizes business Features
► Agree to jointly prioritize work based on economics
► Agree to collaborate to sequence work to maximize Customer value.
Socializing Features and Enablers
Socializing Features and Enablers solves many problems later during PI Planning.
1) Product Management and other stakeholders refine the ART Backlog.
2) Features are socialized with the teams on the train, and each team identifies big/initial Stories.
3) Each team works to prepare a rough backlog for the PI Planning looking for feedback, big unknowns, etc.
How much preparation is enough?
Both too much and too little preparation can cause problems. The RTE helps the teams and stakeholders find a good trade-off.
► Do more pre-planning if you create new architecture or functionality
► Remind attendees that too much pre-planning minimizes exploration, interaction, and emergent designs/solutions
► Do enough preparation to maximize the amount of interaction in the event
© Scaled Agile. Inc.
ART readiness checklist
Planning scope and context
Is the scope (product, system, technology domains) of the planning process
Have we identified our Value Stream(s) and Agile Release Train(s)?
Have we identified the RTE?
Do they understand the scope of the role in preparing the organization and
preparing for the PI Planning event?
Have we identified the PI Planning dates, the Iteration cadence, and the PI
Does each team have an identified SM/TC and Product Owner (PO)?
Have we identified cross-functional Agile Teams?
Are there dedicated team members on every team?
Are all team members attending PI Planning, whether in person or involved
Do we know who will set and present the business context and strategy?
Do we know who will assign business value and accept the plans?
Is there reasonable agreement on priorities amongst the Business Owners and
Product Management?
Do we know who will present the Architecture Vision and required
development practice?
Is there a clear vision of what we are building, at least over the next few PIs?
Have we identified the top 10 or so Features that are the subject of the first PI?
Has the System Team been identified and formed?
Have the Shared Services (User Experiences, Architecture, etc.) been
Do we know what other key business and technology stakeholders should
Do we know how and where Iterations, PIs, Features, Stories, measures, etc.,
will be maintained?
Do we have a strategy for using and improving the Continuous Delivery
Is there a strategy for applying Built-in Quality practices?
Planning timeframe, Iteration and PI
Agile Teams (SM/TCs, POs)
Team makeup/commitment
Agile Team attendance
Executive, Business Owner
Business alignment
Architecture Vision and Development
Product/Solution Vision and ART Backlog
System Team
Shared Services
Other Attendees
Agile Lifecycle Management (ALM) tooling
Development infrastructure
Quality practices
© Scaled Agile. Inc.
The responsibilities of the RTE in PI Planning
RTEs are the heartbeat of PI Planning and are responsible for:
► Helping the ART prepare for PI Planning
– Planning scope and context
– Content readiness
– Logistics
► Facilitating Days 1 and 2 of PI Planning
– Manage agenda
– Run Coach Syncs
– Facilitate draft and final plan readouts
– Facilitate Management Review and problem-solving meeting
Presentations at the start of Day 1
The day starts with the content presentations, creating a shared understanding of the business context and the boundaries that
the teams are planning the PI inside. The RTE should prepare by:
► Double- and triple-checking audio/video equipment and other technological needs.
► Having one slideshow deck and one computer for presentations. Avoid switching between decks and devices to keep it
flowing smoothly.
► Planning room for a short Q&A after each presentation and managing the timebox by pushing discussions to meet-afters as
Team breakout #1
The teams create draft plans for each Iteration, write draft PI Objectives, and identify ART PI Risks and impediments.
► Teams should use visual radiators for planning to create transparency and collaboration
► Make sure teams are using common tools and standards (such as color-coded sticky notes)
► Ask SM/TCs to assist in preparing each team’s physical/virtual spaces for the event
Team planning radiators in detail: (Iterations)
► Teams write and sequence User Stories and Enabler Stories across the PI
► Teams identify risks and escalate them if they cannot be managed within the team
► Stories are estimated so that teams can determine their capacity and load
► Teams should allocate a percentage of capacity for unplanned activities, such as maintenance and production support.
Team planning radiators in detail: (IP Iteration)
► The last Iteration will be used for Innovation and Planning (IP)
► Teams should estimate their capacity but not a load on the IP Iteration
► Teams should not plan any Stories during the IP Iteration
Team planning radiators in detail: (PI Objectives)
► PI Objectives should be written so that they can be understood by someone outside the team
► Uncommitted objectives are in the team plan and fit in the capacity, but the team is unsure if they can deliver
► SAFe suggests targeting 7-10 PI Objectives, with up to 3 uncommitted objectives
Team planning radiators in detail: (risks)
► ART PI Risks are those that are outside of the team’s control and need to be escalated. They will be captured and assessed
after the final plan review.
► Team risks are those under the team’s control. They won’t be presented and are handled by the team themselves.
Team breakout: (Hourly Coach Sync checkpoints)
The Coach Sync checkpoints help keep teams on track and facilitate early identification of risks.
© Scaled Agile. Inc.
ART Planning Board: (Feature delivery, dependencies, and Milestones)
Using the ART Planning Board
The ART Planning Board is a critical artifact during and after PI Planning
► Visually shows the sequence of inter-team dependencies that lead to Feature delivery
► Clearly indicates when Features are planned to be delivered
► Red sticky notes are agreed-upon and planned actions that will resolve a dependency and supports Feature delivery
Writing draft PI and uncommitted objectives
Draft objectives create transparency in PI Planning and help engage the Business Owners and stakeholders in the planning
► Draft versions are presented at the end of Day 1
► Targeting 7-10 committed objectives and up to 2-3 uncommitted objectives seems to work best
► Remind everyone to move team objectives to uncommitted if it is planned, but team confidence is not 100%
Draft plan review
At the end of Day 1, the RTE facilitates the session where each team presents their draft plan to the ART.
► The main purpose is to get everyone in the room thinking about dependencies, problems, and opportunities for tomorrow
► Make sure everyone follows the agenda when presenting and make the agenda visible to everyone
Draft plan review agenda:
1. Current capacity and load for each Iteration
2. Draft PI Objectives
3. Identify ART PI Risks and impediments
Management review and problem-solving
At the end of Day 1, management meets to make adjustments to scope and objectives based on the day’s planning.
Common questions:
► What did we just learn?
► Where do we need to adjust Vision, scope, team assignments, or anything else?
► Where are the bottlenecks?
► What Features must be de-scoped?
► What decisions must we make between now and tomorrow to address these issues?
© Scaled Agile. Inc.
Facilitating the management review and problem-solving meeting
The RTE is the facilitator of the management review and problem-solving meeting and is responsible for making sure that the
session produces an output.
► Have a clear idea of how to facilitate the meeting so that it is effective
► Work with the key ART roles, teams, and stakeholders throughout Day 1 to identify potential inputs for the meeting
► Invite selected team members that can help clarify problems and find solutions
► Make sure to document inputs and outputs from the meeting
► Over time, evolve how you facilitate the meeting
DAY 2: Facilitate final PI plan development and commitment.
Make planning adjustments.
► On day 2, based on the previous day’s management review and problem-solving meeting, adjustments are discussed
► Possible changes include:
– Adjust business priorities
– Adjustment to Vision
– Changes to scope
– Realignment of work and teams.
Team breakout #2
Based on new knowledge (and a good night’s sleep), teams now work to create their final plans.
► Focus on getting all Feature deliveries and dependencies visualized on the ART Planning Board – the RTE should assist the
teams and SM/TCs to get items placed
► Help the teams write readable, understandable, and S.M.A.R.T. PI Objectives
► Be available to facilitate discussions that might happen when assigning business value to PI Objectives
PI Objectives should be S.M.A.R.T.
Specific, Measurable, Achievable, Realistic, and Time-bound (SMART)
During the second team breakout, assist the teams in writing their PI Objectives using the S.M.A.R.T. format.
State the intended outcome as simply, concisely, and explicitly as possible.
M It should be clear what a team needs to do to achieve the objective. The measures may be descriptive, yes/no,
quantitative, or provide a range.
Achieving the objective should be within the team’s control and influence.
Recognize factors that cannot be controlled. (Hint: Avoid making assumptions)
The time period for achievement must be within the PI. Therefore, all objectives must be scoped appropriately.
Assigning business value to PI Objectives
► As the PI Objectives are finalized, each objective is assigned business value by the ART Business Owners on a scale of 1–10
► In a direct conversation with the Agile Teams, the ART Business Owners assign business value to each of the teams’ individual
PI Objectives
► Business value communicates the potential business impact of achieving an objective, which helps teams on the train
prioritize work
► The RTE might need to be available to facilitate this conversation, especially during the first PIs
© Scaled Agile. Inc.
Final plan review
The RTE facilitates the session where everyone in the room peer-reviews the final plans for all teams, and the Business Owners
accept the plan.
► Make sure everyone follows the agenda when presenting. Make it visible in the room.
► Validate that presented risks and impediments are outside of the teams’ control before accepting them as ART PI Risks.
► Manage the timebox for the Q&A.
► After each review, ask the Business Owners in the room if they accept the plan.
Final plan review agenda:
1. Changes to capacity and load for each Iteration
2. Final PI Objectives with Business Values
3. ART PI risks and impediments
4. Q&A
Addressing ART PI Risks
After all plans have been presented, the remaining ART PI Risks and impediments are discussed and categorized.
ROAM stands for:
► Resolved - Addressed; the risk is no longer a concern
► Owned - Someone has taken responsibility
► Accepted - Nothing more can be done, and if the risk occurs, the release may be compromised
► Mitigated – The team has a plan to adjust as necessary
The risk ROAMing session.
The risk ROAMing session can be challenging if you are new to the train as the RTE.
► Make sure to continuously look at risks as they appear in the planning session so you can develop a plan for how to ROAM
► Ask the SM/TCs to be proactive and come to you if their teams find big risks during planning.
► Be the facilitator when ROAMing. Avoid trying to find the solution yourself and ask the room for help.
► Product Management and the System Architect should be an active part of the ROAMing process.
Confidence vote: Teams and ART
Once ART PI Risks have been addressed, a confidence vote is taken by each team and the ART. “The teams and ARTs vote”
A commitment with two parts:
1. Teams agree to do everything in their power to meet the agreed-to objectives
2. If objectives become not achievable, teams agree to escalate immediately so that corrective action can be taken
PI Planning retrospective
PI Planning will evolve over time. Ending it with a quick and focused retrospective will help it continuously improve.
► By this time, everyone in the room is exhausted and wants to go home. Make it as focused and quick as possible.
► Keep the focus on collecting opinions, ideas, and data; you can sort and prioritize later.
► Make sure to change how you run the retrospective over time to keep it fun and energizing
After the PI Planning event
Following PI Planning, the RTE needs to take care of many key outputs and artifacts:
► If appropriate, make sure the work is tracked in an 98zaAgile project management tool
► Move the ART Planning Board to a dedicated location
► Capture the decisions made during the risk ROAMing session
► Create a set of integrated ART PI Objectives
► Set up meetings for recurring ART events
► Start planning the next PI Planning event
© Scaled Agile. Inc.
RTE takeaway: integrated ART PI Objectives
ART PI Objectives are the synthesis of each team’s PI Objectives.
For large solutions, ARTs are combined into a Solution Train
Solution Trains are used to build large solutions that require coordination across multiple ARTs and suppliers.
► Requires additional roles to coordinate delivery, including Solution Train Engineer (STE), Solution Management, and Solution
► Requires additional events to manage delivery across ARTs, including RTE Sync, Architect Sync, and Product Management
The role of the RTE in planning the Solution Train PI
► Collaborate with the STE to build the PI Planning schedule and agenda
► Integrate the Solution Vision into the Business Context portion of PI Planning
► Provide input for the Solution Train Management Review and problem-solving meeting
► Contribute ART PI Objectives to the aggregated Solution Train PI Objectives
Synchronize routinely throughout the PI
► Communicate progress toward objectives and track dependent work at RTE Sync or Solution Train Sync
► Coordinate large releases with STE and other Solution Train stakeholders
© Scaled Agile. Inc.
Explore facilitation of PI Planning across multiple locations
Distributed planning events
Distributed planning events require significantly more preparation and facilitation.
► Have a dedicated RTE proxy and tech support person at each location
► Test audio, video, and presentation-sharing connectivity multiple times
► Have a common understanding of how plans will be shared (video, intranet, collaborative ALM tool, emailing PPT, and so on)
► Establish team-based audio/video communication for breakout sessions
Respect for people and culture
► Have clear working agreements to be respectful and compromise when it comes to time zone differences
► Follow the Lean principle to respect people and cultures by avoiding asking teams to stay up all night
► Avoid asking teams to commit to their PI Objectives in a sleep-deprived state
► Consider extending the PI Planning agenda to accommodate multiple time zones.
Piplanning.io is now a part of SAFe.
A modern way to conduct PI Planning
With piplanning.io, collaborating virtually feels like being together in front of the same board. Empower RTEs to lead remote PI
Planning events that ensure alignment and focus across all teams.
► RTE Cockpit streamlines PI Planning prep and includes a strong team breakout experience
► Dependency Management visualizes your requirements with easy-to-follow link options
► Capacity Allocation balances new Features versus technical debt with one click
Executing a PI – (Using events to keep the ART on track.)
Responsibilities of Agile Teams and ARTs
Improving Relentlessly
Connecting with the Customer
Planning the Work
Delivering Value
Getting Feedback
Stories  Features  Epics
SAFe Scrum overview
Qualities of Story Points
Features & Dependencies are found on the ART Planning Board
© Scaled Agile. Inc.
SAFe Team Kanban overview
ART execution events
ART events create a closed loop system to keep the train on the tracks.
ART Sync is used to coordinate progress
Coach Sync
▸ Visibility into progress and impediments
▸ Facilitated by the RTE
▸ Participants include SM/TCs, other select team members,
SMEs if necessary
▸ Weekly or more frequently, 30–60 minutes
▸ Timeboxed and followed by a meet-after
PO Sync
▸ Visibility into progress, scope, and priority adjustments
▸ Facilitated by RTE or PM
▸ Participants include PM, POs, other stakeholders, and
SMEs as necessary
▸ Weekly or more frequently, 30–60 minutes
▸ Timeboxed and followed by a meet-after
© Scaled Agile. Inc.
Demo the full system increment every two weeks “best measure of progress for complex system development.”
► Features are functionally complete or toggled so as not to disrupt demonstrable functionality
► New Features work together and with existing functionality
► Happens after the Iteration Review (may lag by as much as one Iteration maximum)
► Demo from a staging environment that resembles production as much as possible
Executing the PI with Built-in Quality
Teams incorporate basic Agile quality practices
Agile quality practices apply to every team, whether business or technology.
► Shift learning left – Reveal problems sooner, take corrective action with minimum impact “Applicable to all teams.”
► Pairing and peer review – Multiple viewpoints enhance work quality and grow knowledge
► Collective ownership and T-shaped skills – Reduce bottlenecks and increase flow
► Artifact standards and definition of done – Ensure consistent quality for each work product
► Workflow automation – Enable small batches and reduce errors
Scalable definition of done
© Scaled Agile. Inc.
ART definition of done
The ART Kanban board
An ART Kanban board is a powerful tool to visualize the flow of Features and Enablers through the ART.
► Helps visualize PI Planning readiness and PI execution progress
► Useful tool for Coach Sync, PO Sync, ART Sync, and problem-solving meetings
► Accessible by RTE and stakeholders for ART Flow measurements
► Makes process policies and decisions visible to the entire ART
Visualize the workflow using an ART Kanban
Working with Kanban boards is lightweight and disciplined.
► All work is visualized, and the progress of individual items is continuously tracked
► Kanban board contains defined states that work moves through
► Stakeholders agree on work-in-process (WIP) limits for selected states and adjust as necessary to improve flow
► Kanban board has explicit policies detailing how work is managed in each state
► Flow through the Kanban board is measured, which informs future improvements
The Kanban board columns
The columns define the individual states in the identified workflow that the Kanban board visualizes.
► Each column represents one state in the defined workflow
► Columns can be split into work area and buffer if more detailed visualization is needed
The Kanban board cards
The Kanban board visualizes the flow of items from left to right. Each item on the board, represented as a card, is a unit of value
that can be created and delivered on the board.
► Each card can be individually created, validated, and delivered
► Similarly-sized pieces of work enable smoother flow through the board
The Kanban board WIP limits
The agreed-upon WIP limits are displayed above each column. These are the limits for how many cards each column can
contain at any time.
► WIP limits adjust demand to capacity at bottlenecks and help flow through the board.
► WIP limits are initially a hypothesis. They will evolve over time as you learn.
Why are WIP limits necessary? To ensure large queues are not forming.
The Kanban board explicit policies
The agreed-upon exit policies for each step in the workflow are displayed above each state on the board.
► These are the things that need to be done for the card to move to the next column
► The visualization of these policies encourages collaboration and removes uncertainty
© Scaled Agile. Inc.
Measuring the flow of value
How efficient is the organization at delivering value to the Customer?
► Flow Metrics provide insights into the efficiency of the delivery pipeline
► Highlights opportunities for removing delays and increasing our speed and agility
Flow distribution
Flow distribution measures the proportion of work items by type in a system.
Flow distribution measures the amount of each type of work in the system at a specific time.
Flow velocity
Flow velocity measures the number of completed work items over a time period.
Flow time
Flow time measures the time elapsed from start to completion for a given work item.
Flow time measures the interval needed for all the steps in a defined workflow to be completed.
Flow load
Flow load measures the number of work items currently in progress (active or waiting).
GLOSSARY Definition
Flow load indicates how many items are currently in the system.
TEXT Verbiage
Flow efficiency
Flow efficiency measures the ratio of the total time spent in value-added work activities divided by the total flow time.
Flow efficiency is the sum of the active time divided by the total time it takes to get the item through the system.
Flow predictability
Flow predictability measures how consistently teams, ARTs, and portfolios are able to meet their commitments.
Art Flow predictability measures how well a train can plan and meet its PI objectives.
Continuous Learning Culture Learning
► Everyone in the organization learns and grows together (Learning Organization)
► Exploration and creativity are part of the organization's DNAv (Innovation Culture)
► Continuously improving Solutions, services, and processes is everyone's responsibility (Relentless Improvement)
Innovation and Planning (IP) Iteration
The Innovation and Planning (IP) Iteration is a unique, dedicated iteration that occurs every PI. It provides an estimating buffer
for meeting PI Objectives and dedicated time for innovation, continuing education, PI Planning, and Inspect and Adapt events.
Innovation: Opportunity for innovation spikes, hackathons, and infrastructure improvements
Planning: Provides for cadence-based planning and is an estimating guard band for cadence-based delivery
Hackathons are innovation events where team members can work on whatever they want, with whomever they want, so long
as the work reflects the mission of the company and they demo their work at the end.
Common anti-patterns
Planning work for the IP Iteration in PI Planning
Leaving testing or bug fixing to the IP Iteration
Leaving integration of the whole system to the IP Iteration
Innovation culture
Leaders must create an environment that supports creative thinking, curiosity, and challenging the status quo.
Keys to building an innovation culture are:
► Innovative people
► Experimentation and feedback
► Time and space for innovation
► Pivoting without mercy or guilt
► “Go see” activities
► Innovation riptides
Enable continuous learning
► The IP Iteration is the perfect time to offer learning opportunities that build common skills across the ART
► The move to Lean-Agile requires many new skills, including:
- Feature/Story writing
- Understanding and applying flow
- Automated testing
- Team building
- Collective ownership
- ART role mastery
Without the IP Iteration
► Lack of delivery capacity buffer impacts predictability
► Little innovation; the tyranny of the urgent
► Technical debt grows uncontrollably
© Scaled Agile. Inc.
► People burn out
► No time for teams to plan, demo, or improve together
Building a Continuous Delivery Pipeline with DevOps
DevOps is a mindset, culture, and set of technical practices that supports the integration, automation, and collaboration
needed to effectively develop and operate a solution.
A CALMR approach to DevOps
Building the Continuous Delivery Pipeline with DevOps
► The Continuous Delivery Pipeline (CDP) represents the workflows, activities, and automation needed to deliver new
functionality more frequently
► Each ART builds and maintains (or shares) a pipeline
► Organizations map their current pipeline into this new structure, remove delays, and improve the efficiency of each step
Three components of the Continuous Delivery Pipeline
1) Continuous Exploration
a. Hypothesize
b. Collaborate & Research (Product Management)
c. Architect
d. Synthesize
2) Continuous Integration
a. Develop
b. Build
c. Test End-to-End
d. Stage
3) Continuous Deployment
a. Deploy
b. Verify
c. Monitor
d. Respond
© Scaled Agile. Inc.
Decouple release elements from the total Solution
Separate deploy from release
► Separate deployment from release
► Hide new functionality under Feature toggles
► Enable testing background and foreground processes in the actual production environment before exposing new
functionality to users
► Consider the timing of the release a business decision
“Decoupling deployment from release enables releasing functionality on demand to meet business needs”
Release on Demand: Making value available when it’s needed
► Release
► Stabilize and Operate
► Measure
► Learn
Fostering Relentless Improvement - Relentless Improvement in SAFe
A commitment to relentless improvement is foundational to the success of SAFe.
► Relentless Improvement is one of the four SAFe Core Values
► Relentless Improvement is a dimension of the Continuous Learning Culture core competency
Improving results with the Inspect & Adapt event
Three parts of Inspect & Adapt (I&A):
1. The PI System Demo
2. Quantitative and Qualitative Measurement
3. Problem-Solving Workshop
► Timebox: 3 – 4 hours per PI
► Attendees: Teams and stakeholders
PI System Demo
At the end of the PI, teams demonstrate the current state of the Solution to the appropriate stakeholders.
► Often led by Product Management, POs, and the System Team
► Attended by Business Owners, ART stakeholders, Product Management, RTE, SM/TCs, and Agile Teams
Quantitative and qualitative measurements
► The teams review Metrics they have agreed to collect
► Facilitated by the RTE
► Timebox: 45 – 60 minutes
Assessing team performance
During the IP Iteration, the PI Objectives for all teams are assigned an actual business value from 1 to 10.
► The RTE and SM/TCs facilitate the business value assignment events between the teams and the Business Owners
► Business Owners evaluate each PI Objective against the stated objectives, including timeliness, content, and quality against
the planned value
► The RTE aggregates and averages the scores across all objectives for the ART
© Scaled Agile. Inc.
Team PI performance report
► The planned total does not include uncommitted objectives
“A team does not commit to uncommitted objectives.”
► Actual total includes uncommitted objectives
calculation (C / C+UC)
► Percent achievement equals actual total divided by the planned total
► A team can achieve greater than 100% (as a result of achieved uncommitted objectives)
► Effort required for uncommitted objectives is included in the load (this is not extra work the team does on weekends)
► Individual team totals are rolled up into the ART Predictability Measure
ART Performance Metrics
► During the I&A, the RTE presents and discusses the ART Predictability Measure as well as any other agreed upon ART Metrics
being collected.
► Discussions should always focus on trends in the Metrics rather than static data snapshots
► Other example Metrics:
– Deployments and releases per PI
– Average cycle time
– PI Feature throughput
– Enabler throughput
– Flow Metrics
The Problem-Solving Workshop (6 steps)
(what is wrong: People, Process, Tools, Programs, and Environment)
After a retrospective, teams use root cause analysis to address the larger impediments that are limiting velocity.
1) Agree on the problem to solve
(What, When, Where, and Impact)
2) Apply root cause analysis and five whys (Why, Why, Why, Why, Why)
3) Identify the biggest root cause using Agree on the problem to solve Pareto analysis
4) Restate the new problem for the biggest
5) Brainstorm solutions
6) Identify improvement backlog items root cause
Agree on the problem to solve
Clearly stating the problem is key to problem identification and correction.
► You must define the problem or situation so that everyone involved in the workshop understands it
► A clearly defined problem focuses your investigation efforts and saves time
► A problem that is not well-defined may result in failure to reach the proper countermeasure
Use Pareto analysis to identify the biggest root cause
► Pareto analysis is a statistical decision technique that uses the 80/20 rule to narrow down the number of actions that
produce the most significant overall effect
► It uses the principle that 20% of root causes can cause 80% of problems
► It is useful where many possible sources and actions are competing
© Scaled Agile. Inc.
Measure outcomes, competency, and flow
Below is a comprehensive and simple model for measuring progress toward Business Agility.
Outcome Metrics
Do our solutions deliver the expected benefits to the business?
► KPIs represent ongoing ‘health’ Metrics that can be used to measure overall business
► Objectives and Key Results (OKRs) define the specific objectives that we are working
toward in order to achieve future success
Flow Metrics
How efficient is the organization at delivering value to the Customer?
► Provide insights into the efficiency of the delivery pipeline
► Highlight opportunities for removing delays and increasing speed and agility
Competency Metrics
How proficient is the organization in the practices that enable Business Agility?
► Organizations use the Seven Core Competency assessments to improve technical and business
practices that support Business Agility
► Levels of proficiency can be compared against the ‘worldwide index’ and other organizations in your
Measure competency: core competency assessments
► One assessment for each one of the Seven Core Competencies
► Assess at a greater level of detail to generate deeper insights
► Measure the progress being made toward a specific core competency
► Identify specific practice
Using SAFe assessments
► Perform assessments to quantify the Lean-Agile journey of the ART using the collective intelligence on the train
► Get help from the SM/TCs and the Agile Teams to perform regular assessments
► Run regular assessments with the key ART roles
Where do we go next?
Growth recommendations are activities designed to increase levels of competency.
1. Identify growth recommendations - Two sources of growth recommendations:
• Create growth recommendations from the assessment data
• Review the provided growth recommendations
2. Create backlog items of improvement opportunities
3. Prioritize backlog items
CRITICAL success factors for effective measurement
© Scaled Agile. Inc.
Systems Thinking (#2 SAFe Lean-Agile Principle)
Attributes of Systems Thinking
► Optimizing a component does not optimize the system
► For the system to behave well as a system, a higher-level understanding of behavior and architecture is required
► The value of a system passes through its interconnections
► A system can evolve no faster than its slowest integration point
The RTE optimizes the full Value Stream
► Most problems with your process will surface as delays
► Most of the time spent getting to market is a result of these delays
► Reducing delays is the fastest way to reduce time-to-market
The RTE moves from bottleneck to bottleneck
► The Value Stream Mapping of your Continuous Delivery Pipeline is an Enabler that helps the RTE identify and remove bottlenecks
► Every system has only one or a few bottlenecks that significantly constrain performance
► Once you have identified and removed the current bottleneck, there will be another bottleneck
© Scaled Agile. Inc.
Optimizing flow - Accelerating flow with the Eight Flow Accelerators (#6 SAFe Lean Principle - Make value flow w/out interruptions)
1. Visualize and limit WIP
5. Work in smaller batches
2. Address bottlenecks
6. Reduce queue lengths
3. Minimize handoffs and dependencies
7. Optimize time ‘in the zone’
4. Get faster feedback
8. Remediate legacy policies and practices
1. Visualize and limit WIP
► Why it matters:
– Excessive WIP decreases team productivity and impedes the flow of value
– Excessive WIP confuses individual and team priorities, causes frequent context switching, and increases waste and overhead
► What to do about it:
– Make current WIP visible
– Set WIP limits to balance WIP against available capacity
2. Address bottlenecks
► Why it matters:
– A bottleneck constrains the productivity of the entire ART
– Teams must address them to improve flow and continuously optimize
► What to do about it:
– Identify bottlenecks and understand their impact
– Assess the improvement impact on the system
– Identify the resolution: bypass? Increase skills towards the bottleneck? Prioritize enablers?
3. Minimize handoffs and dependencies
► Why it matters: Excessive and unnecessary dependencies and handoffs disrupt Team Flow, create delays, and increase context-switching
► What to do about it:
– Use the ART Planning Board to visualize dependencies within and external to the ART
– Foster incremental execution of dependencies
– Organize around value, and reorganize when necessary
4. Get faster feedback
► Why it matters: When feedback is delayed or missing, mistakes pile up quickly, leading to substantial rework for multiple teams, slow
delivery, and unsatisfied Customers.
► What to do about it:
– Determine which types of feedback are missing or inadequate
– Provide Solution telemetry
– Shift reviews left
– Frequently engage with the Customer and Business Owner
5. Work in smaller batches
► Why it matters: Operating in large batches leads to delayed feedback, significant rework, and high variability. Teams have many different
types of batches in play, including feedback batches, integration batches, and deployment batches.
► What to do about It:
– Use recommended cadence and team size
– Provide Solution telemetry
– Ensure enablers support automating the delivery pipeline
– Explicitly plan for small batches
6. Reduce queue lengths
► Why it matters: Queues represent committed work. The longer the queue, the longer the wait time for new functionality to be delivered to
the Customer.
► What to do about it:
– Short Iteration time boxes and crisp Iteration and PI Objectives bring focus
– Ensure all work goes through the backlog
– Enable Product Managers and POs to exert positive yet firm ways to prioritize
– Leave capacity for emergent priorities
7. Optimize time 'in the zone'
► Why it matters: Solution development relies heavily on creativity, focus, and deep, intellectual effort. It may take up to 20 minutes to fully
immerse in work, and a simple external factor may instantly interrupt it.
► What to do about it:
– Continually optimize the efficiency of all meetings
– Maintain Solution health
– Refine what productive collaboration patterns mean to the team
– Make WIP visible, and update limits across teams as needed
8. Remediate legacy policies and practices
► Why it matters: Teams find themselves in a difficult predicament: pretend to conform to conflicting policies and reduce transparency or fight
the system while development is in process, slowing progress and creating friction. We want to be fully Agile, not half.
► What to do about it:
– Know that these impediments likely exist
– Actively solve the issues you can within the teams and ART
– Grant time and space to raise issues
– Raise the visibility of the effects of those out of ART control
© Scaled Agile. Inc.
Servant leadership - A servant leader knows that their own growth comes from facilitating the growth of others who deliver the
The RTE is a servant leader
The RTE focuses on optimizing the flow of value through growing and maturing the teams and roles on the ART.
► This is a challenging, large, and complex task
► The RTE will need coaching support from an on-site SAFe Practice Consultant (SPC)
Eight Behaviors of Servant Leaders
Listens and supports team
• Encourages everyone to express their opinions
members in decision
• Notices hesitant behavior and body language during SAFe events and meetings
• Helps teams identify positive and negative changes during the Inspect & Adapt event
Creates an environment of
• Facilitates PI Planning and shared team events for all ART members and stakeholders
mutual influence
• Asks for opinions/input and carefully considers the response
Understands and
• Shares in celebrating every successful System Demo; feels bad about
empathizes with others
impediments, failures, etc.
Persuades rather than uses
• Asks questions to encourage teams to look at decisions from
new perspectives
• Articulates facts; helps the teams see things they may have
overlooked; helps rethink
Encourages and supports
• Encourages team learning
the personal development
• Fosters collaborative practices like teamwork, Continuous Integration, collective code
of each individual
ownership, short design sessions, and specification workshops
• Encourages rotation in technical areas of concern, such as functionality,
components/layers, and role aspects
• Facilitates team decision-making rather than making decisions for the teams
Thinks beyond day-to-day
• Sets long-term operating goals for the team, such as Lean-Agile practices to master, new
activities; applies Systems
skills to acquire, etc.
• Examines what is missing in order to make the environment better for everyone; prioritizes
improvement activities and makes them happen
Supports the teams’
• Facilitates ad-hoc meetings if needed
• Helps teams access external sources of information like SMEs and shared resources
(architects, UX designers, tech writers)
• Helps clarify and articulate the rationale behind priorities, Milestones, and commitments
• Helps teams prepare for System Demo
• Helps teams find techniques to be more collaborative
Is open and appreciates
• Shows appreciation for team members who raise serious issues
• Encourages and facilitates open communication among team members
• Encourages healthy conflict during team meetings
• Gives open, honest opinions
Stages of high-performing teams
▸Forming teams
▸Establishing ART Vision
▸Establishing ART events
▸Fostering collaboration
▸Surfacing and resolving team conflict
▸Dealing with individual and team performance
▸Fostering relentless improvement
▸Establishing the ART as a community
▸Improving engineering practices
▸Fostering effective communication
PERFORMING ▸Creating space for spontaneous leadership and self-organization across the ART
▸Creating a flow of knowledge across the teams and the ART
© Scaled Agile. Inc.
The RTE can mitigate the five dysfunctions using SAFe
Facilitating large groups
Often during a PI, the RTE will be the facilitator for meetings and events with many people attending. Possible events are:
► Inspect & Adapt (I&A)
► Management review and problem-solving
► PI Planning
► ART Backlog refinement
► ART Sync
► Coach Sync
Large group facilitation preparation and techniques
► Allow social networks to form. Everyone should be in a mindset of safety, and this happens through the natural formation of
social networks.
► Provide clear instructions in writing but offer no more than three steps at a time. Handouts are extremely helpful.
► Design, test, and leverage your audiovisuals.
► Optimize the physical spaces for maximum participation. Round tables and pods are best. Leverage the wall space as well.
► Use video conferencing tool features like polls that can simplify participation in virtual events.
► Timebox everything and use your tools to manage timeboxes.
► Call upon coaches in your organizations to help. You’ll need all the coaching power you can get!
► Create energy through fun!
Identify the steps to create an ART with a one-team culture
Tribal unity: Steps to creating a one-team culture
1. Create a great team
4. Connect the tribe to an idea
- Compose a SAFe Agile Team of ten or fewer individuals - Have a vision
- Form via self-selection
- Communicate the vision
- Use Agile practices
- Learn together
2. Connect the teams and create a tribe
5. Sustaining tribal unity
- Share a collective identity
- Quantify culture with an employee Net Promoter Survey (eNPS)
- Share experiences
- Record and share tribal legends
- Celebrate as a tribe
- Set up successors for success
3. Connect the tribe to its leader
6. Engaging management in tribal unity
- Connect everyone to the leader during Gemba
- Tap into your empathy
- Create an Agile Team of Agile leaders
- Shine a light on a bright spot
- Encourage vulnerability in front of the tribe
- Invite them into Gemba
© Scaled Agile. Inc.
ART Flow
#1 Visualize and Limit WIP
Excessive Work In Process (WIP) significantly decreases ART productivity and impedes value flow. It overloads people and
teams, confuses priorities, causes frequent context switching, and creates long waits for new functionality.
What to do about it:
►Visualize all features in process.
►Establish control with capacity allocation.
#2 Address Bottlenecks
A bottleneck constrains the productivity of the entire ART, teams must address them to improve flow. Once the current bottleneck is resolved,
the next one materializes and must be taken care of to reach the next level of performance. (continuous process)
What to do about it:
►Identify the bottleneck.
►Increase capacity at the bottleneck when possible.
►Understand the full impact.
►Bypassing the bottleneck.
#3 Minimize Handoffs and Dependencies
A ‘handoff’ of information and assets occurs when a work product transitions from one process step to another. And when
situations require a specific person or unique input from another person or a team, a dependency occurs (impede flow).
What to do about it:
►Use the ART planning board to visualize dependencies. ►Optimize the structure of teams.
►Foster incremental execution of dependencies.
►Visualize and manage dependencies with external parties.
►Synchronize frequently.
#4 Get Faster Feedback
Solution development relies on the fast feedback that guides the ART in the right direction. Mistakes pile up quickly when
feedback is delayed or missing, leading to substantial rework for multiple teams, slow delivery, and unsatisfied customers. Two
types of feedback are typically required: Is the ART creating the right thing for the Customer? Is the ART building it right?
What to do about it:
►Assure both types of feedback.
►Integrate and test frequently.
►Provide solution telemetry.
►Use research spikes and MVPs.
►Engage with customers early and often.
# 5 Work in Smaller Batches
Operating in large batches of work leads to information decay, delayed feedback, rework, and high variability.
What to do about it:
►Understand the types and respective sizes of batches. ►Automate a delivery pipeline.
►Use cadence.
►Plan for smaller batches.
►Manage team and ART size.
►Use thin vertical slices of work.
#6 Reduce Queue Lengths
The ART backlog queue contains all the committed feature work awaiting service. The longer that queue, the longer the wait for
the new features to reach the Customer.
What to do about it:
►Keep roadmaps flexible.
►Leave capacity for emergent priorities.
►Establish a strong Product Management function.
#7 Optimize Time ‘In the Zone’
Solution development relies on creativity and the focused intellectual effort of team members.
What to do about it:
►Keep work-in-process low.
►Maintain solution health.
►Frequently integrate work.
►Ensure efficient events.
#8 Remediate Legacy Policies and Practices
Legacy policies and practices present pernicious problems that may occur during and even after a SAFe implementation.
What to do about it:
►Once identified, teams must take corrective action. Action depends on the impediment’s specific stakeholders, nature, and
context. Change agents often discover that many of these stakeholders have not been on the transformation journey and
require additional training and coaching. No change journey is complete until the changes are fully embedded in the culture.
Measuring ART Flow SAFe’s Measure and Grow system provides 3 measurement categories: competency, flow, and outcomes.
Flow Metrics Summary SAFe’s Flow metrics will help highlight ART flow improvement opportunities. However, the numbers
alone cannot tell the whole story. Qualitative analysis, along with good judgment, is needed.
© Scaled Agile. Inc.
Exam breakout: