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:

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