Another variation on this I've seen is an 'agile' 'team' composed of several groups of engineers each reporting to different managers in the organization with a

Another variation on this I've seen is an 'agile' 'team' composed of several groups of engineers each reporting to different managers in the organization with a scrum master and product owner who reported to yet different chains of command. All of these chains of command had different and conflicting priorities as well as political wars with each other. The product "owner" knew very little about the ill-defined product they owned yet they set the team's 'official' priorities based on wish lists from the business while the engineers also got different priorities from their chain of command and the scrum master was a glorified admin assistant. The result was that no strategy existed and nothing of value was done but the engineers were still ground to a paste against the mill stones of the Jira board every two weeks. It made me miss the simpler times of having a well defined waterfall project being done by a single team of engineers with a single engineering manager and a project manager to make the gantt chart and schedule the meetings.