Age-of-Product.com - Page 3 of 113 - Tools and insights for agile software development, product management, and lean methodologies to help you invent for your customers.

Download the Scrum Master Salary Report for Free

by Stefan Wolpers | 2023-02-10 Downloads

Welcome to the Download Page of the Scrum Master Salary Report

How do you compare? The Scrum Master Salary Report 2023 is based on 1,100-plus replies from practitioners gathered globally during the 4th quarter of 2022. Learn more about your Scrum Master career opportunities for free.

Scrum Master Salary Report 2023 — Age-of-Product.com

The Background of the Scrum Master Salary Report

The Scrum Master Salary Report 2023 is the fourth edition of the industry survey after 2017, 2019, and 2022. This free report is based on the answers of 1,143 participants globally. If you are considering a career decision this year, maybe, whether you should join the industry as a junior Scrum Master or move to a new organization or go independent, you will find the report’s information beneficial.

By the way, the average salary of the participants in the survey is $80,995, with a standard deviation of about $53,700. In the complete report, you will find more detailed information; download your copy below. Moreover, we are considering creating a statistical model to suggest further career steps: The “Scrum Master Salary Toolkit.”

But see for yourself by downloading your copy of the Scrum Master Salary Report 2023:

Cannot see the subscription form?
Please click here.

Please note that downloading this content will also subscribe you to our popular, professionally-curated weekly ‘Food for Agile Thought’ newsletter if you aren’t already subscribed. You may, of course, unsubscribe at any time.

Please note that you will not be able to download the PDF without having JavaScript enabled.

Scrum Master Salary Report — Related Posts

Hiring: 73 Scrum Master Interview Questions To Avoid Agile Imposters

Peer Recruiting: How to Hire a Scrum Master in Agile Times

Scrum Master Salary Report 2022

Scrum Master Trends Report 2019

Scrum Master Salary Report 2017

Download the ’Scrum Anti-Patterns Guide’ for Free

Food for Agile Thought #379: Patton’s Product Vision, Spotify Model Revisited, Design Thinking’s Failure, More Scrum Bashing

by Stefan Wolpers | News

TL; DR: Patton’s Product Vision — Food for Agile Thought #379

Welcome to the 379th edition of the Food for Agile Thought newsletter, shared with 36,703 peers. This week, we follow Jeff Patton when he revisits his beliefs on the product vision. Also, Henrik Kniberg reflects on the ‘Spotify Model,’ if there is such a model, to begin with, how it started, what its principles are, and whether copying it is a good idea, and Reforge engages in more Scrum bashing with little knowledge of how Scrum works in practice when not run by dogmatic lunatics. Moreover, we sketch how to help your stakeholders build trust in your delivery capabilities and point to twelve success principles of employing a Definition of Done to ensure that.

Then, we learn why Rebecca Ackermann fears that, instead of democratizing access to design, Design Thinking accomplished the opposite, and we reject the idea that ‘90% of product managers are incompetent or lazy or quietly quitting’ because stakeholders consider them unresponsive to their product requests. Our weekly dose of AI is provided by Lenny Rachitsky and Marily Nika, who delve into the importance of artificial intelligence concerning the future of product management.

Finally, we enjoy Tanmay Vora’s illustration of ‘six components of creating a culture of change acceptance based,’ from ownership to relevance, and listen to Jocko Willink diving into decision-making and why people closest to problems need a voice in how to solve them. Lastly, Dan Shipper details how he used GPT-3 and the content from a newsletter archive to create a niche chatbot.

Food for Agile Thought #379: Patton’s Product Vision, Spotify Model Revisited, Design Thinking’s Failure, More Scrum Bashing — Age-of-Product.com

Definition of Done: Business Agility Abhors Technical Shoddiness

by Stefan Wolpers | 2023-02-06 Agile and Scrum

TL; DR: The Definition of Done: Business Agility & Technical Excellence

Most of the time, stakeholders are not interested in how we solve their problems as long as we ethically play by the rules. Instead, they are interested in the regular delivery of valuable Increments as these pave the road to business agility. However, there is no business agility without technical excellence, which brings us to today’s topic: the importance of an actionable Definition of Done.

