Publications

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

Industrial-­scale agile requires much more than just being able to scale agile. It also means taking a disciplined approach to ensuring that our IT investments are resulting in sustainable benefits for both the producing organization and its customers. This involves adopting a different approach to many aspects of agility. We need to look beyond small-­scale agile, beyond independent competitive islands of agile excellence, beyond individual craftsmanship and heroic teams, and beyond the short-­term, instant gratification that seems to be the focus of many well-­intentioned but self-­centered agile teams. It is this adoption of a more holistic approach that we call moving from craft to engineering. This paper is published at acm.org.

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.

The challenges for many organizations when adopting DSDM (Dynamic System Development Method) are around mind set change, awareness and communication. The Essence standard helps teams navigate through many of the complex challenges common in software development delivery from helping teams identify and engage with the right stakeholders at the right time in the right way, to making health and progress visible to all in a language that everyone can understand. The Essence standard is presented in a number of tools such as a deck of Alpha State Cards, which are a simple, easy way to track status of a software project and help plan next steps. Applying Alpha State Cards with the DSDM Framework helps portray the aforementioned and enable communication between team members.

Change. This simple word has been used to create communities, build businesses, and promote adoption within a myriad of other actionable objectives. It is as common as the air we breathe and as revolutionary as any invention. Yet in all of its grandeur, it has incessantly stumped many businesses and individuals along the way. Software has taken a front seat in several organizations. It has become the core to any business, and change initiatives have sprouted and evolved to provide better solutions, be they faster, smarter or more affordable. Furthermore, for those organizations that adapt to change well and continue to sustain said changes and evolve over time, the rewards are exponential and in many cases, lasting. As new companies emerge in markets offering innovative solutions that can ultimately disrupt the market, those organization that cannot and or will not adapt and change, and perhaps more importantly, sustain change will lose. As a result, software development teams are adopting agile development techniques to shorten development times, decrease risk, all whilst developing solutions to become more responsive to the needs of the business.

This instructional guide provides a brief introduction to the Alphas and presents seven different games that can be played with the Alpha State Cards by software development teams.

SEMAT (Software Engineering Methods and Theory) is an international initiative designed to identify a common ground, or universal standard, for software engineering. It is supported by some of the most distinguished contributors to the field. Creating a simple language to describe methods and practices, the SEMAT team expresses this common ground as a kernel–or framework–of elements essential to all software development. The Essence of Software Engineering introduces this kernel and shows how to apply it when developing software and communicating among teams and team members. It is a book for software professionals, not methodologists. Its usefulness to developers, who need to evaluate and choose the best practices for their particular projects, goes well beyond the description or application of any single methodology.

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.