Contact

Blog

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

Many teams struggle to let go of their waterfall, silo mentality when they first transition to agile ways-of-working. In particular they shy away from collaboratively working on the definition, evolution and implementation of their backlog items insisting on up-front definition of Features and Stories, and clean handovers between the Product Owners and the Development Teams. This is an issue that we see with all the various agile methods but which always seems to get compounded whenever teams try to scale. So what are the worst things you can do to compromise the agility of your program when using Features? In Part 4 of this series, Ian Spence provides some practical tips to avoid waterfalling your features.

Preparing Features for PI Planning: SAFe

Many teams struggle to let go of their waterfall, silo mentality when they first transition to agile ways-of-working. In particular they shy away from collaboratively working on the definition, evolution and implementation of their backlog items insisting on up-front definition of Features and Stories, and clean handovers between the Product Owners and the Development Teams. This is an issue that we see with all the various agile methods but which always seems to get compounded whenever teams try to scale. In this short blog series we will look at how this tendency towards waterfall thinking can seriously hinder team’s adopting SAFe® and working with a Program Backlog full of Features. We will also provide some advice on how to get your Features Ready without succumbing to premature Story writing.

Free Agile Resources - Feature State Cards from Essence Agility Pack

Many teams struggle to let go of their waterfall, silo mentality when they first transition to agile ways-of-working. In particular they shy away from collaboratively working on the definition, evolution and implementation of their backlog items insisting on up-front definition of Features and Stories, and clean handovers between the Product Owners and the Development Teams. This is an issue that we see with all the various agile methods but which always seems to get compounded whenever teams try to scale. So what are the worst things you can do to compromise the agility of your program when using Features? In Part 3 of this series, Ian Spence provides guidance on what it means for a Feature to be Ready.

Many teams struggle to let go of their waterfall, silo mentality when they first transition to agile ways-of-working. In particular they shy away from collaboratively working on the definition, evolution and implementation of their backlog items insisting on up-front definition of Features and Stories, and clean handovers between the Product Owners and the Development Teams. This is an issue that we see with all the various agile methods but which always seems to get compounded whenever teams try to scale. So what are the worst things you can do to compromise the agility of your program when using Features? In Part 2 of this series, Ian Spence defines the seven deadly sins of feature preparation, and the most wasteful practices we have seen teams adopt in an attempt to be better prepared for the PI Planning event.

Many teams struggle to let go of their waterfall, silo mentality when they first transition to agile ways-of-working. In particular they shy away from collaboratively working on the definition, evolution and implementation of their backlog items insisting on up-front definition of Features and Stories, and clean handovers between the Product Owners and the Development Teams. This is an issue that we see with all the various agile methods but which always seems to get compounded whenever teams try to scale. So what are the worst things you can do to compromise the agility of your program when using Features? In Part 4 of this series, Ian Spence provides some practical tips to avoid waterfalling your features.

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.

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.

Contact Us