4 ms·
This is how we ended up with the "Shadow Sprint" at a previous workplace. A whole bunch of utterly essential engineering work was left out of the sprint process
by s_kilk 10y ago
This is how we ended up with the "Shadow Sprint" at a previous workplace. A whole bunch of utterly essential engineering work was left out of the sprint process, so many of us would just go ahead and do what needed to be done anyway while working on whatever tickets we'd picked up frome the "real" sprint.
Utterly dysfunctional of course, but if it's do-or-die, I'd prefer to 'do'.
- bmj 10y agoHow did you handle regression testing of the refactored functionality? That's our biggest hurdle. QC is swamped with "regular" sprint work, so there's no way they manage any additional load during the sprint.
- s_kilk 10y agoWe had pretty good (but not amazing) unit and integration tests in many of those systems, and a willingness to manually test the systems where we didn't have tests. If we had to lean on a QA department to get this stuff done, I'm not convinced we would have been able to actually deliver that project.
- ktRolster 10y agoOnly refactor things in sections of code that you're changing anyway. That way QA already needs to test those sections of code, and gets no extra work.