Age of Product

Food for Agile Thought’s issue #179—shared with 20,968 peers—questions agile dogmas, we bust more Scrum myths and learn why innovative cultures are paradoxical.

We also explore how to avoid the building trap or to become a feature factory; we learn how to free ourselves from the shackles of inertia and risk-aversion, and we have our gut feeling confirmed that fixed scope, fixed time projects can go only one way—south.

Lastly, we learn what kings, and queens, and knights, and trolls have to do with agile transitions. (Yub, GoT is coming.)

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

Food for Agile Thought’s issue #178—shared with 20,783 peers—focuses on learnings from agile transitions failures, how we as agile practitioners volunteered to join probably futile efforts, and why coaching mistakes may have contributed to the mess.

We learn how to support the transition to a product-centric organization; we remind us why (active) listening is a crucial instrument in our toolbox, and how to avoid falling into the “building the wrong thing” trap.

Lastly, we reconsider the idea of not having product managers at all; why not let the engineers do this job, too?

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

Food for Agile Thought’s issue #177—shared with 20,568 peers—covers Scrum limits, the brand-new Scrum Master Trends Report 2019—a joined venture of Age-of-Product with Scrum.org—and the fallacy of wanting to scale ‘agile’ throughout an organization.

We also learn from the Puppet founder that we are not alone in our skepticism regarding enterprise sales, what the author of ‘The Innovator’s Dilemma’ has learned about innovation for the last 25 years, and how we can achieve a better understanding for product management among stakeholders.

Lastly, we have a look at what creates an exemplary agile workspace; if only more organizations would join ING in this respect.

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

Food for Agile Thought’s issue #176—shared with 20,343 peers—covers a study on personality traits suited for agile team building; we go through the stages of adopting self-management as an organization, and we listen to the professor who coined the term “psychological safety” to realize why it has become an essential building block for organizational success.

Also, we ask whether the rush to ship a new product as soon as possible to gather feedback has become untenable; we dive into determining product value, and we understand the particularities of product management from a new viewpoint.

Lastly, we learn more about the educational challenges agile coaches face themselves.

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

Food for Agile Thought’s issue #175—shared with 20,249 peers—focuses on agile pipe dreams: from the absence of complexity in software development to the management-free organization to abundant team capacity.

We also identify more product management problem areas, how to create a shared understanding about your product within your organization, and how you can engage your engineers beyond churning out code.

Lastly, we can put the fuzziness of the #NoEstimates concept to rest once and for all—there is a new animation explaining everything in merely six minutes.

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