Resources

Ivar Jacobson International (IJI) and Dr. Alistair Cockburn | Humans and Technology Inc. are delighted to announce a partnership to describe and raise awareness for Hexagonal Architecture based on the Essence standard.

Agile is becoming widespread across industries, but its adoption in hardware development has been slower compared to software. Many companies have embarked on Agile journeys, but not all have succeeded, and success often takes different forms. For hardware companies with no prior Agile exposure, understanding where to start can be challenging, especially considering the modest guidance available on the topic. This article provides a roadmap to guide you through a successful Agile transformation in hardware development.

Essence and its many use cases are becoming more widely adopted, and as a consequence its content is growing. Therefore, we have created a new website, Essify.com, which will eventually replace our current Essence-focused webpages on IJI's website.

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.

This page provides a summary and recap of the Webinar: Writing Better Epics in SAFe, that took place on the 11th July 2024. It contains a video replay for anyone who missed it plus a transcription of the voice-over for detailed study. We hope you find it useful.