Actual is a relative term when it comes to business value delivered by a SAFe PI Objective. Planned Business Value — Making sure Business Owners and the Agile Team are on the same page Let’s start from the basics though. PI (Planning Increment) Objectives are used as a “back briefing” mechanism by Agile Teams on an Agile Release …
We find it crucial to emphasize when training new SAFe Program Consultants (SPCs) that they should use SAFe as a framework, not a methodology. First, what’s the difference between a framework and a methodology? I found this concise, useful comparison written by Liz Keogh, who I think highly of over at Quora – A methodology …
In the scaled Agile framework, one key role is the Release Train Engineer (RTE). But who should I look for to fill this role? What are the first few process improvements experienced RTE’s typically do? Yuval Yeret (Yeret Agility) and Mattias Skarin (Crisp) took the time to discuss the traits of a good RTE. What …
I just shared my perspective that SAFe isn’t a hard-coded methodology and while it gives you a comprehensive and to some even overwhelming set of practices, there are still a lot of choices. My old friend Sutap suggested: Would be great if you can share examples around how SAFe is not a one size fits …
A recent discussion on the Scrum Alliance Linkedin group was around Mike Beedle’s claim that “Hard-coded Frameworks are neither Agile or Frameworks” which is clearly aimed primarily at SAFe. I admit to thinking something similar before really getting to know SAFe in depth. Over time I realized SAFe isn’t one size fits all. Far from …
This week I’m in Fort Lauderdale, Florida speaking at the Lean/Agile US conference. The subject of my talk today was “Introduction to Lean/Agile scaling approaches” where talked about why scaling approaches are necessary and when to actually try to de-scale as well as gave a very brief introduction to a couple of the key frameworks …
Last week I helped facilitate Program Increment (PI) Planning for an Agile Release Train (ART) practicing the Scaled Agile Framework (SAFe). One impediment for this ART was that although the leadership team ROAMed risks in PI Planning as well as continued to manage the flow of risks/issues using a ROAMing Kanban Board throughout PI execution, …
Invitation and Pull-based approaches for implementing agile at scale has been a reoccurring theme in my work, writing and talks in recent years — including my talk at Agile 2016 and this series on my blog. In recent months I was working on a SAFe guidance article on this topic. Richard Knaster as well as Dean Leffingwell …
What is the connection between Uncertainty and the Scaled Agile Framework? Uncertainty is one of the core reasons we need to be agile. Different modes of Business/Requirements/Technology uncertainties impact our economic costs in product development – especially the potential impact of risk. The first principle of SAFe™ is “Take an economic view”. I frequently use …