3 ms·
This is sort of what scrum does isn't it? Release every cycle no matter what was completed. Whatever was not completed goes back into the backlog and potentiall
by skummetmaelk 7y ago
This is sort of what scrum does isn't it? Release every cycle no matter what was completed. Whatever was not completed goes back into the backlog and potentially into the next cycle.
- Quekid5 7y agoIdeally, yes. In practice there are often complications, however. Usually, it's just office politics: Those cases can be quite difficult -- you really need buy-in and TRUST from management (and have to do the right political plays, etc.) to be able to cut through the bullshit and "allow" feature slips. Books have been written about this scenario. Rarely, deadlines are imposed by Real Politics, aka: law... which can make for Interesting Times. This can range from "quite difficult" to "too easy!", so I have no advice here.
- saagarjha 7y ago> Release every cycle no matter what was completed. What happens when your software is in a broken state that's worse than what you had before?
- justinator 7y agoI guess the keyword is, "completed". If something is broken, I doubt it would be in master, or the team has done something terribly strange. Or they should be nicer to QA ;)
- andreareina 7y agoRollback to last known good state. Hopefully that's not as far back as the previous release (been there, done that, all I got was this lousy egg on my face).
- Too 7y agoYou don't have tests?