TL; DR: Virtual 25/10 Crowdsourcing, Innovation Theater — Food for Agile Thought #254
Welcome to the 254th edition of the Food for Agile Thought newsletter, shared with 26,836 peers. This week, we applaud David for creating a free virtual 25/10 Crowdsourcing app; we learn what happened to a thriving agile culture once the company laid off the agile folks. Also, we accept the necessity to avoid delays in the management decision process if our agile transition shall bear fruit.
We then lift the confusion over vision and mission and the question who is responsible for which; we delve into a favorite corporate pastime and browse a well-curated repository of templates for product people for new shiny things to support our journey to build great products.
Lastly, we listen in to a conversation on Wardley maps with — Simon Wardley.
TL; DR: Successful Change, Product Centricity Lessons — Food for Agile Thought #253
Welcome to the 253rd edition of the Food for Agile Thought newsletter, shared with 26,802 peers. This week, we delve into successful change; we explore self-organization at scale, and we revisit the mantra of the two-pizza teams.
We then listen to the story of a product leader who has to move beyond ‘Agile’ & metrics; we pick up insights from a success story on transitioning to a product-driven organization, and we come back to the adage that ideas are worth nothing, only execution is.
Lastly, we consider whether regarding transitions as products would increase the chances of a successful change.
TL; DR: Resolving Team Conflict, Ikigai & Cynefin — Food for Agile Thought #252
Welcome to the 252nd edition of the Food for Agile Thought newsletter, shared with 26,787 peers. This week, we analyze options for resolving team conflict; we learn more about our team’s reason for being, and we think about how we are complicit in change fatigue.
We then advocate the unlearning of user stories, and we learn how to rejuvenate user growth by focusing on unlikely user groups. Moreover, we discover another five ways to tackle churn and improve retention.
Lastly, we embrace another help to get a hold on uncertainty and complexity with the Cynefin framework.
TL; DR: Software Factory Syndrome, Product Discovery — Food for Agile Thought #251
Welcome to the 251st edition of the Food for Agile Thought newsletter, shared with 26,781 peers. This week, we analyze the software factory syndrome; we apply Jocko Willink’s leadership principles to writing software, and we point at the elephant in the #noestimates room.
We then follow a CEO’s take on the importance of empowerment of product teams; we check the approach of a cross-functional team’s real-world collaboration model, and we learn about the next version of the future press release concept for (product) risk mitigation.
Lastly, we thank Jeff Patton for providing another helpful free ebook on how to figure out what is worth building. Spoiler alert: 85-plus percent of all startups get this wrong.
TL; DR: JTBD Guide, Good Retrospectives — Food for Agile Thought #250
Welcome to the 250th edition of the Food for Agile Thought newsletter, shared with 26,776 peers. This week, we appreciate a comprehensive JTBD guide with templates; we learn how to figure out whether a team is capable of having meaningful Retrospectives, and we reconsider our inclination to favor feature teams over component teams.
We then delve into opportunity mapping to improve our product work; we embrace the idea that we are probably not charging enough and that we should run some pricing experiments, and we explore the timing and the dynamic of innovation.
Lastly, we learn more about OKR throughout the different stages of product development work.
TL; DR: Ruinous Scrum, Losing Out to SAFe — Food for Agile Thought #249
Welcome to the 249th edition of the Food for Agile Thought newsletter, shared with 26,763 peers. This week, we analyze the ruinous Scrum claim of some developers; we empathize with a failed attempt to avoid SAFe, and we learn about the success of an ambitious change project with Scrum.
We then delve into the journey of Sarah Cooper and her approach to product discovery as a comedian; we reassure our belief that lying to customers is unacceptable, and we analyze five critical success criteria of Design Thinking.
Lastly, we thank Bob Sutton for an interview on change and identifying pockets of excellence.