Impact-driven Scrum development by Sara Lerén
Impact-driven Scrum development
Well-functioning Scrum teams have proved to be good at delivering working software, but that does not necessarily mean that they deliver optimal, or even expected, business value. Agile is becoming the standard way of developing software, and the understanding of the value of User Experience (UX) is increasing. Business Impact Mapping and Management (BIMM) is a method that ensures value creation by focusing on the expected business value in relation to the user needs.
The most visible artifact in BIMM is the Business Impact Map. The map follows a simple and most helpful formalism that makes it useful throughout development projects as well as in maintenance. It reveals priorities and expected outcomes in a way that makes it possible to use for verification and validation during any given moment. In short - the Business Impact Map gives such a clear definition of the business requirements that it can be used for managing approval of design suggestions or solutions.
Business Impact Management is the framework for managing decisions in such a way that the expected business value is secured along the way. The most important tool for securing value is testing with users. Since the Business Impact Map defines actionable metrics for the outcome in use, it makes it possible to evaluate and validate if proposed solutions will result in expected user value, that later - in a full scale use - will result in expected business impact.
BIMM is a method for ensuring business and user value. The Business Impact Map is an excellent way of expressing business requirements for any product or service. Excellent, since it defines the expected outcome in a way that can be used for continuous evaluation from the early stage, during development and all the way into maintenance. BIMM prefers, but does not require Scrum for the building part of the project. Scrum offers very clear tools for handling business value and evaluating design which creates great potential for ensuring that needs are met and that value is created.
The idea of BIMM was initially published in the article “From Business to Buttons” at the 7th International Design Conference in Dubrovnik, 2002. In 2004, the book “Effektstyrning av IT” by Ingrid Domingues and Johan Berndtsson was published, and later in 2007 the english version “Effect Managing IT”. During the 10+ years of practice and teaching Business Impact Mapping, some important insights have enhanced the method in a profound way. Today the method is wide spread and used as inspiration for governmental frameworks, but also by management and design bureaus. It has also inspired the Agile community to a way of mapping requirements called “Impact mapping”.
Product Owners, Architects, Designers, Managers, Scrum Masters, Project Leaders
Experience from Agile development
Projected learning outcomes / lessons learned:
The workshop will give a hands-on walk-through of the method with engaging examples from real life development projects. You will learn about how to define the Business Impact and User requirements in such a way that it can be used for managing design and builds in Scrum development. You will learn how to use the Business Impact Map in the creation of the Road Map/Release plan, User Stories and their acceptance criteria as well as in the validation of designs. At the end of the workshop you will have laughed at the problems and acquired a new way of defining requirements, reasoning about design and ensuring quality in agile development.
Ingrid Domingues is the woman behind Business Impact Mapping and Management, and the author of several books on the subject. She has spent more than two decades designing digital experiences, and her speciality is defining needs and metrics. Ingrid is also one of the founders of one of Scandinavia's leading UX agencies, inUse.
|Last Updated||15 Aug 07:14|