Food for Agile Thought #411: Team Diversity Problems, Marginal Users’ Tyranny, Useful Agile Mantras, Shared Understanding?

TL; DR: Team Diversity Problems — Food for Agile Thought #411

Welcome to the 411th edition of the Food for Agile Thought newsletter, shared with 49,134 peers. This week, Christiaan Verwijs and Daniel Russo scrutinize the complex relationship between team diversity and performance, pointing to team diversity problems. Emily Webber identifies three collaboration anti-patterns sabotaging teamwork in organizations, and Jason Little takes us back to the foundational Agile principles that we should remember. Also, Jason Evanish dispels myths around introverted leadership, highlighting its unique strengths and benefits, and we enjoy a great interview with Jim Highsmith.

Then, Ivan Vendrov critiques the sacrifice of user experience for metrics in consumer software, while David Pereira distinguishes between genuine product management and its hollow counterpart, urging us to develop a “bullshit radar.” Leah Tharin cautions Airtable on its enterprise focus, potentially jeopardizing product-led growth for smaller clients. Moreover, Jenny Wanger showcases a food delivery company that has successfully integrated customer-centricity through operational choices.

Finally, Benji Huser-Berta underscores the importance of feature forecasting for effective planning in organizations with long release cycles. Chris Meyer delves into the Dunning-Kruger Effect, spotlighting its impact on self-awareness. Kai Hellström critiques superficial approaches to ‘Shared Understanding,’ advocating a more profound commitment to solving customer problems.

Food for Agile Thought #411: Team Diversity Problems, Marginal Users’ Tyranny, Useful Agile Mantras, Shared Understanding? — Age-of-Product.com
Continue reading Food for Agile Thought #411: Team Diversity Problems, Marginal Users’ Tyranny, Useful Agile Mantras, Shared Understanding?

Food for Agile Thought #410: Best Product Teams, Communication in Low Trust, Killing Features, Stop Using ‘Failure’ When Learning

TL; DR: Best Product Teams — Food for Agile Thought #410

Welcome to the 410th edition of the Food for Agile Thought newsletter, shared with 49,013 peers. This week, Shane Parrish discusses with Shreyas Doshi the nuances of best product teams and product development; Charity Majors touches upon communication dynamics in strained relationships, emphasizing the role of trust; Jason Cohen advocates for redefining the narrative around business setbacks, championing terms like “experiment” over “fail,” and Ryan Holiday dissects the art of leadership, reminding us that leadership roles manifest in diverse ways throughout life. Also, we shed a light on unspoken reasons to resist Agile transformations.

Then, Andrew Quan delves into the self-doubt that plagues many Product Leaders, shedding light on their challenges and offering guidance. Assaph Mehr sets an intriguing take on the potential value of altering favorite product features, elucidating its long-term benefits for the product and business. Meanwhile, Roman Pichler examines the intricate process of assembling product teams in organizations unfamiliar with the digital product’s true essence.

Finally, Jason Yip debunks common productivity myths, urging a deeper understanding of effectiveness. Jeff Gothelf emphasizes the value of consistent customer interactions to gain insights without hefty investments. Stephen Puiszis highlights the intricacies of evaluating product roadmaps, providing tools for those outside product management. Lastly, Łukasz Korecki offers a candid reflection on the challenges of implementing OKRs within software engineering teams.

Food for Agile Thought #410: Best Product Teams, Communication in Low Trust, Killing Features, Stop Using ‘Failure’ When Learning — Age-of-Product.com
Continue reading Food for Agile Thought #410: Best Product Teams, Communication in Low Trust, Killing Features, Stop Using ‘Failure’ When Learning

Food for Agile Thought #409: How to Be Unproductive, Customers Hate the MVP, Waterfall Misconceptions, Supporting Continuous Discovery

TL; DR: How to Be Unproductive — Food for Agile Thought #409

Welcome to the 409th edition of the Food for Agile Thought newsletter, shared with 48,883 peers. This week, we explore several provocative perspectives: John Cutler delves into factors affecting developer productivity, or: how to be unproductive, suggesting the environment plays a more substantial role than individual aptitude. Kris Brandow makes a case for the undervalued potential of the Waterfall method. Stephan Schmidt pinpoints the unintentional merger of Scrum and Waterfall into “Scrumfall” due to external pressures. Lastly, Ben Biran shares insights from Zapier’s Interfaces team, emphasizing how shifting prioritization duties to engineering leaders can catalyze team performance and culture.

Then, Jason Cohen critiques the widely adopted MVP approach for sidelining the user experience and calls for its reevaluation. In conversation with Lenny Rachitsky, Tim Holley of Etsy unfolds his ten-year odyssey with the e-commerce giant, touching on various facets, from handling the pandemic-induced surge to fine-tuning marketplace dynamics. Meanwhile, Arne Kittler brings product maven Teresa Torres into the spotlight, who, in dialogue with Petra Wille, clarifies the essence of product discovery grounded in customer feedback.

