Cracking the PM Career: The Skills, Frameworks, and Practices To Become a Great Product Manager (Cracking the Interview & Career)

Keep a leaderboard of how many bugs each person fixes and have a variety of small prizes: most bugs fixed, oldest bug fixed, bug with the highest number of customer reports fixed, etc. You can also consider bringing in snacks, playing music, or having fun activities to get people excited.

A PM shouldn't dictate a solution to the designer; rather, they should share their thoughts in a way that's respectful of the designer's role.

The "Key Trade-Offs & Decisions" section highlights the places where the PM considered alternatives to help readers understand the reasoning. Problems Companies often build terrible products that could have been much better with improved PMing. PMs don't always know what it takes to PM well. The best PMs aren't always effective at man

Our goal is for this book to help more people become great product managers.

Break work into incremental launches and validate early

Common tasks during the design phase include: Writing a spec Deciding what functionality is in or out Negotiating dependencies with other teams Whiteboarding with designers and engineers Giving feedback on design Running usability studies

The tasks or stories usually have cost estimates—for example, in the format of story points. Story points are an abstract unit of cost; 1 point is the easiest possible work, 2 points is work that should take twice as long as a 1-point task, and it increases from there. Engineers (not PMs) set the cost estimates.

In Scrum, teams work in sprints of one to four weeks. At the start of each sprint, the team does sprint planning where they pull work from the product backlog into the sprint backlog and estimate how much work can be done in the next sprint. During the sprint, team members pick work off the backlog and meet daily for a fifteen minute standup meetin

The design phase is not just about putting your ideas into pictures; it also includes expansive thinking and validating your ideas with real people. This includes both the user experience (e.g., mock-ups and visual prototypes) and the technical solution (design docs and technical prototypes).