Jump to: navigation, search

Changes


HowTo:Organize UBIK Development

322 bytes added, 16:53, 10 November 2023
/* A Feature for every requirement */
A use-case consists of multiple Features, i.e., functional parts or requirements for that use-case.
In the example of Operator Rounds, one such Feature could be the basic data model, or presentation of {{UBIK}} MRO work packages on the mobile client.
The main idea of a Feature is to create a work package on a level I can still discuss with the customer, because it is not too technical or detailed.
 
[[Category:Best Practices (internal)|Organize UBIK Development]]
[[Category:How-To|Organize UBIK Development]]
[[Category:Resources (internal)|Organize UBIK Development]]
==== A User Story for every task group ====
1,606
edits