This post is about what is perfect for Sprint Start/End Tenure/Days of the week.
When I first started managing agile projects, my teams routinely started their iterations on a Monday and ended them on a Friday. We’d do this whether the specific team was using two-, three-, or four-week iterations.
Mondays seemed like a natural day to begin an iteration and Fridays were an obvious day to end on.
Well this sometime or most of the time does not work, as any last minute issues resulting team to work on weekends and again get ready on Monday filled with meetings for next iteration .. Ufff.. Leaving no space to drinks or bowling..
I suggested to change their mind about this and began coaching team for more happy path.
To accommodate this, we decided to run two-week iterations that would start on a Friday and end on a Thursday. This worked wonderfully.
The iteration would start in earnest the following Monday. This was great because there was no dread of a Monday filled with meetings, as there was when Monday was review and planning day.
The team also benefitted by occasionally using Friday morning to wrap up any last minute work they’d been unable to finish on Thursday.They didn’t make a habit of this and it only happened a few times; however, spending a few hours on a Friday morning wrapping things up was preferable to coming in over the weekend (as they would have done with a Monday iteration start).
This approach made team having Thu-Evening/Fri-Morning most logical time to deploy/release. If something went wrong, they could fix it Thu-Evening/Fri-Morning rather weekend and keeping a good work-life balance.
Source- Mike-Cohn (Iteration Planning)
Keep Blogging..
Arun Manglick
When I first started managing agile projects, my teams routinely started their iterations on a Monday and ended them on a Friday. We’d do this whether the specific team was using two-, three-, or four-week iterations.
Mondays seemed like a natural day to begin an iteration and Fridays were an obvious day to end on.
Well this sometime or most of the time does not work, as any last minute issues resulting team to work on weekends and again get ready on Monday filled with meetings for next iteration .. Ufff.. Leaving no space to drinks or bowling..
I suggested to change their mind about this and began coaching team for more happy path.
To accommodate this, we decided to run two-week iterations that would start on a Friday and end on a Thursday. This worked wonderfully.
- Fridays (Between Sprint Day) were divided in half
- First half - Spent doing last minute left-over, an iteration review, retrospectives and in planning the next iteration. This usually took until mid-afternoon most.
- Second half - Here team would either get started on the work of the new iteration or they would occasionally head out for drinks or bowling.
The iteration would start in earnest the following Monday. This was great because there was no dread of a Monday filled with meetings, as there was when Monday was review and planning day.
The team also benefitted by occasionally using Friday morning to wrap up any last minute work they’d been unable to finish on Thursday.They didn’t make a habit of this and it only happened a few times; however, spending a few hours on a Friday morning wrapping things up was preferable to coming in over the weekend (as they would have done with a Monday iteration start).
This approach made team having Thu-Evening/Fri-Morning most logical time to deploy/release. If something went wrong, they could fix it Thu-Evening/Fri-Morning rather weekend and keeping a good work-life balance.
Source- Mike-Cohn (Iteration Planning)
Keep Blogging..
Arun Manglick
No comments:
Post a Comment