Times have changed in the world of product development. Delivery cycles have shortened significantly over the past two decades, so
Successful and popular products are rarely born in moments of inspiration, nor are they likely to just pop into the minds of entrepreneurs or product managers. More often, great products are the result of a rigorous and effective product discovery process.
Information matters. But what information team members have and when they get it is just as important as the information itself. In the world of Agile product management, information is best funneled to teams through sprint planning, an essential Agile productivity tool. If sprint planning is not used – and product owners or scrum masters don’t take the time to schedule upcoming work properly – team members might misunderstand what they must focus on and when.
Does your product team sit around with little work to do, wondering what you’re going to do next quarter? Yeah, I didn’t think so. If there’s one thing that product teams all have in common is that they all suffer from the opposite problem – too many things to do.
As a product manager, you never suffer from a lack of things to do. Sometimes when you have so many things you could do, it’s difficult to pick the things you should do. You know you need to focus on outcomes that will help customers solve their problems, and benefit your company as well, but how can you identify those features?