Scaled Agile Framework

A Four Part Webinar Series

Effective Product Management requires constant interaction with the customers and the developers, and awesome listening, negotiation, synthesis, communication and leadership skills, all of which can easily get lost if our focus is purely on which User Stories to focus on next. In this series of webinars, Ian Spence explores the value of treating Features as first class citizens as part of a hypothesis-driven approach, and how we can then use the analysis of these Features to improve our development value streams

So what does it mean for a Feature to be “Ready”? And just as importantly when do they need to be “Ready”?** Definition of Ready can be a dangerous thing leading to waterfall behavior and strict hand-overs between Product Owners and their teams. To help resolve these issues, IJI has developed a set of 6 mini-checklist cards that together define the lifecycle of a Feature to use when preparing features for PI Planning.

Easy to Use Cards

The SAFe® principles are very powerful but they can be quite hard for people to understand and therefore whole-heartedly support. To this end, IJI has produced a set of cards that we believe present the nine SAFe® principles in a self-contained, readily accessible fashion — allowing executives, leaders, and team members to readily understand them and quickly assess their relevance. This is something that is invaluable at any stage of a SAFe® adoption.

EM360 Interviews Ian Spence

In EM360’s Podcast interview, Ian speaks about his experiences of specialising in large-scale agile adoptions. Drawing on his expert knowledge, Ian has worked with hundreds of projects to introduce iterative and agile practices in sectors as diverse as government, telecommunications, finance, and internet start-ups.

Scaled Agile Announcement: January 30, 2018

Scaled Agile, Inc. today announced the induction of Ian Spence as a new Fellow into the SAFe Fellow program. The SAFe Fellow achievement is Scaled Agile’s most prestigious distinction, recognizing individuals who have exhibited the highest levels of thought leadership and transformational expertise for implementing the Scaled Agile Framework® (SAFe).

Ian met the SAFe Fellow requirements based on his ongoing contribution to the evolution of the Framework, his demonstrated success in implementing SAFe implementations in a broad range of industries and disciplines, and his willingness to share his expertise publicly through writing and speaking.

Part 4: Some practical tips to avoid waterfalling features

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.

Part 3: What Does it Mean 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 3 of this series, Ian Spence provides guidance on what it means for a Feature to be Ready.

7+Sins-Feature Preparation

Part 2: The Seven Deadly Sins of Feature Preparation

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.

Easy to Use Cards

The SAFe® principles are very powerful but our coaching and consulting experiences have shown that, as currently presented, they are far less accessible and intuitive than the Agile Manifesto and its supporting 12 Agile Principles. In line with the release of 4.5 of SAFe®, which simplifies and enhances the SAFe® big picture, we have produced a set of cards that we believe do the same for the underlying SAFe® Principles. The cards present the nine principles in a self-contained, readily accessible fashion — allowing executives, leaders, and team members to readily understand the principles and quickly assess their relevance. Download the cards today to help your teams be SAFe®.

This blog post introduces the SAFe Principle Cards produced by Ian Spence (SPCT) with help from Brian Kerr (SPC) and Brian Tucker (SPCT).

Pages

Subscribe to RSS - Scaled Agile Framework