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.
The software testing lifecycle consists of multiple phases, including alpha, beta, and general availability, designed to enhance the user experience.
Finding out which dependencies matter and which impact timelines the most can be challenging. That is where the critical path method (CPM) can help.
As a business grows, project milestones evolve. Larger companies are typically more ambitious, which impacts how milestones are defined and what significant progress is.
Kanban is the simplest way of visualizing the status of the work and understanding the next best action to keep the flow going.
User research democratization is about expanding access, participation, facilitation, and ownership of UX research to other non-user researching teams.
The stage-gate process divides projects into different stages with gates (reviews) in between them. Results of the previous phase are presented to stakeholders.
A technical debt register brings transparency and clarity as to what type and how much debt you have and can be used to monitor and review your debt ratio.
As a PM, tracking and managing work via a burndown chart is a shared responsibility with the engineering manager and scrum master of the team.
