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

Blog

Agile

Iterating faster with SAFe

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?

Read More »
Product Management

Handling scope change during a SAFe Program Increment (PI)

How do we handle Scope Changes in a SAFe Program Increment?

A question about handling scope changes in SAFe was posed recently on a forum I’m participating in (The SAFe Community Forum). This is a question posed regularly in training and on ARTs I’m coaching so I thought I’d provide my thoughts here.

Read More »
Program Board Discussion
Scaled Agile Framework

SAFe Program Dependency Board Retrospective

Learning from the SAFe Program Dependency Board

The SAFe Program Board or Program Dependency Board is a key artifact used in PI Planning and Execution. The ART Teams and Stakeholders used it to align, anticipate risks, and adapt the plan accordingly.

This “inspection and adaptation” of the plan based on insights from the Program Dependency Board is “first loop learning” – making changes in the plan based on what we see.

Read More »
Business Agility

The difference between Planned vs Actual vs Actual Actual Business Value when it comes to SAFe PI Objectives

Actual is a relative term when it comes to business value delivered by a SAFe PI Objective. We had a discussion about this a couple of weeks ago in an Implementing SAFe class and I promised a blog post about this. Here it goes.

Planned Business Value – Making sure Business Owners and the Agile Team are on the same page

Let’s start from the basics though. PI (Program Increment) Objectives are used as a “back briefing” mechanism by Agile Teams on an Agile Release Train to share their plan for the PI and validate that they are indeed focusing on the highest priorities and are planning to deliver objectives that will be valuable for the business.

Read More »
Subscribe for Email Updates:

Most New:

Categories:

Tags:

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

Contact Us

Request for additional information and prices

This website uses Cookies to provide a better experience
Shopping cart