Food for Agile Thought #299: Learning from Spotify, The Lizard Brain & Agile, Building Products at Slack, Product Thinking

TL; DR: Learning from Spotify, The Lizard Brain & Agile—Food for Agile Thought #299

Welcome to the 299th edition of the Food for Agile Thought newsletter, shared with 32,056 peers. This week, we continue learning from Spotify: Kevin Goldsmith shares lessons learned during the hay days of the “Spotify Model.” Moreover, we delve into the psychology of our inner lizard, constantly on the alert and hiding below a thin crust of civilization and how it relates to team building. Finally, we also witness a desperate attempt by McKinsey to save the PMO by relabeling it ATO. (The sad thing is that C-level folks from BigCorp will go for it.)

We then reflect on autonomy, empowerment, agency, and what that means for work at the team level, and we try to define what “product sense” is about in design, product management, engineering, or venture capital. Also, Ken Norton shares another interview from his outstanding series on successful product practices, and there is an infographic on the differences between projects and products developed by agile teams.

Lastly, we share Patricia Thompson’s journey of teaching Agile in schools, the “triumphs and enlightenment and how we adapted along the way.”

Food for Agile Thought #299: Learning from Spotify, The Lizard Brain & Agile, Building Products at Slack, Product Thinking — Age-of-Product.com
Continue reading Food for Agile Thought #299: Learning from Spotify, The Lizard Brain & Agile, Building Products at Slack, Product Thinking

Food for Agile Thought #298: Scaling Agility, Hard Product Discussions w/ CEOs, Product Team Health Signals, Enterprise Agility

TL; DR: Scaling Agility, Product Team Health—Food for Agile Thought #298

Welcome to the 298th edition of the Food for Agile Thought newsletter, shared with 31,941 peers. This week, we advise how to create a system of interdependent agile teams also know as scaling agility. In addition, we advocate for a budgeting approach that will not impede your organization’s agile transformation, and we enjoy a moment of serendipity: Don’t use a big-name consultancy to support agile transformations and beware of their playbooks.

We then provide actionable advice on dealing with a CEO’s worldview that is impeding your product team; we delve into validation, de-risking, and when to use what, and we reflect on the short shelf life many solutions in today’s volatile environment have and how you may counter that effect.

Lastly, we appreciate a set of signals that hint at your product team’s progress in becoming more effective.

Food for Agile Thought #298: Scaling Agility, Hard Product Discussions w/ CEOs, Product Team Health Signals, Enterprise Agility — Age-of-Product.com
Continue reading Food for Agile Thought #298: Scaling Agility, Hard Product Discussions w/ CEOs, Product Team Health Signals, Enterprise Agility

The Lack of Agile Leadership Qualities — Making Your Scrum Work #15

TL; DR: The Lack of Agile Leadership Qualities — When Change Agents Don’t Act as Role Models

There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. When Scrum becomes an element of an agile transformation, a lack of agile leadership qualities on the incumbents’ side may impede its overall progress significantly despite the best efforts of all other change agents.

📺 Join me and explore the consequences of a lack of agile leadership qualities and what you can do about it in less than three minutes.

The Lack of Agile Leadership Qualities — Making Your Scrum Work #15 — Age-of-Product.com

Update: Join the LinkedIn Poll: What leadership behavior have you noticed in the past that is impeding an agile transformation?

Continue reading The Lack of Agile Leadership Qualities — Making Your Scrum Work #15

Scrum Master Skills: Visualizing the Cost of Team Building with the Tuckman Model

Scrum Master Skills: Visualizing the Tuckman Model

“A picture is worth a thousand words.” Probably, we have all heard that piece of wisdom before. In my experience, having some — even rudimentary — sketching or drawing capabilities is an essential Scrum Master skill. Visualizing a tricky issue while explaining the background to a stakeholder, someone from the management or a teammate helps to pave the way to have a meaningful discussion.

Let me introduce you to an example sketch based on the Tuckman model of group dynamics I use in my Professional Scrum Master training classes to make the effort and cost of creating a Scrum team easier understandable.

Scrum Master Skills: Visualizing the Cost of Team Building with the Tuckman Model — Age-of-Product.com
Continue reading Scrum Master Skills: Visualizing the Cost of Team Building with the Tuckman Model