Week 3 Flashcards
What is Experiential learning theory?
Learn by doing
Who is on the Scrum Team?
Product Owner - they see to what gets done and when.
Scrum Master - removes obstacles, ensures proper processes are followed.
Team - between 3 and 9 people (inc PO and SM). Developers and Testers (maybe sometimes UX analyst).
What is the Scrum Master?
- NOT the team leader - the team is self-organising
- Works with the PO to define the product backlog (stories) and translate the PO language into words the team will understand.
- Works with the team members: facilitates the events, coaching and teaching, removing impediments.
- Works with the rest of the organisation - liaise with other Scrum Masters.
What are iterations called in Scrum?
Sprints
How long are Sprints in Scrum?
Between 1-4 weeks (typically 2 weeks).
What happens if a story can’t be finished within a sprint?
It is returned to the product backlog.
How many sprints should a story take to be finished?
A story should be finished within one sprint
How do you reduce the risks during a sprint?
There are risks that need to be coped with in the Sprints. At the end of the sprint, you run all the tests for each story to demonstrate the story works.
Can sprints be cancelled?
Yes, but you will still need to have the retrospective at the end of the sprint to find out what went wrong
What is a Sprint Review?
The Product Owner is here and checks to see what’s been done.
Team discusses what went well and what didn’t.
What’s left to do/likely completion date (if that’s going to change).
Happens at the end of the Sprint.
What is the iteration velocity?
The iteration velocity is the expected number of story points (ideal days) that can be completed in each iteration. It’s the total amount of effort that the developers can put in.
An initial estimate of the velocity must be made for the first iteration but can be modified for later ones in light of experience.
How do we calculate the estimated project length in iterations?
total number of story points on all the user stories divided by the velocity.
What are the steps to plan an iteration?
- An iteration will consist of a small number of stories.
1) The team discusses the stories in priority order (recall: MoSCoW value on story card)
2) each story is split into individual tasks - detailed design happens here.
3) The developers pick the tasks they want to work on.
4) estimate the time needed for each of their tasks (usually in ideal hours)
5) Make sure dev are not overcommitted!
What’s an example of the relationship between stories and tasks?
A story may involve 3 classes, each developer owns a class. It can be split into 3 tasks.
How do we measure actual velocity?
- By measuring completed stories.
- The actual time it takes to complete stories, measured in the same metric as predicted velocity.
e.g. if we have 4 stories with ideal time 4 days each. and we only complete 3 of these stories, we add up the predicted effort. So that actual velocity would be 12. Even though we may have spent 20 ideal days doing the work.
We do this because we don’t want to reward people for taking too long.
