3 ms·
About a year ago, we went from no-process to "agile?? I guess?" And let me tell you, a badly implemented process is a great way to turn self-driven developers
by fwip 8y ago
About a year ago, we went from no-process to "agile?? I guess?"
And let me tell you, a badly implemented process is a great way to turn self-driven developers into cogs that just do what's in Jira. Getting your tech decisions questioned by non-tech scrum masters during standup, requirements that don't arrive till midsprint, inability to deploy anything that hasn't been specifically inspected by the sole overworked product owner, etc.
It's not intellectual laziness, it's a defense mechanism. You can't be emotionally invested in your work if the process makes things worse for everyone, at least not without a good therapist.
- srtjstjsj 8y ago> questioned by non-tech scrum masters during standup, Standup is for raising issues, not answering questions. Standup rules says to defer discussions to a separate meeting. > requirements that don't arrive till midsprint, Not scrum-specific, and scrum requires either (a) not doing that, or (b) negotiating a trade to remove another requirement. > inability to deploy anything that hasn't been specifically inspected by the sole overworked product owner Not scrum at all. Scrum deploys every month, as clockwork, with whatever is built so far.
- fwip 8y agoYes, these are all examples of process done badly.