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:

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