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.
