Comments by "Immudzen" (@Immudzen) on "Why Don’t Developers Like Agile Coaches? | A Day In My Life" video.

@nickjcresswell I would agree with this. It seems some of the agile coaches I have run into just want to follow SAFe to the letter and that ends up frustrating people enormously. I love CI/CD, testing, KANBAN, and even the daily standups can be useful. The people we have on our team are all specialists. Usually there is only one person that can do any one item in the backlog so doing some kind of group backlog refinement is not very useful. Prioritizing tasks also tends to not be very useful since you don't do the next higher priority task instead you do the next highest priority task that you are capable of doing. We also have other teams who build things to make the highly technical team more effective. There is no real reason to plan more than a few weeks ahead at most because you don't truly know what is coming up. Instead a KANBAN approach and keeping people updated helps respond quickly. Code quality is really important because technical debt really slows down the process.
8
In our team we have modified the meetings quite a lot. Just giving a status update does not seem very useful because gitlab already captures that. Instead we focus more on if anyone is stuck, what resources they need, that kind of stuff. Since I do science and engineering programming sometimes people have actual hard issues and having a bunch of brains to help can really cut through the issues quickly. We do CI/CD and a KANBAN style of working. I sometimes wonder if the way we have modified agile just would not work for more normal software teams.
1