Food for Agile Thought #216: Product-Market Fit, Agile Contracts, Accelerating User Research, Daily Scrum Anti-Patterns

Food for Agile Thought’s issue #216—shared with 24,073 peers—delves into the product-market fit concept with statistics, frameworks, and models; we discover the essential elements of high performing teams, and we kiss fixed-everything contracts good-bye.

We also learn from Spotify how to speed up user research by not focusing on running more user interviews, and we look behind the scenes of WeChat and its — by Western standards — unconventional approach to innovation.

Lastly, we enjoy the unpacking of “iteration” and question the language of our community.

Did you miss last week’s Food for Agile Thought’s issue #215?

Food for Agile Thought #216: Product-Market Fit, Agile Contracts, Accelerating User Research, Daily Scrum Anti-Patterns
Continue reading Food for Agile Thought #216: Product-Market Fit, Agile Contracts, Accelerating User Research, Daily Scrum Anti-Patterns

Food for Agile Thought #215: Agility Flywheel, Transformation Failures, Fostering Collaboration, Customer-Centricity

Food for Agile Thought’s issue #215—shared with 23,979 peers—delves into the requirements for the business agility flywheel to work; we reason about transformation failures, and we understand that Liberating Structures allow us to avoid groupthink when working on strategy.

We also learn what failure made LEGO getting serious about agility; we follow an interview on the importance of collaboration in product teams to escape the feature factory, and we get a better understanding of what customer-centricity means for product managers.

Lastly, we enjoy a new infographic comprised of tips & tricks for agile teams.

Did you miss last week’s Food for Agile Thought’s issue #214?

Food for Agile Thought #215: Agility Flywheel, Transformation Failures, Fostering Collaboration, Customer-Centricity
Continue reading Food for Agile Thought #215: Agility Flywheel, Transformation Failures, Fostering Collaboration, Customer-Centricity

Food for Agile Thought #214: Scrum & Agility, Time-Based Estimates, Output vs. Outcome vs. Impact, From Developer to PO

Food for Agile Thought’s issue #214—shared with 23,916 peers—delves into Scrum agility; we follow a notion for time-based estimates, and we learn more about similarities and differences between Cynefin and the Stacey matrix.

We also consider the suggestion to skip standups as those are supposedly the worst breed of time-wasting status update meetings; we appreciate an infographic on output, outcome, and impact, and follow AirBnB to Cuba.

Lastly, we applaud an engineer for sharing his take on the role of the Product Owner.

Did you miss last week’s Food for Agile Thought’s issue #213?

Food for Agile Thought #214: Scrum Agility, Time-Based Estimates, Output vs Outcome vs Impact, From Developer to PO
Continue reading Food for Agile Thought #214: Scrum & Agility, Time-Based Estimates, Output vs. Outcome vs. Impact, From Developer to PO

Have We Reached Peak Agile?

TL; DR: Have we reached Peak Agile?

There has never been a shortage of articles claiming that Agile is either dead, failing, disrespectful, or useless, with authors ranging from respected signatories of the Agile Manifesto to click baiters to people who never experienced the real thing in the first thus lacking a standard for comparison. (See the links below.)

The question from my perspective, though, is: Have we finally have reached peak agile?

Have We Reached Peak Agile? Age-of-Product.com

Share your opinion and join the discussion on LinkedIn.

Continue reading Have We Reached Peak Agile?

Food for Agile Thought #213: Liberating Structures Rescue Scrum, Pair Coaching, Stakeholder Buy-in, Magic Prioritization Bullet

Food for Agile Thought’s issue #213—shared with 23,845 peers—delves into how Liberating Structures rescue Scrum; we borrow Swedish ideas on agile leadership beyond the so-called ‘Spotify model,’ and we learn to create an environment that is attractive to introverts.

We also consider pair coaching; we learn how to include stakeholders in product decisions while managing their expectations, and we dare to look at some math, namely Cost of Delay.

Lastly, we shed light on Mr. Amazon’s grand plan for the universe.

Did you miss last week’s Food for Agile Thought’s issue #212?

Food for Agile Thought #213: Liberating Structures Rescue Scrum, Pair Coaching, Stakeholder Buy-in, Magic Prioritization Bullet
Continue reading Food for Agile Thought #213: Liberating Structures Rescue Scrum, Pair Coaching, Stakeholder Buy-in, Magic Prioritization Bullet