When detailing how to build a feature, PMs must make sure a lot of decisions are made. In our interviews with over 300 PMs, we saw that the best of them handle this without becoming overwhelmed by properly framing and following up on these decisions. The Iceberg of Micro-Decisions Most PMs don’t think about it …
Good PMs write some kind of document to detail how to develop a feature. This gives the team a central place to know what has been said and decided regarding the feature. To be useful, this document needs to cover the most important details, and so commonly runs to a couple of pages. With several …
Does the term “Double Diamond” sound familiar? Chances are, it does. The Double Diamond model describes a framework that designers use. Originally intended for developing physical products, this model has recently started gaining popularity in software development, and for good reason. Understanding how the Double Diamond fits into Dual-Track Scrum can help you work better with discovery sprints and understand the design process on a deeper level.
Being a PM is not a piece of cake. You probably know that by now. You have probably also encountered a long list of features hanging in the air, unsure why half of these features were on that list in the first place. This is exactly why brief discovery projects are important in figuring out whether it’s worth developing a feature before going into the details of how to develop it at all.
You probably know all about roadmaps and user story mapping in agile product management. Both are effective tools used to capture and communicate your product’s goals and the journey to achieve them. User story mapping, for instance, will help to prioritize among relevant features and user stories and give the development team a better understanding …
