<!-- DO NOT REMOVE THIS -->{{Template:HowTo/Begin}}<!-- DO NOT REMOVE THIS -->
= Functional Spec & Effort Estimation =
Before working on the implementation of a {{UBIK}} project, it is essential to have a very good understanding of the effort involved. {{UBIK}} projects can be highly complex and much depends on the customer's requirements and a common agreement on a proposed solution.
For the sake of a successful project, a very clear functional specification is paramount. Without it, it is impossible to estimate the effort, and thus the costs, of a {{UBIK}} project adequately.
Also, the effort should not be underestimated; unknown factors are guaranteed to distort even the best theoretical plan into a more complex reality.
Without an adequate time frame and budget, the climate in the project will become one of stress and conflict with the customer.
We recommend PERT as a method for effort estimation.
Effort can be estimated both on task-level and on more abstract levels: For every task, three estimates are provided by the team (optimistic, most likely, and pessimistic), and for every milestone, we can calculate respective sums from the individual tasks. Then, we can use PERT for the final estimate.
= Project Structure Plan =
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 = Functional Spec & Effort Estimation = Before working on the implementation of a {{UBIK Development]]}} project, it is essential to have a very good understanding of the effort involved. {{UBIK}} projects can be highly complex and much depends on the customer's requirements and a common agreement on a proposed solution.[[Category:How-To|Organize For the sake of a successful project, a very clear functional specification is paramount. Without it, it is impossible to estimate the effort, and thus the costs, of a {{UBIK Development]]}} project adequately.[[CategoryAlso, the effort should not be underestimated; unknown factors are guaranteed to distort even the best theoretical plan into a more complex reality.Without an adequate time frame and budget, the climate in the project will become one of stress and conflict with the customer.We recommend PERT as a method for effort estimation. Effort can be estimated both on task-level and on more abstract levels:Resources For every task, three estimates are provided by the team (internaloptimistic, most likely, and pessimistic)|Organize UBIK Development]], and for every milestone, we can calculate respective sums from the individual tasks. Then, we can use PERT for the final estimate.
= Requirement Supply Chain =
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 =
