Survey: How Do You Solve Impediments Outside Your Team’s Control? (Anonymous.)

TL;DR: How to Solve Impediments (Survey)

No matter if you are a Scrum Master or an agile coach, sooner or later, you will run into a problem that’s outside of the team’s sphere of control. The question is: How do you solve impediments of this kind? What approach has worked best for you in the past?

Barry Overeem, Christiaan Verwijs and I teamed up to provide some transparency in this matter and share your best techniques and approach with the agile community. All it takes to contribute is five minutes of your time to participate in the anonymous ‘how to solve impediments’ survey. (We expect results to be available in November.)

Survey: How to Solve Impediments outside the Team’s Control — Age of Product

Continue reading Survey: How Do You Solve Impediments Outside Your Team’s Control? (Anonymous.)

Food for Agile Thought #159: Agile Industrial Complex, Scrum Team Kick-off, Idea Funnel, Product Discovery

Food for Agile Thought’s issue #159—shared with 19,054 peers—covers the agile industrial complex and its fake-agile distortion field, according to Daniel Mezick, we kick-off new Scrum teams, and we advocate to manage the flow of work, not people.

We also appreciate another success story from the continuous product discovery field, supported by a proven & tested reference idea funnel, and ask: is Design Thinking merely preserving the status quo?

Lastly, we address agile sensemaking—a visualization of working and learning in a state of perpetual beta.

Have a great week!

Food for Agile Thought #159: Agile Industrial Complex, Scrum Team Kick-off, Idea Funnel, Product Discovery

Continue reading Food for Agile Thought #159: Agile Industrial Complex, Scrum Team Kick-off, Idea Funnel, Product Discovery

Webinar #7: Scrum Sprint Anti-Patterns — October 2, 2018

TL;DR: Webinar #7: Scrum Sprint Anti-Patterns

The seventh Hands-on Agile webinar Scrum Sprint Anti-Patterns analyzes 12 ways a Scrum team can improve its effectiveness by avoiding typical sprint anti-patterns. Learn on October 2nd, 2018, at 6 pm CEST more about gold-plating, delivery Y instead of X, absenteeism, side-gigs, and organizing people instead of the flow of work.

Scrum Sprint Anti-Patterns Hands-on-Agile Webinar #7

Continue reading Webinar #7: Scrum Sprint Anti-Patterns — October 2, 2018

Food for Agile Thought #158: Semco Transformation, Trust, 10 Product Commandments, Unfounded Confidence

Food for Agile Thought’s issue #158—shared with 18,935 peers—visits the poster child of self-managed organizations—Semco—, we deal with building trust in teams, and we learn why agile companies no longer require plans.

We appreciate Roman Pichler’s sprint planning tips & tricks for product owners, we dive into the commandments of outstanding products, and we understand how falling in love with a solution can wreck a whole organization.

Lastly, we come back to product discovery and learn a new approach how to reinvent a strategy to figure out what’s worth building.

Have a great week!

Food for Agile Thought #158: Semco Transformation, Trust, 10 Product Commandments, Unfounded Confidence

Continue reading Food for Agile Thought #158: Semco Transformation, Trust, 10 Product Commandments, Unfounded Confidence

The Meta-Retrospective — How To Get Customers and Stakeholders Onboard

TL;DR: The Meta-Retrospective

A meta-retrospective is an excellent exercise to foster collaboration within the extended team, create a shared understanding of the big picture, and immediately create valuable action-items. It comprises of the team members of one or several product teams—or representative from those—and stakeholders. Participants from the stakeholder side are people from the business as well as customers.

Meta-retrospectives are useful both as a regular event, say once a quarter, or after achieving a particular milestone, for example, a specific release of the product. Read more on how to organize such a meta-retrospective.

Meta-Retrospective — Age-of-Product.com
Continue reading The Meta-Retrospective — How To Get Customers and Stakeholders Onboard

Food Agile for Thought #157: Agile 2018, Mediocrity, Peter Principle, Business vs. Technical Debt

Food for Agile Thought’s issue #157—shared with 18,862 peers—applauds Martin Fowler for his Agile Australia keynote on Agile 2018, we learn about the road to mediocrity, and we ask: Is the Peter Principle not a satire but reality?

We also address the issue of hidden (technical) costs of being ‘agile,’ as well the how to solve the conflict between prioritizing business needs as well as maintaining the health of the code base.

Lastly, we deal with the challenges of planning poker in a short and entertaining video.

Have a great week!

Food Agile for Thought #157: Agile 2018, Mediocrity, Peter Principle, Business vs. Technical Debt

Continue reading Food Agile for Thought #157: Agile 2018, Mediocrity, Peter Principle, Business vs. Technical Debt