Food for Agile Thought #416: Feature Team Fallacy, Measuring Product Discovery, Forget the Spotify “Model,” Working Backwards

TL; DR: Feature Team Fallacy — Food for Agile Thought #416

Welcome to the 416th edition of the Food for Agile Thought newsletter, shared with 49,471 peers. This week, we dive into compelling critiques and analyses: Bryan Finster assesses the LeSS approach to team structures, pointing at the Feature Team Fallacy, while Mark Levison sheds light on misconceptions about the “Spotify Model.” Johanna Rothman highlights the pitfalls of dehumanizing metaphors in software development. Additionally, a collaborative piece delves deep into the implications and nuances of the Agile Mindset in decision-making and its role in organizational behavior. Moreover, we address how to Say No without burning bridges.

Then, Jeff Gothelf discusses the actual indicators of product discovery’s effectiveness, cautioning against vanity metrics. Charles Lambdin parallels Gandalf’s adventures and Agile’s inherent adaptability, questioning traditional roadmaps. Dan Collins underscores the pivotal role of churn prevention in SaaS, emphasizing customer-centric strategies. Lastly, Laura Morgan provides a personal account, highlighting three transformative moments in her professional journey.

Finally, Paulo Caroli introduces a Press Release template inspired by Amazon’s customer-centric approach. Also, Jim Morris tackles the challenges of sharing group dynamics techniques to combat dominant voices and foster inclusivity. Marcus Castenfors laments the absence of robust product visions in companies and champions the Design Sprint process for alignment. Lastly, Tim Harford at #mtpcon London 2023 enlightens on common tech innovation missteps, emphasizing the transformative power of simple solutions and AI’s impending influence on employment.

Food for Agile Thought #416: Feature Team Fallacy, Measuring Product Discovery, Forget the Spotify “Model,” Working Backwards — Age-of-Product.com
Continue reading Food for Agile Thought #416: Feature Team Fallacy, Measuring Product Discovery, Forget the Spotify “Model,” Working Backwards

Saying No as a Product Owner or Product Manager

TL, DR: Saying No Without Burning Bridges

Are you navigating the delicate art of saying No as a Product Owner or product manager? Actually, it’s more of a strategic ‘yes’ to higher priorities, turning down lower-level requests without shutting down communication.

This article will dive into various approaches, from reframing conversations and fostering stakeholder collaboration to being transparent to data-informed rationale and empathetic engagement. Discover how to maintain a harmonious balance between driving Product Goals and nurturing professional relationships with your stakeholders.

Saying No as a Product Owner or Product Manager — Age-of-Product.com
Continue reading Saying No as a Product Owner or Product Manager

Food for Agile Thought #415: Product Nightmares, Assumption Testing Guide, Freemium Fiasco, Agile Inflection Point?

TL; DR: Product Nightmares — Food for Agile Thought #415

Welcome to the 415th edition of the Food for Agile Thought newsletter, shared with 49,394 peers. This week, we delve into various aspects of Agile and Scrum, starting with Dean Peters’ eerie depiction of product nightmares as Halloween monsters, urging an outcome-driven strategy. Mike Griffith contemplates the mainstream adoption of Agile amid declining conference attendance, hinting at a possible inflection point. Jason Evanish warns against toxic positivity’s corrosive effects on workplace morale and productivity. Also, Viktor Cessan shares how a tailored feedback format enriched communication in a re-missioned team. And, seriously, this Week’s Lemon suggests a hybrid approach of Agile and Waterfall.

Then, Teresa Torres highlights the value of regular assumption testing for quick product idea evaluations, and Marty Cagan commends Spotify’s innovation amidst market challenges. Moreover, Itamar Gilad addresses idea prioritization, advocating for a strategic framework with a clear mission and measurable growth model, while Leah Tharin explores the transition to a freemium model, emphasizing aligning sales and marketing incentives, revamping onboarding experiences, and assessing a product’s freemium suitability to prevent revenue loss.

Lastly, Nicola Ballotta delves into Engineering Metrics, showcasing them as instrumental tools in quantifying and enhancing various software development aspects and aligning engineering operations with broader business goals. Additionally, we unveil a novel Stability Metric (ψ) based on queueing theory to bolster predictability in agile systems. The authors suggest the application of ψ as a tool for teams to improve project timeline foresight and enhance predictability. Finally, we point to the recording of Bob Galen’s session on ‘An Agile Coaches Guide to Storytelling” at the 53. Hands-on Agile.

Food for Agile Thought #415: Product Nightmares, Assumption Testing Guide, Freemium Fiasco, An Agile Inflection Point? — Age-of-Product.com
Continue reading Food for Agile Thought #415: Product Nightmares, Assumption Testing Guide, Freemium Fiasco, Agile Inflection Point?

An Agile Coaches Guide to Storytelling — Bob Galen at the 53. Hands-on Agile

TL; DR: Hands-on Agile #53: An Agile Coaches Guide to Storytelling with Bob Galen

On September 5, 2023, we had the opportunity to listen to Bob Galen on “An Agile Coaches Guide to Storytelling.” In this session, Bob shared his experience coaching an agile coach struggling to connect with a development manager. He underscored the transformative impact of incorporating personal narratives, lessons learned, teaching stories, and purpose or vision stories into coaching conversations. Moreover, Bob demonstrated the compelling power of storytelling in agile coaching by using stories to share knowledge and wisdom while fostering dialogue.

An Agile Coaches Guide to Storytelling — Bob Galen at the 53. Hands-on Agile

📺 Watch the video now: An Agile Coaches Guide to Storytelling — Bob Galen at the 53. Hands-on Agile.

Continue reading An Agile Coaches Guide to Storytelling — Bob Galen at the 53. Hands-on Agile

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?