Never make the same product mistake twice! Gather your team, reflect on your latest project together, and figure out how to make things better next time.
The timing of the retro can be interesting. I’ve tried a few ways:
1. Finish the epic on a Friday and immediate retro
2. Finish the epic on a Friday, release Monday, retro after release
3. Schedule a recurring mid-sprint retro (for previous sprint), on a Wednesday
And more.
I recently tried the Shape Up methodology. With this, we finished our cycle on a Friday and had to make a decision on the retro. I deviated a little bit and held my retro the Monday after (nice weekend to relax) but _before_ releasing the cycle into prod.
I found if you put the retro _after_ the release, things might have gone wrong during release (unrelated to the work done during the cycle), in which case the devs involved in the cycle+release are the wrong state of mind for the retro.
The timing of the retro can be interesting. I’ve tried a few ways:
1. Finish the epic on a Friday and immediate retro
2. Finish the epic on a Friday, release Monday, retro after release
3. Schedule a recurring mid-sprint retro (for previous sprint), on a Wednesday
And more.
I recently tried the Shape Up methodology. With this, we finished our cycle on a Friday and had to make a decision on the retro. I deviated a little bit and held my retro the Monday after (nice weekend to relax) but _before_ releasing the cycle into prod.
I found if you put the retro _after_ the release, things might have gone wrong during release (unrelated to the work done during the cycle), in which case the devs involved in the cycle+release are the wrong state of mind for the retro.
Just my 2c!