Blog

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 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.

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.

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. In this post we’ll explore the Portfolio Kanban that visualises the lifecycle of an Epic and look at some of the decisions that influence the Epic’s progress through its lifecycle.