This post does what its title says: It shares my recommendations for creating an agile product strategy using the Vision Board. It addresses readers who want to find out more about using a product strategy in an agile, dynamic environment and readers who want to get better at using the Vision Board.Read More
Tag archive for "learning"
The sprint retrospective is the key mechanism in Scrum to improve the way people work. Some product owners believe though that they should not attend the meeting, and if they do then only as guests and not as active participants. But the retrospective does not only benefit the development team and the ScrumMaster; it is also an opportunity for the product owner to learn and improve, as this post explains.Read More
Working with sprint goals is a powerful practice. But many product owners and teams don’t leverage sprint goals or don’t apply them correctly: Sprint goals often state the stories to be implemented rather than the reason for undertaking the iteration. That’s rather unfortunate: Effective sprint goals serve to test ideas, to deliver features, and to foster teamwork. This post introduces a sprint goal template to help you write powerful sprint goals to build great products.Read More
Personas are a powerful technique to describe the users and customers of a product. While there is plenty of advice available on using personas in a traditional setting, employing personas effectively in an agile and lean context can be challenging. This post shares ten tips to create great personas when working with Lean Startup, Customer Development, and Scrum.Read More
Innovating existing products is a common challenge for many enterprises: New features are developed to enter a new market segment, to increase the market share, or to catch up with the competition. But while the product is being updated, small improvements and bug fixes have to be made to maintain the current version. This post shares my thoughts on balancing the innovation and maintenance work.Read More
Learning what a product should look like and do, and building solid, shippable software are different concerns. Separating the two aspects and distinguishing between learning and execution helps you manage the stakeholder expectations, select the right research and validation techniques, and choose the right sprint goals.Read More