Food for Agile Thought #414: Agile Scaling Effectiveness, Product Waste, Customer Obsession, Good Mistakes

TL; DR: Agile Scaling Effectiveness — Food for Agile Thought #414

Welcome to the 414th edition of the Food for Agile Thought newsletter, shared with 49,319 peers. This week, Christiaan Verwijs and Daniel Russo analyze Agile scaling effectiveness, highlighting minor differences and suggesting alignment with organizational culture, while Thorsten Ball discusses modern software bloat due to user expectations. Adam Mastroianni and Russ Roberts contrast factual and emotional retention when learning, and Tim Harford emphasizes the importance of a safe environment for acknowledging errors for continuous learning and improvement. Also, we ask: ‘Should we change Scrum?’

Then, Maret Kruve suggests segmenting customer feedback for a better understanding of product needs, and John Cutler discusses the invisible yet significant impact of waste in product development through 15 metaphors. Moreover, Jeff Gothelf provides tips for building a customer-centric organization, plus Rob Zuber encourages businesses to experiment with AI, sharing CircleCI’s journey from brainstorming to AI integration.

Lastly, Paulo Caroli discusses the ‘Build the MVP Canvas’ activity for structured product idea validation. Roman Pichler introduces the downloadable checklist for the GO Product Roadmap, and Egor Savochkin talks about the pace of software development, linking it to technical debt. Finally, Stephen Dubner emphasizes viewing tragedies as cumulative missteps to shift the perspective for mitigation.

Food for Agile Thought #414: Agile Scaling Effectiveness, Product Waste, Customer Obsession, Making Good Mistakes — Age-of-Product.com
Continue reading Food for Agile Thought #414: Agile Scaling Effectiveness, Product Waste, Customer Obsession, Good Mistakes

Should We Change Scrum?

TL; DR: Can We Or Should We Change Scrum?

Can we or should we change Scrum, or is it a sacrilege to tweak the ‘immutable’ framework to accommodate our teams’ and organizations’ needs?

Not so fast; don’t just dismiss augmenting Scrum as leaving the path, contributing to the numerous Scrumbut mutations, giving Scrum a bad name. However, in our rapidly evolving business landscape, sticking rigidly to traditional Scrum by the book could be a straightjacket stifling innovation, user focus, and adaptability.

From ensuring cultural compatibility to facing technical debt challenges and emerging technologies, discover ten compelling reasons why augmenting Scrum isn’t just okay—it’s necessary for modern teams.

Read on to discover when and how to adapt Scrum responsibly without diluting its essence.

Should We Change Scrum? Age-of-Product.com
Continue reading Should We Change Scrum?

Food for Agile Thought #413: Firing Agile Coaches? Are All Feature Factories Bad? Why Didn’t They Say No? Dumb Decisions?

TL; DR: Firing Agile Coaches? — Food for Agile Thought #413

Welcome to the 413th edition of the Food for Agile Thought newsletter, shared with 49,263 peers. This week, Anthony Mersino reflects on firing agile coaches due to financial constraints and urges a focus on continuous improvement to prove value. David Rodenas discusses the misguided adoption of “Agile” due to a lack of understanding, and Marty Cagan emphasizes holistic organizational involvement in digital transformations. Joost Minnaar advocates for subtraction over addition in workplace transformation, promoting identifying and eliminating unnecessary tasks for more effective change.

Then, Sam Gimbel addresses the general disdain towards ‘feature factories,’ advocating for a more nuanced approach and customer-centric development. John Cutler delves into the tendency of teams to overcommit, attributing it to a culture of affirmative bias and advocating for realistic engagement in work commitments. Moreover, Kilian Butler narrates Papercup’s experience in machine learning product development, offering practical insights to help others navigate this challenging yet rewarding domain.

Lastly, Jimmy Janlén explores blending Scrum and Kanban for optimized workflows, providing a roadmap for an informed choice or fusion of these agile frameworks. Oscar Ibars discusses the art of saying ‘no’ in Product Management to maintain realistic project scopes. Paweł Huryn delves into Product-Led Growth strategies, emphasizing customer-centric approaches for product growth. Also, David Perell shares 50 insightful ideas focusing on critical thinking, human behavior understanding, and system optimization, introducing principles like Inversion, Doublespeak, and the Theory of Constraints.

