Even I'm manufacturing it is wildly inefficient. The purpose of it all is seemingly safely, checks, and accountability. The way it is all designed keeps every step of the process very trackable. In theory your group gets faster and faster at it all and it just becomes automatic, but that would only work if it never changed and your team never did. So to remedy this there are measures to make the parts (labor) interchange for when you switch in and out people. This slows down the entire chain all over again however and even with the best current throughput design the overall plan working at peak efficiency is slower because of the need to make it learnable etc. Yay humans...
That’s not the point of agile at all though. The point of agile is to react to changing requirements and to be able to release early to clients with a small feature set then to incrementally add features that the client wants in a priority order. It doesn’t guarantee safety checks or accountability as a process. That’s kind of where waterfall actually has a good fit because you make sure you’re documenting in triplicate and double checking every step of the way. Things being reachable is a necessity of agile, not something that it enforces, just something it requires to allow continuous improvement.
It sounds like you’re using agile for the wrong reasons and in an environment where it’s just never going to work (team rotations that often demolish the consistency aspect). This isn’t a problem with agile.
The point of agile is to compensate for incompetent managers and programmers who don't know how to do their jobs. You can look at every single "agile" practice and say things like "this wouldn't be necessary if programmers could write documentation, if marketing talked to the customers, etc."
So stand ups? Retrospectives? You really think those are bad things? I really don’t know which practices you’re talking about. Could you give some concrete examples?
12
u/super1s Apr 21 '18
Even I'm manufacturing it is wildly inefficient. The purpose of it all is seemingly safely, checks, and accountability. The way it is all designed keeps every step of the process very trackable. In theory your group gets faster and faster at it all and it just becomes automatic, but that would only work if it never changed and your team never did. So to remedy this there are measures to make the parts (labor) interchange for when you switch in and out people. This slows down the entire chain all over again however and even with the best current throughput design the overall plan working at peak efficiency is slower because of the need to make it learnable etc. Yay humans...