Recently I stumbled a few times across job ads asking for "ScrumMaster Project Manager", or something along these lines.
I have to admit, this combination sounds inherently controversial to me.
In my view, there is quite a clear conflict of interests between the two.
The PM is expected to put the project's interests first and foremost, and push to the quickest possible delivery of as many product features as can be delivered. PMs also would often operate under some deadlines / milestones dictated by the business, and as a result will have to push towards getting a certain feature set completed by a specific date.
The SM, on the other hand, should put the team's interests to the top of his/her priorities, while actively shielding the team members from any external pressure, and allowing them to operate in "clean environment", so that they can fully utilize their ability to professionally deliver products, without compromising on the quality and the definition of done just to meet some deadlines (that ideally should not even be in a Scrum team's lexicon).
Among the rest, this means that the team of professional Agile craftsmen should be able to push back on any such pressure, and SM should be their bullhorn for that.
So, are these 2 extremes really expected to be balanced by a single person? Can they? Should they?
I have to admit, this combination sounds inherently controversial to me.
In my view, there is quite a clear conflict of interests between the two.
The PM is expected to put the project's interests first and foremost, and push to the quickest possible delivery of as many product features as can be delivered. PMs also would often operate under some deadlines / milestones dictated by the business, and as a result will have to push towards getting a certain feature set completed by a specific date.
The SM, on the other hand, should put the team's interests to the top of his/her priorities, while actively shielding the team members from any external pressure, and allowing them to operate in "clean environment", so that they can fully utilize their ability to professionally deliver products, without compromising on the quality and the definition of done just to meet some deadlines (that ideally should not even be in a Scrum team's lexicon).
Among the rest, this means that the team of professional Agile craftsmen should be able to push back on any such pressure, and SM should be their bullhorn for that.
So, are these 2 extremes really expected to be balanced by a single person? Can they? Should they?
No comments:
Post a Comment