3 ms·
I dont see why those ideas couldnt be identified and sprinkled into regular sprints. The idea of a forced break to do these things implies they arent important
by nonethewiser 4y ago
I dont see why those ideas couldnt be identified and sprinkled into regular sprints.
The idea of a forced break to do these things implies they arent important. Otherwise they should already get picked up.
- VyseofArcadia 4y agoI've been in orgs in which developers are considered grunts and no one listens to their feedback. It's not that they aren't important, it's that the PMs/managers/whatever know better. I see firebreak sprints as a symptom of an org not valuing engineer feedback. "Let the grunts blow off some steam or they'll get disgruntled and leave."
- micromacrofoot 4y agobecause sprints don’t allow the idle time that’s often needed to come up with such ideas. I could probably work for a year on “oh I’ve been meaning to look into that” tasks that have no clear outcome