Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Iterating faster with SAFe

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Here’s a frequently asked question in the SAFe community: I wanted to understand what SAFe says about someone who wants to go faster than 2 weeks of iteration? I mean the whole PI concept is based on 5 iterations worth of planning. What if a team/organization wants to develop and synchronize faster than 2 weeks? Is speed going to be compromised by following the standards of PI cadence?

Here’s my take:

Adjusting Cadence Length in SAFe – Can you? Should you?

SAFe considers the 2-week iteration length as a default rather than a rule.

The question you need to consider is what inspection and adaptation cycle you’re looking to accelerate – the Iteration or the PI.

Basically, do you want an opportunity to tactically adjust priorities more frequently than every 2w? Or do you want to adjust a more strategic direction more often than every 8-12w?

With the answer to that, you can experiment either with iteration length and/or PI length. Of course, the cadence length affects coordination overhead – there’s a fine balance.

Additionally, we’re talking about a Planning, Inspection, and Adaptation cadence – NOT the release cadence. Releases are on-demand meaning can be more frequent (or less).

Iteration Goals and PI Objectives provide us with room to maneuver

Another point to remember is that you can adjust iteration backlogs as long as you’re focusing on iteration goals. And even PI objectives can be adjusted – “Assume Variability Preserve Options”. If it’s occasional adjustment it’s not a reason to necessarily use a faster cadence.

Is team-level Kanban the solution to the need for more flexibility in SAFe?

Many teams think Kanban might be the best choice for them if they need more and more flexibility. Kanban CAN be a better fit if your demand is extremely volatile. I would be very careful though. Doing some level of goal-setting and prioritization and planning on a cadence is a powerful way for a team to focus. Do we really WANT to be a strictly reactive team?

Kanban combined with flexibility with some of the capacity we have each iteration can definitely be helpful and is why we recommend all Agile Teams in SAFe use Kanban to limit their WIP and improve their flow – this actually enables them to change scope even within an Iteration if that’s needed in order to achieve their Goal. (see my recent blog post that talks about dynamic scope in SAFe).

“Kanban Teams” in SAFe have an iteration cadence with the establishment of iteration goals even if not detailed iteration backlogs. Maybe that’s a good fit for your context maybe not. It might be an interesting experiment to try.

What if Planning a PI doesn’t make sense?

Finally, if PI planning doesn’t make sense even if PI is shorter – maybe you need to reflect on SAFes appropriateness for your context or on what’s so volatile about the demand coming your way and whether it’s “nature of the beast” or a systemic impediment to work on …

What’s the Bottom Line

What I tried to show here is that a conversation about what to do when the iteration feels too long should start with “Why”. Get to the bottom of what’s currently not ideal, look at the different options, consider Lean, Agile, and SAFe principles, and figure out whether it makes sense to change the cadence, change your approach to the balance between planning and flexibility, the difference between committing to goals and committing to backlogs, and the role that more flow-oriented techniques such as Kanban can play in addressing your issue.

Interested to hear any thoughts or experiences. Leave us a comment !

Subscribe for Email Updates:

Categories:

Tags:

Process Improvement
ART Success
Frameworks
Agile Project
Planning
Agile and DevOps Journey
Product Ownership
RTE
Kaizen Workshop
speed at scale
Agile Israel Events
Kanban
Scrum Master Role
Agile Marketing
NIT
Spotify
ATDD vs. BDD
Scrum Values
Introduction to ATDD
Managing Projects
Agile Basics
EOS®
Kanban Game
User stories
Scrum With Kanban
Operational Value Stream
Business Agility
Agile Mindset
Jira Cloud
Accelerate Value Delivery At Scale
Kanban Kickstart Example
Amdocs
Agile Testing Practices
LPM
Large Scale Scrum
Product Management
Scrum.org
RSA
Nexus
Agile Techniques
Agility
PI Objectives
Pomodoro Technique
Continuous Improvement
Slides
Lean Budgeting
Lean-Agile Software Development
Kanban Basics
AI
ScrumMaster Tales
System Team
Agile Project Management
Development Value Streams
Scrum
QA
Lean Software Development
SAFe
Value Streams
Acceptance Test-Driven Development
Releases Using Lean
chatgpt
agileisrael
Agile for Embedded Systems
Agile Product Development
Lean Agile Basics
Continuous Delivery
Nexus and Kanban
Professional Scrum Product Owner
Artificial Intelligence
Agile Israel
Tools
Sprint Iteration
The Kanban Method
Test Driven Development
Certified SAFe
Rapid RTC
A Kanban System for Software Engineering
Introduction to Test Driven Development
Agile Release Management
Agile Release Planning
Entrepreneurial Operating System®
Lean Risk Management
Continuous Deployment
Program Increment
Reading List
Manage Budget Creation
Enterprise DevOps
Certification
Agile in the Enterprise
Lean Agile
Daily Scrum
LeSS
Nexus Integration Team
Lean and Agile Principles and Practices
Agile Games
Agile Delivery
Managing Risk on Agile Projects
Lean-Agile Budgeting
Agile Outsourcing
ATDD
Games and Exercises
Limiting Work in Progress
Achieve Business Agility
Hybrid Work
Built-In Quality
Effective Agile Retrospectives
SAFe DevOps
Nexus vs SAFe
Software Development
Nexus and SAFe
Code
Scrum and XP
Lean Agile Organization
Agile Community
Iterative Incremental Development
IT Operations
Release Train Engineer
Kanban 101
Agile Product Ownership
What Is Kanban
Agile Games and Exercises
Software Development Estimation
speed @ scale
DevOps
lean agile change management
Agile Program
Agile India
GanttBan
Jira
WIP
Agile
Portfolio for Jira
Scaled Agile Framework
Risk Management on Agile Projects
Webinar
Scrum Primer
Engineering Practices
Applying Agile Methodology
POPM
Lean Agile Leadership
SA
ALM Tools
Agile Exercises
Perfection Game
Lean and Agile Techniques
Advanced Roadmaps
Elastic Leadership
Risk Management in Kanban
Change Management
Principles of Lean-Agile Leadership
BDD
Agile Contracts Best Practices
Presentation
Quality Assurance
System Archetypes
System Integration Environments
LAB
Professional Scrum with Kanban
Jira admin
SAFe Release Planning
Covid19
Lean Startup
Continuous Integration
TDD
Scrum Master
Legacy Code
Kaizen
Systems Thinking
The Agile Coach
Sprint Planning
Risk-aware Product Development
Professional Scrum Master
ROI
An Appreciative Retrospective
ARTs
Legacy Enterprise
RTE Role
Lean Agile Management
predictability
Story Slicing
Jira Plans
AgileSparks
AI Artificial Intelligence
Sprint Retrospectives
Atlaassian
SPC
Agile Risk Management
Self-organization
Implementation of Lean and Agile
Implementing SAFe
Video
Scrum Guide
Coaching Agile Teams
Agile Assembly Architecture
Atlassian
Agile Development
Tips
Continuous Planning
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart