Metrics and estimation

Question 1

3 common failures

Answer 1

• developers lack technical knowledge
• developers lack domain knowledge
• epic (story too big)

Question 2

who is responsible for prioritisation in scrum

Answer 2

product owner - writes story and does prioritisation
devs can help write technical user stories if needed
devs don’t always have relevant experience in the field, such as communicating with client

Question 3

what scenarios are in scope for acceptance criteria

Answer 3

you can work with a subset of input data
can defer conditional steps to other stories
you can defer data validation
you can defer error handling - should be handled by developers when carryinf out test, not really to do with stories

Question 4

2 kinds of epics

Answer 4

compound epics
complex epics

Question 5

compound epics

Answer 5

comprises of multiple shorter stories

Question 6

complex epics

Answer 6

• cannot be easily disaggregated into smaller stories
• use spikes to find out how to split epics
• important to know if something is impossible earlier on

Question 7

spike

Answer 7

spend some time over a couple iterations working on a particular problem in order to estimate how long it would take to build