Week 6: Cost Estimation
Goal
On this week teams will work on they own planed features, user stories, or use-cases for their project. They will estimate their required effort and gained value. This will help them to prioritize their work for the next milestones.
Expected Results until this Week
We will discuss expected results during the class on this week. So please make sure to be prepared! More about penalty and bonus points- Each team has at least 6 no more than 8 features, user stories, or use-cases defined for their project as individual GitLab issues.
| Title | Duration |
|---|---|
| Moscow | 10 minutes |
| Story Points | 30 minutes |
| Value Points | 30 minutes |
| Prioritization | 30 minutes |
Notes for tutors: 🗒️
1: Moscow (10 minutes)
Why is this useful for me?
Things you learn and experience in this session will help you to solve the following tasks:
Background
Prerequisites
- Features or user stories are listed and described as GitLab issues or in a project management tool.
Activities
- Each team will categorize the features or user stories into the following categories:
- Must Have: Essential features that are critical for the project's success. Without these, the project would be considered a failure.
- Should Have: Important features that add significant value but are not critical. The project can still succeed without them, but their absence may impact user satisfaction.
- Could Have: Desirable features that enhance the user experience but are not essential. These can be included if time and resources permit.
- Won't Have (this time): Features that are agreed to be excluded from the current project scope. These may be revisited in future iterations.
2: Story Points (30 minutes)
Why is this useful for me?
Things you learn and experience in this session will help you to solve the following tasks:
Background
Activities
- Each team will estimate the effort required for each feature or user story using story points. Use a Fibonacci-like sequence (e.g., 1, 2, 3, 5, 8, 13, 21) to represent the relative effort. Mark story points with labels in GitLab issues. You could use the group level labels the tutor has created for you.
3: Value Points (30 minutes)
Why is this useful for me?
Things you learn and experience in this session will help you to solve the following tasks:
Feature Pledging
Pledging is open
Feature pledging is open on this week's class, from the moment the tutor enters the room until the tutor leaves the room after the class.
Background
Activities
- The teams will present features or user stories in a round-robin format (Team#1's Use-Case#1, Team#2's Use-Case#1, ..., Team#1's Use-Case#2, ...). Each team will have a limited time (e.g., 2 minutes) to present one feature or user story they believe is of high value to the project.
- After each presentation, other teams can ask questions or seek clarifications for a brief period (e.g., 1 minute).
- After each presentation the tutor will decide the value points for the presented feature or user story, taking into account other teams' opinions.
- The process continues until all teams have presented their features or user stories or until the allocated time.
- Tutor should document the value points assigned to each feature or user story in the project management tool (e.g., GitLab issues) using labels.
4: Prioritization (30 minutes)
Why is this useful for me?
Things you learn and experience in this session will help you to solve the following tasks:
Background
Activities
- Each team will compute Bang for the Buck score and prioritize their user stories accordingly.