Today's agenda was:
- Definition of done
- Agile Estimating (still continued in the next session)
Definition of Done:
Helps us build the thing right versus the acceptance criteria which helps us build the right thing
There can be various artifacts to call a story or sprint or release done.
For example, we call a story done if unit tests passed or acceptance tests passed.
we can all a sprint done if bugs found during sprint are resolved and release notes are updated.
A release is done when integration tests on deployment build pass and release notes are delivered.
Then we did one more fun exercise to define few artifacts to call various levels done in building a travel web site. For example, travel operators need to follow some govt. compliance so that becomes part of the definition of done.
Agile Estimating:
Different people provide different estimates for the same task. That happens mostly because of different assumptions.
A little effort at understanding requirements and estimating, helps a lot. But a lot of effort would help only a little more.
People are naturally good at comparing things. So there are relative sizing methods. We did an exercise to give some points to various breeds of dogs. Mostly these numbers were from fibonacci sequence. We used smartphone apps for "planning poker" for expressing our estimate of dog point. If there are differences of opinions in estimation, person with far estimate would express why does he think so? And then vote is taken again to reach an agreement eventually.
Estimation is very important topic and is gladly continued.
We are also going to have some guest speakers from industry, so more fun is lined up.
0 comments:
Post a Comment