3 ms·
My company is undergoing an "agile transformation" to use Scrum. Whereas before my team was working prioritising people and communication over process we're now
by Guid_NewGuid 4y ago
My company is undergoing an "agile transformation" to use Scrum. Whereas before my team was working prioritising people and communication over process we're now "committing" to arbitrary deadlines and bogged down by process and useless meetings. Rather than being able to respond to change we have set scope and bringing work in is frowned upon because it might cross the "deadline". We don't even have a fixed release schedule so the fortnightly sprint boundary is pointless.
I can see why you might need to run a low-trust low-skill offshore project this way but actually existing Scrum is worse than even the waterfall my first company did.
- ibejoeb 4y agoSorry to hear again that common refrain. Imagine it's 2002 and you're pitching a great new way to get work done: SCRUM, and its heart, the Sprint. From the docs: "A new Sprint starts immediately after the conclusion of the previous Sprint." Now imagine ever believing that sprinting for eternity is good, or even feasible. It really is a testament to their marketing prowess that this ever took off.