Table of Contents

User Stories

When it comes to understanding the needs of customers and conveying it to developers, a lot of detail is missing.

With AMMERSE, you provide different strategic Sets which are evaluated and understood, thereby providing clear gap analysis between different views of the same story.

By creating and evaluating the product owner’s vision and the developer’s technical vision, we can begin to bridge gaps and understand the different views. Also as a decision, the AMMERSE Set creates a proper record of what has been done and why. Consider a product owner who always promotes R (1), S (1), to the detriment of other principles, creating TechnicalDebt. After looking at completed stories and the AMMERSE Set that was used for the story (perhaps together with an AMMERSE ADR), you will see patterns of good or bad decision making.


Substack Newsletter

Sign up to our newsletter and collaborate.

Join the free newsletter


Level 1

7 Principles: Agile, Minimal, Maintainable, Environmental, Reachable, Solvable, Extensible.

Level 2

The AMMERSE Set has weights assigned to 7 Principles. eg. “Enterprise Strategy”.

Level 3

AMMERSE Sets in a grouping that work together for a purpose. eg. Modes.

Level 3.1

You can extend AMMERSE by creating your own Sets and Frameworks.

Our goal is to enable business strategy, implementation and the reaching of objectives by giving you the tools to design your own methods. 

Sign up for the occasional email