In this guide, we’ll define what a story map is, look at a practical example, and provide a step-by-step guide and template to help you create your own story map.
The fundamental value of low-code/no-code platforms is expanding the delivery power of a niche workforce — aka engineers — to everyone.
Learn everything you need to know about the product owner role, including the responsibilities and job description, characteristics of a good PO, and common antipatterns.
For any product team, the top-down and bottom-up approaches are crucial strategies to process information and make better product decisions.
Many design teams have moved to a more agile viewpoint known as an intentional iterative design process. Here’s how to build one yourself.
Continuous discovery is all about ditching dedicated research projects and making them a permanent part of your team’s workflow.
By having a team charter, teams can have more focus and direction. It clearly spells out what the team will and won’t be working on.
“Economies of scale” is an old concepts that the unadvised might shrug to, but in reality economies of scale are the backbone of product management.
Scrum boards are an important elements of the software development process. They can help a PM and the engineering team deliver impactful products faster.
As a principle, only product backlog items that meet the definition of ready should be considered during sprint planning.
A communication plan describes what information must be communicated as well as to whom, by whom, when, where, and via what medium.
The 4 Ds of time management can help you be more productive as a product manager and instill important principles of task prioritization in your team.
