We will use various weapons of demand splitting in practice. Here are some commonly used weapons: role, entity, purpose, solution, data object, business operation, business process, "personality-commonality" principle, "simple- Complexity” principles, etc., these weapons help us gradually break down from the initial product vision to the development requirements in iterative delivery.
The figure below illustrates the use scenarios of various weapons in different stages in general. Iteration 0 is a very critical stage, which will prepare for future iterations in terms of requirements, design, and teams. As far as the category of demand is concerned, this stage will gradually split and understand the demand according to these weapons, and ensure that the demand is not excessively analyzed, no additional waste is generated, and the changing demand is adapted to the minimum cost.
System-level stories include "non-functional requirements" and "functional requirements", and "technical requirements" are added to architecture-level stories.
The "individuality-commonality" principle and the "simple-complexity" principle are the two commonly used weapons in our separation of non-functional requirements and technical requirements.
Development-level stories are prepared ahead of time during the iteration process based on priorities and the development capabilities of the team. The time and amount of preparation will depend on the degree of change in demand.