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.
by Stefan Wolpers|Agile and ScrumAgile TransitionNews
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.
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.
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.
Food for Agile Thought’s issue #169—shared with 20,091 peers—focuses on agile trust, or the lack thereof, how to disagree but commit effectively, and why a big change initiative may be advantageous in some cases.
We also dive deep into how to engage effectively in communication with your stakeholders without burning bridges, why idea velocity and execution velocity are two critical factors for a healthy product roadmap, and speaking of which: what continuous alignment with your stakeholders is all about.
Lastly, the good folks at Rootstrap made an epic ebook on customer development or product discovery publicly available. Kudos!
Food for Agile Thought’s issue #168—shared with 20,064 peers—focuses on the importance of the product backlog, how to create an experimentation culture to verify product hypotheses, as well as on the process of how to create a decent product vision in the first place.
We also learn about the differences and similarities of LeSS and Nexus, the two Scrum scaling frameworks appealing to purists, and enjoy CB Insights guide to moron-proof corporate innovation.
Lastly, we join Marty Cagan when he reveals the secrets to building outstanding product organizations with folks like you and me.
