Contact

White papers

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.

Agile Essentials - Learn how to improve your agility

Agile rightly puts great store on the critical importance of transparency in all things at all times. To build trust and enable predictability, we need it to be transparently clear to all stakeholders what we are doing, how we are doing it, why we are doing it that way, and how well it is going - i.e. what progress are we making towards achieving the required outcomes. The Agile Essentials puts a toolkit of productive process tools literally into the hands of software development professionals, where it can deliver value every day in prompting and guiding the team and supporting team communication and collaboration.

Creating Sustainable Agile Change Paper Image

In this fast-paced, responsive world, software development teams are adopting agile techniques to speed up development times and reduce risks, while simultaneously becoming more responsive to the needs of their customers. Many organisations have kick-started their agile journey and many have successfully introduced agile on a team basis; however, the real challenge is ensuring that agile can scale and is sustainable as corporate plans and personnel evolve over time. Helping organizations embed, sustain and scale agile ways of working is at the heart of Ivar Jacobson International's (IJI) expertise, skillset and intellectual property.

ABC of Essentialization

To be agile as teams, we need to adjust our approach to meet our immediate challenges and needs. To be agile as an organization, we need to learn collectively and evolve our approach over time to support our evolving mission, so that we continue to excel in an ever-changing environment. We would not call a TV set “adaptive” if, in order to adjust the volume, we had to throw it away and replace it with a model with a different volume setting. So why are we prepared to accept process frameworks that leave us in a similar predicament every time we want to improve our product development performance as an organization?

Contact Us