Under agile development, how to integrate requirements analysis, architecture (software) design, development and testing, one go-style integration and efficient completion?

In product development, it often happens that similar " Potato Peeling " 's tragedy.

tragedies happen, often because we only pass the " What functions do you want to make " to developers. Without an effective and lightweight practice, it is possible to verify that developers are really capable of translating the " user's needs " into a "before formally entering an iterative development" executable code "?

" Scene Tree " is a combination Use case , Domain driven Design, UML the agile practices of lightweight visualizations.

through the scene tree, you can confirm that the developer has been designed .:
①User Storyof the"Practice Scenarios".

② generated by a practice scenario " Entity ( Entity ) " .

③ required by each entity " Test Latitude " .

So, when a developer can already when User story needs are translated into the scene tree, not only does the developer understand the requirements sufficiently, but also proves that the developer has a clear idea of how to translate the requirements into executable and testable code.

on the other hand, developers can rely on the scene tree,easy and straightforward to complete...
①User StorySelection of design patterns;Domain ModelorTransaction Script.

② User Story in the Entity with the Value Object the design.

③ User Story test case latitude and the design of the test data.

A "scene tree"; an extremely simple and lightweight practice that enables developers to integrate requirements analysis, architecture (software) design, development and testing, and one go-style integration and efficient completion.

If, you are interested to know, who invented the scene tree , please contact me.

Under agile development, how to integrate requirements analysis, architecture (software) design, development and testing, one go-style integration and efficient completion?