Does Scrum have too many “meetings”??

Teams and organizations at the early stage of adopting Agile using the Scrum framework usually get frustrated with all the “meetings” mandated by the framework.
This frustration led to resistance to further adopting the Agile way of working, resistance to using Scrum, and most of the time trying to overcome it by removing some of the elements of Scrum since they were considered “redundant”.
But, is that really the case? Does Scrum offer too many “meetings” ??
Have we looked closer – not only from the Scrum perspective but also from the ecosystem perspective?

Key takeaways:
1) We shall discover the nature of common workplaces in terms of meetings. What makes meetings frustrating to some people.
2) We will then share the root causes of those resistances to Scrum adoption
3) Last but not least, understand how the Scrum elements can help to mitigate those resistances.