Publications

An agile way of working spread to 5,000 practitioners within two years by using an Essence-based Practice Architecture A sustainable path to agility was created - teams could incrementally improve their way of working and growing Practices provided standardization which helped practitioners share and learn best practices

Increased efficiency with teams aligned and working together Greater creativity as teams are empowered to make decisions Management aligned and supportive of agile teams

This paper discusses IJI's proven approach to sustainable change, and how under proper guidance from a well-formed Change Initiative, Practice Hubs, Coaching Hubs, and Communities of Practice can help make change "stick".

A series of examples and case studies on how people have used the Scrum Essentials cards to benefit their teams and improve how they work.

Use cases have been around for almost 30 years as a requirements approach and have been part of the inspiration for more-recent techniques such as user stories. Now the inspiration has flown in the other direction. Use-Case 2.0 is the new generation of use-case-driven development—light, agile, and lean—inspired by user stories and the agile methodologies Scrum and Kanban. Use-Case 2.0 has all the popular values from the past—not just supporting requirements, but also architecture, design, test, and user experience—and it is instrumental in business modeling and software reuse.

As with any new initiative people are struggling to see how it fits into the world and how it relates to all the other things going on. For example does it improve or replace their current ways of working. Is it something like lean that supports and furthers the aims of the Agile Movement, or is it something like waterfall planning that is in opposition to an agile approach? The good news is that both Agile and SEMAT promote non-prescriptive value-based philosophies that encourage software development teams to select and use whatever practices best fit their context and, most importantly, continuously inspect, adapt and improve their way of working. In this keynote we will look at how these two initiatives complement one another, providing the perfect foundation for teams that want to master the art of software development.

Combining agile and SEMAT yields more advantages than either one alone. This paper discusses how two current popular movements complement one another to provide a powerful basis for software development.

New article published on ACM Queue discusses two powerful complementary movements in software development.

The Agile Architecture Essentials practice provides guidance for achieving just-in-time architecture preparation and continuous and emergent evolution of the software system.

A modularized set of interchangeable practices that enable organizations to scale agile smoothly as part of a tailored transformation program that delivers value early and often, and builds a flexible and long-lasting library of practices, able to flex and grow over time in response to changing technology and business challenges.