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:

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