I have been working in Agile or "Agile" for the past 7 years, across 3 different companies and noticed similar patterns: - complete failure to adapt to unplann

I have been working in Agile or "Agile" for the past 7 years, across 3 different companies and noticed similar patterns: - complete failure to adapt to unplanned interrupt driven work, such as mid-sprint escalations, QA issues etc. Management rarely pull anything out of the sprint when a developer gets pulled to work on unplanned tasks. - countless meta discussions about what constitutes a story point and whether it should be tied to time and just exactly what it means to be "agile". Agile discussions are starting to turn into "no true Scotsman" arguments. - grooming and planning discussions often overlap in scope leading to exact same things being discussed twice - management/senior staff pressures to trivialize tasks complexity leading to pressure to underestimate and little thought is given that not all developers work at the same pace across all technologies. - sprints rarely finish exactly as planned, so a lot of tasks either get carried over to the next sprint or if they are finished early, it leads to even more unplanned meetings to decide what should be pulled into the sprint. I recently noticed among my colleagues who complete tasks early to just "ride them out" until the end of sprint.