Resources

Image of the Essence WorkBench Logo

The page explains how to play the Values Spotlight serious game using Essence WorkBench. It covers, the what, why and how of the activity.

Image of the Essence WorkBench Logo

The page explains how to map your way of working using Essence WorkBench. It covers, the what, why and how of the activity.

Image of the Essence WorkBench Logo

The page explains how to undertake a method agnostic healthcheck using Essence WorkBench. It covers, the what, why and how of the activity.

Image summarizing the requirements spine of SAFe, Epics, Features and User Stories

Recently I’ve been having to contemplate what makes a “Good” Epic. Obviously, definitions of “Good” are going to vary but if you’re going to define good then you need to examine the characteristics of an Epic to the be able to characterise good.

Image of the Essence WorkBench Logo

This page gives an introduction on the initial things that you will need to do as you get started with Essence WorkBench

SAFe Dispersed PI Planning Diagram - how to run PI Planning events remotely

With more and more people working from home, many organisations that have adopted SAFe® are having to adapt their processes in order to accommodate completely dispersed teams.

24 Questions - why Essence is not just another method white paper

Written by Dr. Ivar Jacobson, Paul E. McMahon and Roland Racko Over the years, collective experience of the authors has revealed many questions on the SEMAT and Essence initiative. To bring clarity of the initiative to our readers, the authors have answered 24 of the most common questions.

The Essentials of Modern Software Engineering: the book cover

An in-depth introduction to software engineering that uses a systematic, universal kernel called Essence to teach essential elements of all software engineering methods

Ivar Jacobson Speaks about Agile and Essence in this podcast

Shane Hastie, Lead Editor for Culture & Methods, invited Dr Ivar Jacobson to his podcast to speak about his work defining the essence of software engineering.

Dr Ivar Jacobson talks about Use Cases in Agile Development - Podcast

Key Takeaways Use Case 2.0 expand on the ideas embodied in user stories Some up-front design is needed in all software development projects For any product you need the skeleton system that has the key requirements embodied in it early on Any system should be able to be represented by between 10 and 20 key use cases