Fast, up-to-date and stable: This can describe a software solution or a racing bike model – the exact meaning depends on the context.
Context is also crucial in agile software development. Thus, requirements form the core foundation, and at the same time they pose major challenges for everyone involved. This is because requirements are passed on in a communication process and it is communication that is often the cause of misunderstandings between different parties when differen t contexts are brought in.
What does this mean concretely?
When passing on requirements – in the agile environment, these are summarized in "user stories" – the following errors can occur:
- Observation errors
- Remembrance errors
- Interpretation errors
- Ambiguity of the problem definition
These errors can run through the entire software development process. The later they are discovered, the higher the cost to correct them. Ideally, the highlighted risks are identified and corrected before their implementation.