In this guide, we’ll compare the three most popular agile frameworks (besides scrum): scrumban, iterative development, and lean development.
For any product team, the top-down and bottom-up approaches are crucial strategies to process information and make better product decisions.
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.
Value chain analysis helps find a company’s competitive advantage and increase profits. Each product phase is important for the analysis, from beginning to end.
Testing assumptions is one of your most important responsibilities as a PM. It’s also one of the most ambiguous. Using an assumption map can help make validating your assumptions more tangible.
In practice, technology stacks are extensive. The combination of potential technology is endless, but I cannot emphasize the downsides of using the wrong tech stack enough.
In this guide, we’ll define workflow management, demonstrate how to implement a workflow management system in your organization, and review the benefits of streamlining your processes.
As a principle, only product backlog items that meet the definition of ready should be considered during sprint planning.
While being a first mover can bring you a tremendous competitive advantage, it also comes at a cost. In this guide, we’ll weigh the pros and cons of being first.
