Scaled Agile

Stories, or User Stories, are a common way to express each backlog item for a single team to complete within one Iteration or Sprint. Lots has been written over the years about how to write good stories; so why are so many stories still bad? In this webinar we describe where the user story concept came from, the true purpose of stories and explain ways that teams can avoid falling into the trap of doing work rather than delivering value. We describe how in SAFe the purpose of stories can be different to other agile development practices, since SAFe describes a Feature as being a releasable item, not an individual story. And we explain strategies to slice a SAFe Feature into stories.

A single backlog of work shared by many people focuses and aligns their work towards the most important work items. In SAFe, an ART Backlog of Features is used to align the work of multiple teams in the ART to the most important work items. However there are many pitfalls that must be avoided when writing Features for the ART backlog. Bad Features will result in poor work throughput, unaligned and disempowered teams. In this webinar we describe some of the strategies you can follow when writing Features to encourage agility as well as improve productivity.

A single backlog of work shared by many people focuses and aligns their work towards the most important work items. In SAFe, an ART Backlog of Features is used to align the work of multiple teams in the ART to the most important work items. However there are many pitfalls that must be avoided when writing Features for the ART backlog. Bad Features will result in poor work throughput, unaligned and disempowered teams. In this webinar we describe some of the strategies you can follow when writing Features to encourage agility as well as improve productivity.

Question & Answers Questions & Answers from the webinar on Writing Better Epics In SAFe Sign up for the remaining webinars var ss_form = {'account': 'MzawMDE1MTI2AwA', 'formID': 'M7BMSTayNDLUtTS3tNA1SUwx0k00MTHRTUqzALItTEwTjU0B'}; ss_form.width = '100%'; ss_form.domain = 'app-3QN6TZF8X8.marketingautomation.services'; // ss_form.hidden = {'field_id': 'value'}; // Modify this for sending hidden variables, or overriding values // ss_form.target_id = 'target'; // Optional parameter: forms will be placed inside the element with the specified id //...

When Is An Epic done? “Always show your working out!" was the mantra of my maths teacher in senior school. This series of blog posts “On the Nature of Lean Portfolios" is an exploration of Lean Portfolios. It is the thought processes running through my mind, exploring the possibilities so that I understand why things are happening rather than just doing those things blindly. It is not intended to be a fait-accompli presentation of the solutions within Lean Portfolios but an exploration of the Problems to understand whether the solutions make sense. There are no guarantees that these...

How do Epics get work done? How do they get work done in a manner that respects the Lean/Agile Principles and Values rather than replicating the old processes.

What should you be considering when approving Epics? The Epic needs to be considered within the context of the Portfolio rather than in isolation. What is that wider portfolio context?

Free Scaled Agile Framework® Webinar Series! We’re excited to announce a new, completely free upcoming webinar series to help guide you on writing better Epics, Features, and User Stories in SAFe...

An exploration of the activities that an Epic Owner needs to perform to progress an Epic through it's lifecycle.

PI Planning is a core mechanic within SAFe; it’s one of the few things that SAFe does that is unique to it amongst all the other scaling frameworks. This series of articles presents IJI's interpretation of how PI planning should be done and, maybe more importantly, why we think it should be done this way. This article covers retrospection and adaption of the PI Planning process and what to be wary of when adapting.