Cost Estimation
Salary
This task pays a fixed salary of 12 MVP points, plus up to 30 quality points for exceeding the minimum requirements — for a total of 42 points, with a maximum of 10 points per person.
Background¶
This section guides you to some additional material that may help you understand the task better. It is not mandatory to read it.
Minimum Viable Product (MVP)¶
By the end of this task, every feature has a justified MoSCoW priority.
For each feature issue:
- classify it as Must Have, Should Have, Could Have, or Won't Have (this time);
- add a short justification for the chosen priority;
- discuss the feature with the tutor;
The MoSCoW categories must be used meaningfully. The team should compare features to each other when deciding whether something is more or less important.
Example: Team 'ByteBusters' assess feature priority
The team marks "Add book" as Must Have because the system cannot provide useful catalog functionality without data. "Delete book" is marked Should Have because the first usable version can work without it.
Technical Details¶
For each feature issue there should be a MoSCoW label GitLab labels and a short justification in the issue description. The justification should explain why the feature is in that category, and how it compares to other features.
When assigning MoSCoW priorities, consider how complex the feature is.
- How much effort is required to implement the feature?
- Is the feature required for a first usable version?
- Does the feature depend on another feature?
- Does the feature unlock other features or enable early feedback?
- Is the feature required to reduce an important risk?
- There is some special knowledge or skill required to implement the feature that the team does not have yet?
- You have or should use some external service or library to implement the feature, and it is not clear if it will work as expected?
Your classifications should be balanced. Marking almost everything as Must Have, or assigning priorities without meaningful differences between features, will not be accepted unless there is a convincing reason. When presenting a feature to the tutor, be ready to explain its value and your priority decision.
Quality¶
Quality means the MoSCoW classification is balanced, comparative, and justified, and these are clearly documented.
The team should be able to explain why one feature is more important than another. If two features receive the same MoSCoW category, that is acceptable here as long as the category itself is justified; their exact development order will be decided during development.
If the scope or meaning of a feature changes substantially, review its MoSCoW priority and discuss its price with the tutor again.
Example: Team 'NullPointers' avoid putting everything into Must
Their first draft marks every feature as Must Have. After discussion they identify the features required for the first usable version and move several useful but non-essential features to Should Have and Could Have. They document the reasons before discussing prices with the tutor.