Food for Agile Thought’s issue #107—shared with 11,115 peers—covers the change of mind of a design thinking skeptic, quick fix agile, and high-performance Agile.
We gain insight into why agile and DevOps are made for each other, and we get a fascinating report on Facebook’s continuous delivery practices.
Lastly, we turn again to product discovery and its various traps: from leading questions in user interviews to chasing the wrong product metrics.
Food for Agile Thought’s issue #106—shared with 10,783 peers—focuses on agile maturity and transition issues, escaping the feature factory, and asks whether sprints have become a burden.
We learn that the product people of WP Engine hate MVPs. Instead, they support SLC. (Which isn’t just another abbreviation but a sound product creation concept.) We also learn why management techniques of the 19th century will not deliver disruptive products today, and how to integrate UX with your agile practices.
Lastly, after months in the making, the Scrum Master Salary Report 2017 is available for download.
Food for Agile Thought’s issue #105—shared with 10,523 peers—covers continuous delivery, the growing commercialization of agile ideas — also known as business agility —, and helpful engineering practices like ‘skin in the game.’
There is also an excellent post on the difference in mindset between amateurs and professionals. (The article is helpful for team-building as well as stakeholder issues.)
Lastly, the Gartner Hype Cycle 2017 is out, the interview script to identify problems worth solving was also updated, and finally, someone wrote a brief guide to experience maps of all kinds.
Food for Agile Thought’s issue #104—shared with 10,408 peers—focuses on team building. We address the challenge how to build and scale high-performance agile teams. We learn how important creating the right culture is in that respect, and that the whole process starts with the first team.
We also revisit ‘dual track’ agile—aka continuous product discovery and delivery—and how to visualize your product development work to foster collaboration and inclusion.
Lastly, we dive into product roadmap planning—ProductPlan just published a new survey on processes and tools—, and how to pick the right product ideas from the abundance of available suggestions.
Food for Agile Thought’s issue #103—shared with 10,283 peers—covers a sad case of failed product discovery. (Yub, SoundCloud.) We also deal with agile misconceptions and hence expectation management for agile transitions, and how to create your agile workspace.
We revisit Google’s learnings on how to create effective teams, pick up ten mental exercises to up your product game, and learn that 15% of product people run weekly experiments.
Lastly, we dive deep into product analytics: what are the data traps to avoid, what is lean analytics, and when to start with what tools and techniques.
Food for Agile Thought’s issue #102—shared with 10,204 peers—applauds Mr. Hodgson for pointing at the obvious: There is no Spotify Model — you have to figure out ‘agile’ within your organization yourself. And by the way, ‘agile’ does not mean Scrum either. Hubspot ditched it years ago and got it right nevertheless. We also learn how to break up silos in your organization, and why people outside the product trenches regular have trouble understanding what we are talking about.
We watch Melissa Perri warn us to fall for the feature factory trap, and we come to understand that ‘feature creep’ is merely a disguise for us failing to identify the core of our product, and we figure out how to identify our customers’ need and to reverse-engineer it into a product.
Lastly, we listen to Jeff Gothelf to learn how continuous innovation can become the center of an organization.