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 equal 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.
Food for Thought’s issue #101—shared with 10,065 peers—focusses on how to get ‘agile’ to work in your organization. We learn that an old OSS manual on do-it-yourself organizational sabotage still sounds very familiar today. We then get advice on how C-level manager may become more agile, and why we should replace Taylorism’s mindset of command & control with trust.
We also listen to John Cutler explaining his feature factory concept and embrace the importance of mental models to improve the way we learn. Speaking of stepping up the game, you can do so, too, with your next set of A/B tests. Kevin Shanahan provides a step-by-step guide.
Finally, we follow Piyush Tantia when he describes a new way for engineering applications and human interactions: behavioral design.
Food for Thought’s issue #100—shared with 9,957 peers—focusses on how to figure out what to build. We learn how to apply continuous product discovery, how to achieve product-market fit, how to use empathy mapping, and why a hypotheses backlog helps to avoid cluttering the product backlog.
We also discover Scrum misconceptions by analyzing job ads for scrum masters, and what cross-functional means with regard qualifications of individual team members. Moreover, we understand ways to improve your Kanban—by Mr. Scrum Jeff Sutherland himself—, and how the principles of the agile manifesto can be matched to change management.
Finally, there is an entertaining interview with Atlassian’s head of R&D on messiness, anarchy, structure, and what all of this has to do with creativity.