Age of Product's Food for Thought of December 4th, 2017—shared with 5,066 peers—focusses on agile myth busting, team dysfunctions, and how trust among teammates influences creativity.
We then dive deep into why switching to Kanban will not fixing your Scrum problems, and how to keep stakeholders and agile teams aligned.
We then support David Cancel’s notion that listening to customers is king, and learn how the Kano model supports product discovery. Speaking of which: Marty Cagan identifies key risks that you should better tackle during the discovery work.
Last but not least, Om Malik reflects on the Silicon Valley’s distinct lack of empathy for “normal people”.
Enjoy a great Sunday!
Agile Myths & Scrum
Scrum Is Not Agile:
Tanner Wortham reminds us not to confuse mechanics and mindset.
Architects Anonymous): No planning fallacy – Agile Anti Patterns(via
Nigel Hamer suggests to overcome the agile planning fallacy – being too optimistic, thus causing cost overruns and delays – by planning little and often.
Why switching to Kanban won’t solve your problems:
Marc Löffler lists ‘reasons’ why Scrum teams move to Kanban and explains why taking your (general) problems from Scrum to Kanban won’t help solving them.
AgileNZ Conference): Dealing with dysfunction(via
Matthew Hodgson shares his slidedeck from Agile NZ 2016 on team dysfunction, detailing how you can use couples counseling patterns to manage team conflict.
Teams, Trust, & Creativity:
David DeSteno, psychology professor at Northeastern University, explores the role of trustworthiness in the workplace, and its influence on creativity and team productivity.
Keep agile teams aligned:
Chris Butler introduces the ‘strategy kernel canvas’ to keep stakeholders and agile teams aligned.
Product & Lean
Mind The Product): The Importance of Listening to Your Customers by David Cancel(via
David Cancel addresses the importance of listening to your customers – “one of things we always talk about but few people do”.
Planning Product Discovery:
Marty Cagan talks about how he frames discovery work to ensure alignment and identifies key risks that need to be tackled during the discovery work.
Before the Backlog – The Vital Upfront Researchand :
Robert Sprigge explains the function of the business analyst who supports the product discovery part of the agile development process in detail.
Medium): Applying Leverage as a Product Manager(via
Brandon Chu explains why he asks every product manager joining his team to read ‘High Output Management’ by Andy Grove.
The Essential Read
The New Yorker): Silicon Valley Has an Empathy Vacuum(via
Om Malik reflects on Silicon Valley’s distinct lack of empathy for those whose lives are disturbed by its technological wizardry.