Scaled Agile

Scaled Agile Inc. have just announced SAFe 6.0, the latest version of the Scaled Agile Framework. The changes realign their core values and rephrase a key principle amongst many other tweaks and adjustments throughout the framework. Ivar Jacobson Intl. have updated the widely utilised SAFe® Principle cards to reflect the changes in SAFe 6.0. ### What are the SAFe® Principles? In addition to fully supporting the agile manifesto and its 12 agile principles, SAFe® introduces the following ten complementary lean-agile principles: SAFe® LEAN AGILE...

The Program Board is generated during PI Planning and is used by the teams to visualise delivery and coordinate collaborations during a PI. This article looks at the Program Board's use during PI Execution.

The Program Board is generated during PI Planning and is used by the teams to visualise delivery and coordinate collaborations during a PI. This article looks at the Program Board's use during PI Planning.

Portfolios should set Work-In-Process limits on what they do to ensure that the organisation focuses on getting things done. This post looks at factors that influence how those Work-In-Process limts should be set and explores how it's not a simple numeric limit.

The Program Board is generated during PI Planning and is used by the teams to visualise delivery and coordinate collaborations during a PI. This article looks at the Program Board's setup and structure.

The Square Kilometre Array (SKA) Observatory is of immense global consequence, with a mission to build and operate cutting edge radio telescopes that will transform our understanding of the universe. They are doing this by building an unprecedented number of receivers across multiple continents. The SKA is designed to observe radio emissions such as those radiating from neutral Hydrogen. Hydrogen is the most common element in the universe, spanning our planetary neighbours all the way out to the very early beginnings of our universe but is invisible at optical wavelengths. Studying its...

Welcome to the amalgamation of a short series of articles on crafting effective, well-formed objectives as part of the SAFe® Program Increment (PI) / Big Room Planning activity. We have seen a lot of confusion surrounding the use of PI objectives; confusion that often results in: Resistance to their use and; The production of poorly formed team objectives that appear to be completely redundant as they just list the Features being addressed. The first step to creating well-formed, useful objectives is for everyone to understand why they are so important. Covered in this document: Why do we need PI Objectives when we have Features? Writing good PI Objectives PI Objectives and the PI Planning Process PI Objectives Beyond PI Planning: Reaffirming and Monitoring Your Commitments  

The Scaled Agile Framework's recommended approach for prioritisation within the Portfolio is to use Weighted Shortest Job First (WSJF), but there are some challenges when trying to run WSJF at the Portfolio level. This series of posts explores those challenges, with this post focusing on what happens when Total Epic Effort is used within WSJF.

In this series of posts we wil explore the Events that either perform, schedule or track the activities that affect the Lifecycle of an Epic. This second post looks at how the events that run the Portfolio could be structured.

In this series of posts we wil explore the Events that either perform, schedule or track the activities that affect the Lifecycle of an Epic. This first post looks at the activites that the Portfolio needs to perform in order for it to make progress.