Changes
One such User Story could be "As a maintenance worker, I want an ACM customizing for my work packages, because I want to see them on the mobile device."
Every User Story requires a definition-of-done. Those are the acceptance criteria, which can be used to decide whether the Story was done or not.One of these acceptance criteria should always be the peer review, i.e., going over the results with a colleague to check for completeness and optimization on a constructive basis.
Only after review and acceptance with respect to the definition-of-done / acceptance criteria, should the User Story be considered finished.
In general, we recommend adding the supply chain part(s) of a story to the title as a prefix. E.g., "Req.: Story A".
= Staging & Manual Test Plans =
* [[HowTo:Transfer_Meta_Data_between_Environments]]
[[Category:Best Practices (internal)|Organize UBIK Development]]
[[Category:How-To|Organize UBIK Development]]
[[Category:Resources (internal)|Organize UBIK Development]]