Lastly, Mike Cottmeyer tackles the growing disillusionment among leaders with Agile, offering ways to reignite their interest and commitment. Mikkel Krenchel sheds light on the rising societal apprehensions around AI, emphasizing the often-overlooked importance of ethnographers in shaping AI’s ethical trajectory. Lastly, Nick Ianetta puzzles over the marked distinction between Research Operations and Market Research Operations, probing the reasons behind their strategic organizational separation.

Food for Agile Thought #409: How to Be Unproductive, Customers Hate the MVP, Waterfall Misconceptions, Supporting Continuous Discovery — Age-of-Product.com
Continue reading Food for Agile Thought #409: How to Be Unproductive, Customers Hate the MVP, Waterfall Misconceptions, Supporting Continuous Discovery

Join the Scrum Master Salary Report 2024 — Let Us Create Transparency

TL;DR: Scrum Master Salary Report 2024 — 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. The report will cover Scrum Masters and Agile Coaches, both employed and freelancing.

The goal is to have at least 1,000 replies by the end of November 2023 to create the report in time for January 2024. Of course, the report will be available for free.

Join the Scrum Master Salary Report 2024 — Age-of-Product.com
Continue reading Join the Scrum Master Salary Report 2024 — Let Us Create Transparency

Food for Agile Thought #408: Developer Productivity, Double Diamond Improvements, Defining Product Problems, Scrum a Failure by Design?

TL; DR: Developer Productivity — Food for Agile Thought #408

Welcome to the 408th edition of the Food for Agile Thought newsletter, shared with 48,813 peers. This week, Kent Beck and Gergely Orosz dispute McKinsey’s measure of developer productivity, underscoring the essence of tailored metrics. Dave West at Agile 2023 notes a perceived halt in Agile’s evolution, highlighting issues from wavering executive support to misdirected investments. Maarten Dalmijn debates Scrum’s pitfalls, suggesting an organizational focus rather than dictating team dynamics. Meanwhile, Pim de Morree shares the Dutch National Police’s transformative journey from top-down to bottom-up methods, providing valuable takeaways for aspiring changemakers. Also, we ask why SAFe® is so successful, although many agile practitioners despise it.

Then, Jayendran Gopalsami exposes biases, like groupthink and popularity bias, that stealthily skew product trajectories. Scott Sehlhorst pinpoints a frequent product management error: addressing symptoms over root causes. Meanwhile, a riveting discourse between Chad McAllister and Atif Rafiq showcases a tripartite formula for expedited innovation. Rafiq, leveraging insights from industry giants, unveils “Decision Sprint,” bridging the chasm between strategy and tangible results.

Lastly, Ciera Jaspan and Collin Green explore the “technical debt” metaphor’s human-centric origins and its implications on software engineering. Lars Jerichau challenges the trend of collaborative ideation, spotlighting studies that laud the superior results of individual brainstorming over group efforts. Additionally, Andy Budd reshapes the revered “Double Diamond” design process, presenting a version more aligned with actual project executions, emphasizing optimal design leverage.

Food for Agile Thought #408: Developer Productivity, Double Diamond Improvements, Defining Product Problems, Scrum a Failure by Design? — Age-of-Product.com
Continue reading Food for Agile Thought #408: Developer Productivity, Double Diamond Improvements, Defining Product Problems, Scrum a Failure by Design?

Food for Agile Thought #407: The Costs of Agile, Product Decision Spectrum, The Ultimate JTBD Guide, Stakeholder Alignment

TL; DR: The Costs of Agile — Food for Agile Thought #407

Welcome to the 407th edition of the Food for Agile Thought newsletter, shared with 48,702 peers. This week, Matt Rickard offers invaluable leadership lessons from his aerospace design experiences; Henrik Mårtensson explores the overlooked facets of the costs of Agile, and Jeff Langr and Nick Goede remind us that true agility stems from core values, not mere practices. Also, Chris Combe delves into the complexities of performance reviews in Agile settings. Moreover, once again, our lemon tries to measure Developer productivity.

Then, Austin Yang underscores the significance of the decision-making process over mere outcomes in product management, and Marty Cagan provides a roadmap from traditional product management to empowered product teams. Meanwhile, Jeff Gothelf points out the rare yet essential cross-functional collaboration in product discovery, emphasizing the combined effort of product management, design, and engineering.

Lastly, Lenny Rachitsky and Bob Moesta dive deep into the JTBD framework, using captivating examples from Snickers and Milky Way. Also, John Davidson sheds light on the complexities of stakeholder alignment, sharing ten indispensable lessons. Meanwhile, Johanna Rothman navigates the murky waters of project estimations, presenting a variety of techniques and highlighting the unpredictability of timeframes.

Food for Agile Thought #407: Costs of Agile, Product Decision Spectrum, The Ultimate JTBD Guide, Stakeholder Alignment — Age-of-Product.com
Continue reading Food for Agile Thought #407: The Costs of Agile, Product Decision Spectrum, The Ultimate JTBD Guide, Stakeholder Alignment