Changes
/* Requirement Supply Chain */
For every software development task, maybe even for every task in any project, but certainly in {{UBIK}} projects, there is a basic sequence of dependencies:
# '''Requirements''' - before you can do anything, you must know the goal and agree on it with the customer. There should be a definition-of-done for this task, also called "acceptance criteria" that can be defined on this level.
# '''Functional Design''' - before you can know ''how'' to do something, you need to know ''what'' to do. But the requirements aren't specific enough. You need to propose a specific behavior, look & feel, and agree on it with the customer.
# '''Technical Design''' - now that we know ''what'' to do, we need to find out ''how'' to do it. We want to do so before actually doing it to avoid frustration and reiteration. That's not always possible, sometimes we need to do prototyping in order to find out. But not to plan is to plan to fail, so a technical design should be done to the best of our ability.
In general, we recommend adding the supply chain part(s) of a story to the title as a prefix. E.g., "Req.: Story A".
[[Category:Best Practices (internal)|Organize UBIK Development]]
[[Category:How-To|Organize UBIK Development]]
[[Category:Resources (internal)|Organize UBIK Development]]
= Staging & Manual Test Plans =
