Keeping IT Simple!

You could see Scrum Masters being promoted as PMs or even Directors in some companies. Isn't it high time, that the community stops misleading/believing that there is no role for a Manager in Agile or Scrum?

The responsibilities of a Scrum-Master matches that of a project manager, by definition of Agile Manifesto and also as per the so-called "rigid"/ "obsolete" standards of PMI.?

The Agile Manifesto claims, the "Scrum Master is responsible for organizing meetings, dealing with challenges and bottlenecks. The Scrum Master interacts with Product Owner to ensure that the product backlog is ready for the next sprint. He or she is also responsible to ensure that the team follows the Scrum process."

Before Agile / Scrum and SAFe were buzz words in Software Engineering, Project Management did account for the Project Manager to be a enabler than a task master.In spirit, this is exactly the expectations/responsibilities of the project managers from the so called "Traditional" waterfall era.

Early authors of Software engineering, duly noted the "Iterative model" as one the methods of developing software. Back then, IT companies had reached the same levels of potential with an seemingly equally talented pool of resources(developers). Hence leaving other obvious factors like quality standards like ISO/CMMI5 and meeting FRs and NFRs, Fixed bid pricing model based on waterfall methodology was the only/apparent way of selecting a vendor.??

So assuming that Agile/Scrum is a recent path breaking revolution in IT Application development / management is wrong. IT industry is guilty of just replacing synonyms in their jargon to sound cool and enterprising. The community needs to understand that certifying organizations and their principles are just guidances. Just like the Constitution, they may need explanations and interpretations with changing times, but the provisions for amendments and executing them to various degrees relies on the need of the organization/community.