Stefan Wolpers

Food for Agile Thought #460: Copy-Paste Agile, How to Improve Retention, Psychological Safety Myth, Your Guide to the Kano Model

by Stefan Wolpers | 2024-09-13 News

TL; DR: Copy-Paste Agile — Food for Agile Thought #460

Welcome to the 460th edition of the Food for Agile Thought newsletter, shared with 42,798 peers. This week, Maarten Dalmijn argues that the era of one-size-fits-all Agile is over, advocating for agnostic approaches tailored to organizational contexts over mere Copy-Paste Agile, and Gustavo Razzetti challenges rigid psychological safety truisms, urging leaders to promote ownership and courage instead. Willem-Jan Ageling highlights common Scrum practices that frustrate developers, while Joost Minnaar shares insights from over 50 self-managing organizations exemplifying the RenDanHeYi model. Also, Pierre Pureur and Kurt Bittner discuss how embracing technical debt through Minimum Viable Architecture can accelerate learning.

Next, James Gunaca explores the evolving product management job market, emphasizing competition and shifting hiring practices. Aakash Gupta shares retention strategies from his 15-year experience in product, while Stephen Shapiro offers unconventional innovation prompts that foster long-term value and differentiation. Moreover, David Pereira outlines five tactics for B2B product managers to avoid the “feature factory” trap, focusing on balancing customer wants with user needs, iterating quickly, and leveraging qualitative data.

Lastly, Mark Somerfield critiques The Lean Startup, emphasizing the importance of strong relationships over data-driven processes. Johanna Rothman advocates for using Cost of Delay (CoD) to align teams with business goals, while Bandan Jot Singh offers a practical guide to prioritizing features using the Kano model. Productside provides a comprehensive overview of U.S. Product Management salaries in 2024, and David Pinsof presents 30 concepts exploring manipulation, self-deception, and the role of status in human behavior.

Food for Agile Thought #460: Copy-Paste Agile, How to Improve Retention, Psychological Safety Myth, Your Guide to the Kano Model — Age-of-Product.com

The Pre-Mortem: Preventing Product Failure Before It Strikes

by Stefan Wolpers | 2024-09-09 Agile and ScrumAgile Transition

TL; DR: The Pre-Mortem: A Non-negotiable Part of Your Product Development Toolbox

Do you want to build products that avoid costly mistakes, meet customer needs, and drastically enhance your career prospects? Then, the pre-mortem is your secret weapon!

By imagining how a project might fail before it even begins, teams can identify and mitigate hidden risks early, ensuring a more resilient, successful outcome. This article explains why pre-mortems are a brilliant tool for risk mitigation, improving your team’s decision process, and how they can transform your product development process. Learn how to apply this proactive strategy and create bulletproof products.

The Pre-Mortem: Mitigate Risk and Transform Your Product Development to Your Greatest Competitive Advantage — Age-of-Product.com

Food for Agile Thought #459: Challenging Assumptions, High-Performing Product Teams, Product Strategy Discovery, The Reason for Agile’s Decline

by Stefan Wolpers | 2024-09-06 News

TL; DR: Challenging Assumptions — Food for Agile Thought #459

Welcome to the 459th edition of the Food for Agile Thought newsletter, shared with 42,779 peers. This week, John Cutler suggests structuring organizations to become comfortable with challenging assumptions and thrive amid changing conditions, while Simon Powers examines culture’s impact on individuals and Agile’s decline. Bob Galen emphasizes the shift from rigid frameworks to flexible, context-driven agile patterns, Ted Neward highlights common ‘manager antipatterns’ in leadership, and Gustavo Razzetti stresses intellectual humility to prevent doubling down on poor decisions.

Next, Melissa Suzuno highlights how Botify’s transition to product-trio-supported enhanced collaboration and decision-making, while Todd Lankford offers a 5-step guide for teams to prioritize user needs over excessive planning. Stephanie Leue shares her approach to building high-performing teams, and Vlad Loktev, interviewed by Lenny Rachitski, discusses leadership insights from his decade at Airbnb, emphasizing chaos, impact, and balance in product development.

