4 ms·
Scrum becomes the process that warps everything else about developing software at the organization. It is easily the strongest influence on how devs do their wo
by MattGaiser 2y ago
Scrum becomes the process that warps everything else about developing software at the organization. It is easily the strongest influence on how devs do their work day to day in most jobs I have had. And that influence is building quotas into every day, week, and sprint.
I have seen (and often done myself) all of the following X items to avoid Y consequences in Scrum.
- Not written unit tests to get a ticket merged under the sprint timeline. We eventually turned them off at one org as a hindrance to merging tickets. Seriously, our unit test runner failed and to keep the sprint on track we disabled the tests. And to keep the project on track, they were never repaired. Scrum demands the sprint always provide value and as value is only what is provided to the user, no tests.
- Inflated points totals and conspired with others to inflate points totals so management is convinced pace is improving.
I waited for my preferred and less diligent QA to be free to get a ticket done, so I am not interrogated holding up the burndown chart.
- Put unfinished functionality into the code as an error and merging it so that it would come back as a bug report, allowing the ticket size to be inflated for the same work.
- Skipping obscure edge cases found later if they would take more time, to avoid a lecture about the importance of detailed grooming. One job got to the point of specifying which files and functions needed to be changed for higher precision.
- Finished a task in the morning and then waited until the next day to pick up a new ticket because points is tied to days and you don't want the Scrum master asking why something is delayed in the burndown chart because you really only had half a day from when you assigned it to yourself.
The central failing of Scrum is that it is built on:
> Commitment, Focus, Openness, Respect, and Courage
And 1,3, and 5 in particular are either about different things for different people, or simply are absent because of the reality of a corporate hierarchy (i.e. it is always in your interest to suck up and seem reliable while hiding failures).