Scrum is a powerful framework that connects the person in charge of the product with the individuals designing and building it. But it offers limited advice on how to collaborate with the stakeholders and involve them in strategic product decisions. This issue can be addressed by forming a product team that extends the traditional Scrum team, as I explain in this article.
Meetings are essential to align the stakeholders and development team members and make the right product decisions. But we’ve all been stuck in bad meetings that lacked a clear objective, didn’t have an agenda, were dominated by a few vocal individuals, started late, or overran. Such meetings are unproductive and demotivating. It doesn’t have to be this way, though. The tips I share in this podcast episode will help you run successful product management meetings that engage the attendees and help you achieve the desired outcomes.
Meetings are essential to align the stakeholders and development team members and make the right product decisions. But we’ve all been stuck in bad meetings that lacked a clear objective, didn’t have an agenda, were dominated by a few vocal individuals, started late, or overran. Such meetings are unproductive and demotivating. It doesn’t have to be this way, though. The following ten tips will help you run successful product management meetings that engage the attendees and help you achieve the desired outcomes.
The product roadmap can be an incredibly useful planning tool that aligns the stakeholders and development teams and communicates how a product is likely to evolve. Sadly, that’s not the case for all roadmaps. To ensure that your product roadmap is effective, you should make it goal-oriented or outcome-based, shared, and actionable, as I explain in this article.
The product roadmap can be an incredibly useful planning tool that aligns the stakeholders and development teams and communicates how a product is likely to evolve. Sadly, that’s not the case for all roadmaps. To ensure that your product roadmap is effective, you should make it goal-oriented or outcome-based, shared, and actionable, as I explain in this episode.
The product vision can be a powerful instrument to inspire and align stakeholders and development teams. But in practice, it is not always effectively applied. This article shares questions about the product vision I am frequently asked together with my answers.
I am a big fan of making decisions collaboratively, as it leverages the expertise of the stakeholders and dev teams; it creates a shared understanding; and it generates stronger buy-in. But deciding together can be challenging: The most senior stakeholder might try to dictate the decision, the group might shy away from difficult conversations, or people might get stuck in endless debates without knowing how and when a decision will be made. This episode shares eight practical tips to help you avoid these pitfalls and harness the full power of collaborative decision-making.
I am a big fan of involving the stakeholders and dev teams in important product decisions. But deciding together can be challenging: The most senior stakeholder might try to dictate the decision, the group might shy away from difficult conversations, or people might get stuck in endless debates. This article shares eight practical tips to help you avoid these pitfalls and harness the full power of collaborative decision-making.
Despite its importance, product strategy is not always effectively practiced. One of the key issues I encounter in my work is that strategy and execution are not aligned but rather disjointed. To address this issue, I have developed an iterative process called the product strategy cycle. The cycle systematically connects strategy and execution so that the former guides the latter and insights gained from the tactical work help evolve the product strategy. In this episode, I explain how you can use the cycle to join up product strategy, product roadmap, KIPs, product backlog, and development work, and I discuss the role stakeholders and development team members play in making effective strategic product decisions.
Despite its importance, product strategy is not always effectively practiced. One of the key issues I encounter in my work is that strategy and execution are not aligned but rather disjointed. To address this issue, I have developed an iterative process called the product strategy cycle. The cycle systematically connects strategy and execution so that the former guides the latter and insights gained from the tactical work help evolve the product strategy. In this article, I explain how you can use the cycle to join up product strategy, product roadmap, KPIs, product backlog, and development work, and I discuss the role stakeholders and development team members play in making effective strategic product decisions.