3 ms·
I've worked in a number of large orgs that have used SAFe and it always seems that you end up spending more time on the bureaucracy than actually writing any co
by _fat_santa 4y ago
I've worked in a number of large orgs that have used SAFe and it always seems that you end up spending more time on the bureaucracy than actually writing any code.
My team just finished a "Release Train" where we supposably adding in a massive feature from a legacy app that required a full team of developers. The team could have probably been half the size and we could have most likely finished it in half the time, what slowed down our velocity so much was all the bureaucracy that SAFe created around doing the most simple piece of work.
The company says that need SAFe to properly track the work that is happening, but they place such a massive reporting burden on the people doing the actual work that things crawl at a snails pace. I once had to push a bug fix for which I had to create a JIRA story. I spent 20 minutes creating the story and attaching all the correct labels, 5 minutes implementing the fix and opening a PR, and then another 15 minutes fighting the time tracker to log the 5 minutes that I worked on the story.
- drran 4y agoSo you spent 40 minutes on a bug instead of whole week? Why?! Just use concise and vague descriptions of your work, like "day 1: trying to reproduce the bug", "day 2: investigating root cause of the bug", "day 3: fixing the bug", "day 4: testing the fix", "day 5: performing release of the fix", and so on. They are very short and fast to type, so you will have lot of free time to do an actual work.