==== A User Story for every task group ====
Every Feature consists of one or many User Stories, i.e., groups of tasks A User Story is a task that can be implemented within one or two weeks(it can be split up in sub-tasks if necessary).While this is the perfect scope for a project engineer to implement, it might be too technical to discuss with the customer, and that's okay, because we have the Feature for that.
A User Story should be formulated using the following pattern:
"As a <user>, I want <requirement>, because <reason>."
Only after review and acceptance with respect to the definition-of-done / acceptance criteria, should the User Story be considered finished.
[[Category:Best Practices (internal)|Organize UBIK Development]]
[[Category:How-To|Organize UBIK Development]]
[[Category:Resources (internal)|Organize UBIK Development]]
= Functional Spec & Effort Estimation =