Learn more about twelve success principles of employing such a Definition of Done as a Scrum team to help your organization become agile.

Definition of Done: Business Agility Abhors Technical Shoddiness — Age-of-Product.com

Food for Agile Thought #378: Top 1% Product Managers, Is Scrum Process-Heavy? 2023 State of PM, Could ChatGPT Do My Job?

by Stefan Wolpers | 2023-02-03 News

TL; DR: Top One Percent Product Managers — Food for Agile Thought #378

Welcome to the 378th edition of the Food for Agile Thought newsletter, shared with 36,661 peers. This week, we reflect on the (product management) industry’s obsession with the top one percent, given the ambiguity about what product managers do. Also, we analyze why Lean Startup is an excellent blueprint for Scrum teams seeking to extend their knowledge of the problem and solution space while breaking down Scrum into components and composite elements, asking: Is Scrum process-heavy? Moreover, we enjoy Jason Yip’s approach to becoming a leadership whisperer.

Then, ProductPlan released the latest edition of its ‘data-backed exploration of how product teams support the entire product lifecycle, from idea to launch and beyond,’ and we learn from a 17th-century naval disaster how not to pursue product design. Speaking of which: We are thirty years into ‘Agile,’ and Jeff Gothelf asks why so few companies incentivize learning and experimentation.

Finally, we list seven estimation anti-patterns, from pretending certainty to effort tampering to story point inflation, and reflect on the increasing popularity of tracking velocity across teams, according to data from the Annual State of Agile reports. Moreover, Sally Goble shares proven practices to get your codebase back into shape, and we advocate that forcing change is often fruitless; why not persuade them with science?

Food for Agile Thought #378: Top 1% Product Managers, Is Scrum Process-Heavy? 2023 State of PM, Could ChatGPT Do My Job? Age-of-Product.com

Agile Transformation: ChatGPT or McBoston?

by Stefan Wolpers | 2023-01-30 Agile and ScrumAgile Transition

TL; DR: Agile Transformation with ChatGPT or McBoston?

This article is another excursion into this nascent yet fascinating new technology of generative AI and LLMs and the future of knowledge work. I was interested in learning more about a typical daily challenge many agile practitioners face: How shall we successfully pursue an agile transformation? Shall we outsource the effort to one of the big consultancies — McBoston? Or shall we embark on an agile transformation with ChatGPT providing some guidance?

If technology can pass a Wharton MBA exam, maybe, it deserves some attention. We thought that AI might initially come after simple office jobs. I am no longer sure about that. Maybe, ChatGPT’s successor will start at the top of the food chain.

Agile Transformation: ChatGPT or McBoston? Age-of-Product.com

Food for Agile Thought #377: Spotify Model Critique, Building Products With AI, Gemba Walk Guide, Product or Feature?

by Stefan Wolpers | 2023-01-27 News

TL; DR: Spotify Model Critique — Food for Agile Thought #377

Welcome to the 377th edition of the Food for Agile Thought newsletter, shared with 36,609 peers. This week, we start with a Spotify Model critique: Jason Yip dissected what many consider an agile framework from an insider’s perspective. Also, we point to issues contributing to management’s failure to keep pace with innovation, from branded management practices vying for attention to business school complicity to confusing management with exact science, and we appreciate John Cutler’s sketch of a simple framework to become a better leader.

Then, we apply the 5C model to ‘bring some structure and product thinking to AI solutions.’ Additionally, we share practical advice on a common product management challenge: feature or product? Also, we listen to Jason Knight and Jeff Gothelf philosophizing about the necessary shift from output to outcome orientation and why organizations still struggle to do so, and we explain Spotify’s approach to validation employing the broader DIBB framework: Data, Insight, Belief, and Bet.

Finally, John Shook shares his guidelines for Gemba walks as an outside advisor, from asking why to showing respect. Moreover, RebootHQ released a bundle of free self-guided courses, and Puppet made the 10th edition of the State of DevOps Report available. Lastly, we shed light on quality metrics, defining different ones for different stakeholder groups while warning of the risks of gaming them.