What comes in mind when you listen the term “Agile Requirement”?

Usually, it is not referring exactly to a concrete requirement, but rather to some requirements engineering related process. The title Agile Requirement usually refers to techniques as User Stories, Story Mapping, Acceptance Criteria, BDD, Prototyping, Backlog Management, Kanban… focused on software development projects using an agile approach.

The usual definition: “The development team must be able to change a requirement during the solution development project to maximize the value delivered by the project”.
The new definition proposed bellow is more comprehensive, applicable to both agile and cascade approaches and oriented to business agility. And it is not about processes, but it is a real concrete requirement that must be added to all digital transformation initiatives.

The agile requirement new definition: “The business manager must be able to dynamically reconfigure business behavior to maximize customer value without the need for a new development project.

Learning Objectives:

• Ignite business agility with dynamically configurable solutions
• Use the agile requirement to stimulate your team’s creativity
• Model business as configurable processes and rules