Technical Debt & Scrum: Who Is Responsible?

TL;DR: Technical Debt & Scrum

If technical debt is the plague of our industry, why isn’t the Scrum Guide addressing the question of who is responsibly dealing with it? To make things worse, if the Product Owner’s responsibility is to maximize the value customers derive from the Development Team’s work, and the Development Team’s responsibility is to deliver a product Increment (at least) at the end of the sprint adhering to the definition of “Done,” aren’t those two responsibilities possibly causing a conflict of interest?

This post analyzes the situation by going back to first principles, as laid out in the Scrum Guide to answer a simple question: Who is responsible for keeping technical debt at bay in a Scrum Team?

Technical Debt & Scrum: Who Is Responsible?

Continue reading Technical Debt & Scrum: Who Is Responsible?

Team Building Mental Models

TL;DR: Team Building Mental Models

Team building has always been a challenge, not just since the advent of agile frameworks and the resulting emphasis on self-organization, engagement, and achieving a valuable objective. This post covers four team building mental models — or concepts — that have proven useful in understanding the context of creating agile teams: from Taylorism to Tuckman to Lencioni to Dan Pink.

Team Building Mental Models — Age of Product

Continue reading Team Building Mental Models

Webinar #7: Scrum Sprint Anti-Patterns [Video]

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

The seventh Hands-on Agile webinar Scrum Sprint Anti-Patterns analyzed 12 ways a Scrum team can improve its effectiveness by avoiding typical sprint anti-patterns. Learn more about gold-plating, delivering 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 [Video]

Solving Impediments as a Team

TL;DR: Solving Impediments as a Team

The main message of the retrospective was clear: there are too many interruptions by stakeholders and the senior management. The interruptions impeded the flow of work through the team. Consequently, achieving the sprint goal had been at risk several times in the past. Moreover, the team missed the sprint goal twice recently. Solving impediments as a team has become a necessity.

Learn more on how to tackle impediments as a team by running experiments and iterating on the solution.

Solving Impediments as a Scrum Team Interruption Buckets v2 — Age of Product Retrospectives

Continue reading Solving Impediments as a Team

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 a 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

Webinar #6: Product Owner Anti-Patterns [Video]

TL;DR: Webinar Product Owner Anti-Patterns

The sixth Hands-on Agile webinar product owner anti-patterns addresses 12 ways to improve a product owner’s skill set. Learn also when you — as the scrum master or scrum team — should reach out to your product owner and offer support.

Hands-on Agile Webinar Product Owner Anti-Patterns — June 19th, 2018

Continue reading Webinar #6: Product Owner Anti-Patterns [Video]