TL; DR: Say Agile One More Time, Scrum Master Salary Report 2022 — Food for Agile Thought #309
Welcome to the 309th edition of the Food for Agile Thought newsletter, shared with 33,012 peers. This week, we enjoy agile in memes — ‘Say Agile One More Time;’ we learn about a remarkable transformation of an industrial behemoth, and we share a beginner list of decision-making patterns, from consensus to rock, paper, and scissors.
We then reflect on the unfortunate ‘practice’ of putting carts before horses when product managers talk to the C-level, and we share six tips on how product folks can annoy their engineering teammates with outstanding efficacy. Also, we point at a critical part of the product creation process that bears many risks: Adding product features is fun and addictive. Now, what if no one uses them?
Lastly, we suggest a practice to test the health of your product creation process, and we shed some light on how long it took startups at Altar.io to build minimum viable products across several industries.
TL;DR: Scrum Master Salary Report 2022 — An Anonymous Poll by the Community for the Community
The purpose of this anonymous Scrum Master salary report is to create a clear, data-backed benchmark that allows everyone in the agile community to understand whether their compensation is adequate. (And yes, the report will cover Scrum Masters as well as Agile Coaches, both employed and freelancing.)
The goal is to have a sufficient number of replies – that would be at least 1,000 – by the end of November 2021 to create the report in time for January 2022. Of course, the report will be available for free.
TL; DR: From Hierarchy to Network, Analyzing Team Boards — Food for Agile Thought #308
Welcome to the 308th edition of the Food for Agile Thought newsletter, shared with 32,931 peers. This week, we dissect the consequences of hierarchies of authority and explain why CEOs, nevertheless, tend to stick with a hierarchy over a network. Also, we advocate applying the ideas of Inspect and Adapt to the Agile principles and values themselves. Moreover, we suggest several actions you can take to identify ‘conflict entrepreneurs’ and other troublemakers and mitigate their negative impact.
We then listen to an interview with Jeanne Liedtka on the importance of distinguishing between Doing vs. Experiencing vs. Becoming; we learn about the end-to-end research process that builds outstanding products, and we dive into premature scaling and its consequences.
Lastly, we share examples of team boards, delving into the importance of visualizing ‘what is actually happening on your team.’ Also, we provide a primer on creating visibility into the waste in a system and what you can do to improve the situation.
TL; DR: Continuous Improvement, Innovation Heroes? — Food for Agile Thought #307
Welcome to the 307th edition of the Food for Agile Thought newsletter, shared with 32,883 peers. This week, we explore the heart of continuous improvement; we dissect the leadership anti-pattern of rewarding the continuation of a broken system, and we suggest eight attitudes to describe leadership styles in a VUCA world, ranging from the organizational refactorer to the flow manager.
We then delve into the anti-pattern of product requirements documents (PRD), substituting proper product discovery. Moreover, we show that successful businesses figure out how to align their goals with the customers they serve. Also, we provide insight into how to practice empathy and communicate effectively with the leadership.
Lastly, we enjoy a podcast with Mr. User Story Mapping Jeff Patton, explaining how you can transform ordinary teams into extraordinary ones by fixing the product backlog.
TL; DR: Selling Product’s Success, Method and Framework Prison — Food for Agile Thought #306
Welcome to the 306th edition of the Food for Agile Thought newsletter, shared with 32,841 peers. This week, we delve into selling Product’s success. Also, we apply David Marguest’s ‘thinking time’ and ‘doing time’ concepts to Scrum events, and we learn what we can do to escape the craziness of methods and frameworks.
We then describe how Intercom changed its NPS strategy to provide helpful customer insights across the company; we share Dovetail’s success story of turning a massive set of qualitative data into an actionable roadmap, and we discuss ethical principles to guide your user research.
Lastly, we share a list of tips and tricks to get more out of your working day without putting in more hours, and we point to the importance of understanding the information cascade and its effect on popular estimation techniques.
TL; DR: Coaching Executive Mindsets, Big Project Syndrome — Food for Agile Thought #305
Welcome to the 305th edition of the Food for Agile Thought newsletter, shared with 32,803 peers. This week, we delve into coaching executive mindsets; we are getting into the zone with the Agile Fluency Model, and we reflect on the difference between accountability and responsibility and how to avoid confusing them.
We then come back to a familiar and highly destructive leadership pattern: turning big ideas into similar-sized projects. Moreover, we point at common analytics problems and how product teams can measure success more effectively, and we mention that output metrics are an obsolete and counterproductive way of measuring human impact in a world of knowledge.
Lastly, we delve into practical aspects of reinventing organizations, from resilience to socio-technical systems to the power of visualization.