This is a serious question 😉
I just led a workshop for a medium size company which was considering (and is now planning) to start using Scrum as the organizing principle for their SW Development efforts. And exactly this question arose.
As it was, we had a classically trained project manager in the room, so he provided much insight into what is expected of a project manager:
Explicitly not part of the Project Manager’s job is removing impediments.
How is this work distributed among the players in Scrum?
|Select Team Members||initial||once established|
|Ensure satisfactory implementations||X|
|Define and Impose Standards||X|
|Coordinate Work between Team Members||X|
|Commit to Delivery Dates||shared||shared|
|Communicate with the Customer (for realization)||X|
So a Scrum master actually has very little in common with a classically trained project manager. The most important job of the scrum master is to remove impediments, something which is explicitly not part of the project manager’s job.
The Scrum master is a ‘servant leader’ — his primary job is to ensure that his team can work and that everyone is playing by the rules. He will also be an agent if not the agent of change in his organization: identify what prevents to organization from advancing and eliminating that impediment.
If you are looking for the difference between RUP and Scrum, waterfall and Scrum, or almost anything and Scrum, look first at the roles. Here is where the fundamental differences are to be found.
|cookielawinfo-checkbox-advertisement||1 year||Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .|
|cookielawinfo-checkbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checkbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
|mailchimp_landing_site||1 month||The cookie is set by MailChimp to record which page the user first visited.|
|CONSENT||2 years||YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.|
|_ga||2 years||The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.|
|_gat_gtag_UA_42152348_1||1 minute||Set by Google to distinguish users.|
|_gcl_au||3 months||Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.|
|_gid||1 day||Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.|
|NID||6 months||NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads.|
|test_cookie||15 minutes||The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.|
|VISITOR_INFO1_LIVE||5 months 27 days||A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.|
|YSC||session||YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.|
|yt-remote-connected-devices||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|yt-remote-device-id||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|COMPASS||1 hour||No description|
|cookies.js||session||No description available.|
|S||1 hour||No description available.|
Well, I tend to disagree that “remove impediments” is not a part of Project Manager’s job. I was a PM several years ago and this was my primary goal that times. Some good books on PM like explicitly mention that. Also here is one nice quote: “Rather than just removing obstacles when they appear, a better Project Manager prevents them from appearing” 🙂
I was actually surprised by this assertion too. The response was that the PM ensures that impediments are addressed, not that s/he actually addresses them him/herself.
I’m curious what RUP has to say on this subject…
It’s odd to me that people would expect the Scrum Master to be in contact with the client (since most impediments need to be resolved ultimately by the client, in my experience), I would think the Scrum Master would be in charge of whipping the BA or PM into action to remove impediments.
I’m not surprised by it at all.
For example, at a former employer of mine, the project leader was the eyes, ears and mouth of the project; the techies were its arms and legs. So the PL was expected to talk to the customer (gather & spoon feed information to the techies, communicate news especially bad news, to the customer.
So there is conflict potential between the Scrummaster’s role as a facilitator and the team’s expectation that a “project leader” be the interface to the customer.
This comment has been removed by the author.
Just for fun, I went googling for Project Manager Job Descriptions.
This one and that one were among the top links. Both largely confirmed the definition of the Project Manager.
Apparently handling impediments (“issues”) is more the job of the program manager than the project manager.