Lastly, Jacob Bennett shares his structured approach to work estimation for better outcomes, and Roman Pichler introduces product strategy discovery to minimize failure risk. Also, Pim de Morree critiques hierarchical team structures, advocating for more collaborative models, and Chris Stone presents the ‘Days Since Last’ metric for driving team accountability. Finally, Paul Graham reflects on the importance of a ‘founder mode’ approach to scaling companies, challenging conventional management wisdom.

Food for Agile Thought #459: Challenging Assumptions, High-Performing Product Teams, Product Strategy Discovery, The Reason for Agile’s Decline — Age-of-Product.com

From Transparency to the Perils of Oversharing

by Stefan Wolpers | 2024-09-02 Agile and ScrumAgile Transition

TL; DR: Why Too Much Transparency Can Have a Detrimental Effect

While transparency is often touted as essential in Agile, too much can have negative consequences. Oversharing can lead to micromanagement, misinterpretation, and loss of trust within the team. Examples include excessive scrutiny during Daily Scrums, misreading progress metrics, and creating a blame culture that erodes psychological safety.

Strategic opacity may sometimes be necessary to protect the team’s autonomy and maintain a healthy dynamic. Be transparent, but not at the expense of the team’s independence and well-being.

From Transparency to the Perils of Oversharing: Why Too Much Transparency Can Have a Detrimental Effect — Age-of-Product.com.

Food for Agile Thought #458: Engineers in Customer Support, Product & Tech Debt, Product Launch Mistakes, Cynics Rarely Succeed

by Stefan Wolpers | 2024-08-30 News

TL; DR: Engineers in Customer Support — Food for Agile Thought #458

Welcome to the 458th edition of the Food for Agile Thought newsletter, shared with 42,762 peers. This week, Ian Vanagas advocates involving engineers in customer support to boost product quality through faster feedback and ownership. Maarten Dalmijn identifies six common pitfalls in using spikes in Agile, and Jamil Zaki warns that workplace cynicism diminishes success, while Joost Minnaar attributes Enterprise’s success to decentralization and a customer-centric approach. Lastly, Andy Cleff emphasizes the importance of leadership virtues—courage, resilience, alliances, gratitude, and vulnerability—in driving continuous improvement and change.

Next, Gregor Ojstersek and Robert Ta provide engineers with strategies to convince Product Managers to prioritize technical debt by aligning it with business goals. Aakash Gupta and Jason Knight shed light on the complexities of B2B product management, stressing the need for PMs to balance revenue-driven features and broader strategic influence, and Aatir Abdul Rauf identifies 15 crucial mistakes to avoid during product launches. Moreover, Yuri Berchenko offers guidance on optimizing subscription product pricing through regular adjustments and customer segmentation.

Lastly, Domenic Edwards presents a detailed list of essential Product Manager tasks, adaptable to any organization’s needs. Dirk Lässig offers strategies for managing “evil dependencies” in software development, focusing on minimization, mitigation, and coordination, and Gustavo Razzetti explains how teams can rapidly build trust by fostering transparency and clarity. Also, Mario Caropreso stresses the need to balance operational excellence with project delivery. Finally, Michael H. Goitein advocates shifting from a “waiter” mindset to a “doctor” approach in product development, emphasizing user-focused continuous discovery.

Food for Agile Thought #458: Engineers in Customer Support, Product & Tech Debt, Product Launch Mistakes, Cynics Rarely Succeed - Age-of-Product.com

You Don’t Get Paid to Practice Scrum

by Stefan Wolpers | 2024-08-26 Agile and ScrumAgile Transition

TL; DR: Why Solving Customer Problems Instead Matters

Scrum is just a tool; your job is to solve real customer problems and deliver value. Stop focusing on perfecting frameworks and start prioritizing outcomes that matter. It’s time to reassess what truly drives your success, particularly given the challenging business environment.

You Don’t Get Paid to Practice Scrum but Solving Customer Problems within the Given Constraints — Age-of-Product.com