The following 56 scrum product owner theses describe the role of the PO from a holistic product creation perspective.
The 56 product owner theses cover the concept of the product owner role, product discovery, how to deal with external and internal stakeholders, product roadmap planning, as well as the product backlog refinement. The theses also address the product owner’s part in scrum ceremonies such as sprint planning, sprint review, and the sprint retrospective.
What ceremony could better embody scrum’s ‘inspect and adapt’ mantra than the sprint retrospective? I assume all agile peers agree that even the simplest retrospective—if only held regularly—is far more useful than having a fancy one once in a while, or in the worst case having none at all. And there is always room for improvement. Learn more about 21 common sprint retrospective anti-patterns.
Are we still on the right track? Answering this question in a collaborative effort of the scrum team as well as internal (and external) stakeholders is the purpose of the sprint review. Given its importance, it is worthwhile to tackle the most common sprint review anti-patterns.
I ran a poll on the question “Would You Recommend SAFe® as a Scaling Framework?” from May 3rd, 2017 to May 17th, 2017 to identify the Net Promoter Score® SAFe®.
In total, 212 participants replied during that period. Based on the Net Promoter Score® concept, 142 of those votes identified detractors, 31 promoters, and 39 passives. The resulting Net Promoter Score® of SAFe® as a scaling framework is – 52.
(Disclosure: I participated in the poll, and I belong to the group of the detractors.)
The purpose of this anonymous poll is to create a clear, data-backed benchmark that allows everyone in the agile community to get an understanding whether her or his compensation is adequate.
The report will cover Scrum Master as well as Agile Coaches, both employed and freelancing.
To generate an acceptable first report, we will need at least 500 answers. A larger sample would allow providing more detailed insights, though.
Update June 8th, 2017
When we started the survey, I thought that we would collect data until May 1st, and have the report available by the end of May. That turned out to be a bit too optimistic given that four people are involved in creating the survey.
Therefore, we like to share in advance some of the findings from the 2017 Scrum Master Salary Report:
Women have astounding chances and salary possibilities in the field. (We could not identify a gender pay gap.)
The United States is the highest paying country for Scrum Masters, while India is the lowest.
Without some form of certification, getting into the career path is almost impossible.
Additional education has no effect on salary.
Some form of previous experience is often a prerequisite.
If you are in for the money, become a freelancer.
We are working hard to make the report available by the end of June—and we kindly ask for your patience… 🙏
The Scrum Master Salary Report will become an application: As we keep getting new replies—we have already more than 650 as of today—we are planning to turn the report into a small application you can query yourself.
Update May 1st, 2017
Things went much better than anticipated:
We gathered 523 replies which will provide the data for a relevant survey.
I expect that the Scrum Master Salary Report 2017 will be available by the end of May.
The next goal is to extend this dataset and build an application on top of it that is available for free, the Scrum Master Salary Calculator.