Food for Agile Thought #413: Firing Agile Coaches? Are All Feature Factories Bad? Why Didn’t They Say No? Dumb Decisions? — Age-of-Product.com
Continue reading Food for Agile Thought #413: Firing Agile Coaches? Are All Feature Factories Bad? Why Didn’t They Say No? Dumb Decisions?

Minimum Viable Library (3) — Agile Leadership Edition

TL; DR: The Minimum Viable Library for Agile Leaders

A new edition of the Minimum Viable Library on Agile Leadership is available! Explore a series of carefully curated collections of essential books, newsletters, podcasts, and tools to elevate your agile expertise.

Read on and learn how the recommendations for agile leaders cover a wide range of topics, from the importance of self-managing teams and trust-based environments to the crucial roles of accountability and resilience. While “servant leadership” as a term may be fading, its principles of empowerment and collaboration endure. Stories of transformation in traditional settings underscore the value of decentralized leadership and quick communication.

Minimum Viable Library (3) — Agile Leadership Edition — Age-of-Product.com
Continue reading Minimum Viable Library (3) — Agile Leadership Edition

Food for Agile Thought #412: The Dark Age Has Returned, Product Management Axioms, Scrum Guide 202(X), Storytelling as a PM

TL; DR: The Dark Age of Waterfall — Food for Agile Thought #412

Welcome to the 412th edition of the Food for Agile Thought newsletter, shared with 49,218 peers. This week, Henrik Mårtensson criticizes the re-emergence of the Waterfall method in software development; Ken Schwaber discusses refining the 2020 Scrum Guide to better serve as a reflective framework, inviting community feedback. Also, Emily Webber highlights three collaboration anti-patterns that create power imbalances and hinder problem-solving, while Burcu A. Şengün offers ten valuable tips for budding Scrum Masters, emphasizing patience, continuous learning, and effective communication. Moreover, the Lemon introduces “time-mapped Estimation” to simplify Scrum estimations by mapping story points to person-hours. (Yub, you read this correctly.)

Then, Saeed Khan introduces four Product Management Axioms to guide and communicate fundamental principles in product management, and Rich Mironov discusses the organizational transformation from a services-centric to a product-centric model, stressing the distinct business models and the need for a clear stance to improve alignment and efficiency.. Anthony Murphy showcases the value of structured storytelling in product management, a skill transitioned from his military training. He asserts that a well-constructed narrative greatly enhances clarity and influence in professional communication.

Finally, Kimberly Hendrick celebrates user stories as a catalyst for meaningful dialogue rather than mere task descriptors. At the same time, Ari Tikka critiques the unscientific “Team Performance Curve” in “The Wisdom of Teams” by Katzenbach and Smith, advocating for emphasizing organizational conditions over “teamyness” for enhanced team performance. Johanna Rothman proposes reducing Work in Progress (WIP) and increasing team size to improve collaboration and efficiency, evolving them into small-world networks for better results. Lastly, Marc Randolph reflects on Netflix’s trust-centric approach during its DVD-by-mail era, illustrating how trust, balanced with verification, fortified customer relations.

Food for Agile Thought #412: The Dark Age Has Returned, Product Management Axioms, Scrum Guide 202(X), Storytelling as a PM — Age-of-Product.com
Continue reading Food for Agile Thought #412: The Dark Age Has Returned, Product Management Axioms, Scrum Guide 202(X), Storytelling as a PM

Lost in Communication and Collaboration — Scrum Anti-Patterns Taxonomy (2)

TL; DR: Lost in Communication and Collaboration

Lost in Communication and Collaboration addresses two categories from the Scrum anti-patterns taxonomy that are closely aligned: ineffective collaboration at the stakeholder level, often resulting in an unsuited reporting system based on misaligned metrics.

Learn how these Scrum anti-patterns categories manifest themselves and how they affect value creation for customers and the organization’s long-term sustainability.

This is the second of three articles analyzing the 183 anti-patterns from the upcoming Scrum Anti-Patterns Guide book. The third article will address failures and breakdowns in planning, process, collaboration, and alignment within the Scrum framework.

Lost in Communication and Collaboration — Scrum Anti-Patterns Taxonomy (2) — Age-of-Product.com
Continue reading Lost in Communication and Collaboration — Scrum Anti-Patterns Taxonomy (2)