Contact

Resources

Program Board

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.

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.

Image of part of a concept map used by IJI consultants to explain Lean Portfolio Management (LPM) principles in this instance structuring portfolio events.

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.

Image of part of a concept map used by IJI consultants to explain Lean Portfolio Management (LPM) principles in this instance Portfolio Events - exploring the decisions being made.

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.

Image depicting Lean Portfolio Management LPM portfolio kanban board or canvas.  Part of the LPM series, this article specifically covers On The Nature Of Portfolios - Portfolio Kanban - Alternative Scenarios

Epics have a lifecycle, they don’t magically appear fully formed. There is work to be done to progressively elaborate a business case and if the Epic is approved then there is further work to progress the Epic through implementation. This post looks at some of the alternate scenarios that might be seen in the Epic lifecycle, covering Bad Ideas, Small Ideas, Lean-Startup and Exploring Options.

Contact Us