Thanks for posting this, shadowspar. Can I just also point out that this is based on discussions we were having on IRC yesterday, and I asked shadowspar if he could summarise the discussion and post about it. So that's where this is coming from.
Notes on the post itself:
- integration: of course we should be doing continuous integration, so the end-of-cycle bit is more about merging any branches that haven't been and double-checking everything.
- coaches: I'd like to have paired coaches on each iteration, and I've asked shadowspar to pair with me for at least the first iteration.
- iteration 0: I suspect that that first iteration will have one user story, something like, "When I visit growstuff.org I see our website." Figuring out *how* to do that (deployment process, etc) will take most of our effort. That -- and trying out the process for the first time -- is why it's iteration 0.
- estimation: in the github issue tracker, I've set up labels marked "effort: small", "effort: medium" and "effort: large". We'll label stories according to these, based on our estimate of how much work they'll take to complete. At the end of an iteration, when we go to look at how much we finished, we'll assign small = 1, medium = 2, large = 5 and count up the resulting sum. That will give us our "velocity" -- perhaps, say, 15 points -- which we can use as a rough guide to how much is reasonable to take on for the next iteration.
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
ninetydegrees
no subject
on 2012-08-02 12:03 pm (UTC)Notes on the post itself:
- integration: of course we should be doing continuous integration, so the end-of-cycle bit is more about merging any branches that haven't been and double-checking everything.
- coaches: I'd like to have paired coaches on each iteration, and I've asked
- iteration 0: I suspect that that first iteration will have one user story, something like, "When I visit growstuff.org I see our website." Figuring out *how* to do that (deployment process, etc) will take most of our effort. That -- and trying out the process for the first time -- is why it's iteration 0.
- estimation: in the github issue tracker, I've set up labels marked "effort: small", "effort: medium" and "effort: large". We'll label stories according to these, based on our estimate of how much work they'll take to complete. At the end of an iteration, when we go to look at how much we finished, we'll assign small = 1, medium = 2, large = 5 and count up the resulting sum. That will give us our "velocity" -- perhaps, say, 15 points -- which we can use as a rough guide to how much is reasonable to take on for the next iteration.