Split heads are people that are assigned to multiple teams. A team of split heads has many negative effects but there are ways around those.
Stakeholder management is a core activity for anyone working in product development. It is key to building a successful product in the confines of a company. Also, it is rarely a topic of conversation.
Many believe that agile coaches can't be product coaches. I disagree. A good agile coach and product coach want the same: great products.
It can be difficult to get buy-in from the team members for a new approach like Scrum. The most effective way to create an open mind is showing what is in it for them. Making the daily work of the team easier and building a relationship on eye level are the key. These eight best practices are aimed at doing exactly that.
A large portion of the workforce is unhappy in their job. Why do they not quit? What are the benefits of quitting a miserable job?
There are ways to conduct effective brainstorming sessions. It’s just not the way they are typically done. Psychology is key.
Anyone responsible for a product knows the situation. Some stakeholder comes with a feature request along the lines of “Can we please add Feature X to the product. It is important because of reasons. Please add it yesterday. Thanks.” How can you deal with these stakeholder requests?
A user story map visually depicts the entire backlog along the user journey while simultaneously showing the priority of user stories associated with each step. User story mapping is an excellent communication aid getting everyone on the same page and it allows for easy definition of releases. It is where you can clearly see the steps from MVP to fully fledged solution.
5 ways to deal with the challenge of attempting to establish a Scrum team (actually any new team) within an existing organization.
Not all of us have a "real" mentor. Formulating your issues and imagining the mentor's advice works as well! It is surprisingly easy.
Continuous Discovery Habits is a practical, extremely useful book. I share the main concepts and the three most important personal takeaways.
The opportunity solution tree is an extremely useful method. Having already covered the why, how and what of the opportunity solution tree, I will focus on the best practices that I have found to be crucial in maximizing the potential of the OST.
The opportunity solution tree (OST) was invented by Teresa Torres as a means to collect and visualize the opportunity space. It is a model or mental representation that clearly links product goals to user needs and to the options for solving those needs. In product discovery, it is a powerful tool for creating a clear structure of what the team wants to achieve.
We often feel the need to immediately fill silence with answers, comments, or questions. And I get it, being in a group where nobody speaks for some moments can be extremely uncomfortable and awkward. Being able to withstand the urge to say something in those moments of silence is not easy to do.
The core of agile development - it should be at the heart of all product development efforts for that matter - is iteratively moving forward. We need to understand the impact of what we are doing without waiting for too long. For this reason, Product teams need to use leading indicators so that they can immediately measure the effectiveness of their product development.
Sometimes you come across a book at just the right time. The content immediately makes sense and you cannot stop reading. This happened to me when I recently read Inspired by Marty Cagan.