Project Manager or Scrum Master? Is there a future for both roles?
For the past 15 years, the Scrum Master and Project Manager roles have coexisted well, especially in IT projects. From the very technical role that was part of the Software Development Team, the Scrum Master evolved into a new organizational role sometimes with a well-defined job description and with responsibilities that transcended the technical background from which it originated. Although the role was defined in the Scrum framework, the Scrum Master role is now present in other frameworks; there are many training courses and certifications available from organizations other than scrum.org and scrum alliance with different views on the skills and responsibilities required of the Scrum Master. This provides additional evidence that the role is evolving beyond what the Scrum Guide authors intended.
The Project Manager role has also changed since the Agile Manifesto publication and the adoption of Agile delivery frameworks. This evolution is mainly due to a dynamic business environment, more geographically distributed workforce, and, last but not least, the digital revolution: cloud, social media, and mobile technology impact how projects are managed and delivered. Some organizations are planning to convert Project Managers to Scrum Masters; in others, the Scrum Masters are encouraged to become Project Managers.
This presentation is an assessment of the responsibilities, skills, and knowledge needed for each role and a view of the future of the two roles based on the presenter's experience as a Development Team Lead, Development Manager, Scrum Master, and Project Manager working with Scrum Teams.
NOTE: You must watch videos in their entirety and all the way through to the end for our system to record your viewing activity accurately. Learn more about PDUs on ProjectManagement.com.