Food for Agile Thought #174: Agile Feedback, Disrespect, Prime Directive, Systems Thinking for PMs

Food for Agile Thought’s issue #174—shared with 20,147 peers—focuses on making sense of feedback with the epic new EPIQ model; we talk about a Scrum value that also applies to managers, and we reflect on the prime directive and the magic it provides.

We also address the importance of product design principles; we add systems thinking to our product management toolbox, and we learn how best exploit the opportunity of a rewrite.

Lastly, we appeal to efficiency freaks to finally realize that slowing down speeds up everything in software development.

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

Food for Agile Thought #174: Agile Feedback, Disrespect, Prime Directive, Systems Thinking for PMs

Continue reading Food for Agile Thought #174: Agile Feedback, Disrespect, Prime Directive, Systems Thinking for PMs

Food for Agile Thought #173: Agile Common Sense, Agile Team Building, Product-Oriented Engineers

Food for Agile Thought’s issue #173—shared with 20,138 peers—focuses on agile common sense as we learn more about the history of ‘agile’ and what defines the learning space that makes it successful.

We also get better at cycle time scatterplot diagrams, what conditions product teams require to support hypergrowth, and why leadership is not always about having a plan.

Lastly, we learn five encouraging ways how to engage the engineers in creating the product beyond its mere coding.

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

Food for Agile Thought #173: Agile Common Sense, Agile Team Building, Product-Oriented Engineers

Continue reading Food for Agile Thought #173: Agile Common Sense, Agile Team Building, Product-Oriented Engineers

Food for Agile Thought #172: Taylorism & Agility, Agile Planning Myths, Product Discovery, Leadership in an Agile World

Food for Agile Thought’s issue #172—shared with 20,138 peers—focuses on Taylorism Agility and its contribution to imposing ‘agile,’ why agility and governance do not have to be mutually exclusive, and busts several agile planning myths.

We also refresh our memory why the engineers need to participate in product discovery, how you prepare for product experiments, and what this whole customer journey mapping is about.

Lastly, we learn what good leadership has to do with intrinsic motivation in the trenches.

This is the last edition of the ‘Food for Agile Thought’ newsletter in 2018. Thank you so much for your feedback and continued support; we will be back on January 6th, 2019, with issue #173.

Enjoy the rest of 2018!

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

Food for Agile Thought #172: Taylorism Agility, Agile Planning Myths, Product Discovery, Leadership in an Agile World

Continue reading Food for Agile Thought #172: Taylorism & Agility, Agile Planning Myths, Product Discovery, Leadership in an Agile World

📅 Agile Camp Berlin 2019: April 26–27, 2019

Save the Date: Agile Camp Berlin 2019

The Agile Camp Berlin 2019 will happen from April 26 to April 27, 2019 and the Agile Camp Berlin 2019 venue will be the Evangelische Schule Berlin Zentrum right in the middle of Berlin.

📅 Agile Camp Berlin 2019: April 26–27, 2019

Continue reading 📅 Agile Camp Berlin 2019: April 26–27, 2019

Food for Agile Thought #171: Pushing Agile, Psychological Safety, Netflix’ Failures, Team Charter How-to

Food for Agile Thought’s issue #171—shared with 20,122 peers—focuses on pushing agile, or better its futility as ‘agile’ needs to be pulled, we analyze current trends in corporate transformation efforts, and we ask: how safe did the attendees of your last workshop feel?

We also try to learn from Netflix’ failures, we come back to technical debt and its influence on product creation once more, and we compare our problems to the most pressing issues Marty Cagan has identified in today’s product-driven companies.

Lastly, we appreciate a great recipe on how to run a team charter creation workshop.

Have a great week!

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

Food for Agile Thought #171: Pushing Agile, Psychological Safety, Netflix’ Failures, Team Charter How-to

Continue reading Food for Agile Thought #171: Pushing Agile, Psychological Safety, Netflix’ Failures, Team Charter How-to

Food for Agile Thought #170: Agile Transformation Lessons, Agile’s 10,000-Hour Rule, UX Is a Team Sport

Food for Agile Thought’s issue #170—shared with 20,108 peers—focuses on agile transformation lessons. We learn that becoming ‘agile’ is one but not the only answer, that agile teams are no causation for business agility, and that the 10,000-hour rule applies to agile practitioners, too.

We also remind ourselves that user research is always a team sport, that NPS detractors are not necessarily bad-mouthing your product, and why there is a difference between cooperation and collaboration.

Lastly, we go back to Scrum basics and revisit the idea of delivering a ‘done’ product increment every single Sprint—without making excuses.

Have a great week!

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

Food for Agile Thought #170: Agile Transformation Lessons, Agile’s 10,000-Hour Rule, UX Is a Team Sport

Continue reading Food for Agile Thought #170: Agile Transformation Lessons, Agile’s 10,000-Hour Rule, UX Is a Team Sport