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:

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