Food for Agile Thought’s issue #119—shared with 12,907 peers—addresses the decision process in groups, how XScale’s business agility approach works, and why cargo cult agile usually means running in circles.
We share a handy guide on how to deal with engineering teams, and why you need to include them in any persona creation activity. We also have a look at Buffer’s 6-week product cycle.
Lastly, we cover why product management by committee is doomed from the start, and we learn about how hard it is as a corporation to get from a big idea to a sustainable product.
Food for Agile Thought’s issue #118—shared with 12,812 peers—addresses the not so apparent Scrum troubles: it is hard, expensive and utterly useless if implemented half-heartedly.
Jeff Patton explains a range of human flaws and failures during product discovery, which is the reason that AirBnB runs experiments diligently—learn from Jan how that works in detail.
Lastly, we cover once more the issue of brilliant engineers who also happen to be jerks, and the pointy-haired Boss finally reveals the purpose of predictions.
Food for Agile Thought’s issue #117—shared with 12,693 peers—covers the agile periodic table, a remarkable visualization of agile principles and practices. We also learn more about the background of the changes to the Scrum Guide leading to the 2017 edition.
In addition to that, we feature survey results that prove that being able to prioritize product features is the most important trait that defines your success as a product owner or product manager.
Lastly, the WhatUsersDo Community on Slack had a great session with tips & tricks from Steve Portigal on user testing. (By the way, the Hands-on Agile Slack community just crossed the 2000 member threshold, see below.)
Food for Agile Thought’s issue #116—shared with 12,576 peers—covers agile experiments, and how to free yourself from five failure anxieties when transitioning to agile.
We also learn how to motivate people to be on time (without playing Bob Marley), and how to rebuild trust in a product and engineering team.
Lastly, we learn from Julian Birkinshaw—Professor of Strategy and Entrepreneurship at the London Business School—about Agile’s impact on strategy.
Food for Agile Thought’s issue #115—shared with 12,439 peers—focuses on winning hearts and minds in the organization as we borrow from political campaigns, and we now can convince financially-minded business people about the Agile ROI.
We also go the extra mile providing transparency on the product process, we learn how to translate prioritization into numbers every MBA understands, and we kiss ‘one-size-fits-all’ Agile good-bye.
Lastly, John Cutler asks the right question: Shall the product organization focus on learning fast or shipping fast?
Food for Agile Thought’s issue #114—shared with 12,308 peers—focuses on team building and rockstar engineers, or better: the lack of them. We also come back to psychological safety and wonder whether the term is overused or abused?
Steve Denning explains why SAFe == pre-Copernican command and control thinking, and we learn what misconception lets software product spiral out of control.
Lastly, Kate Bennet shares the results of her survey on product prioritization methods.
