Skip to content
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.

Commit

Permalink
Update product-planning.md (#8448)
Browse files Browse the repository at this point in the history
  • Loading branch information
csells authored Jan 17, 2024
1 parent 58b556b commit d454584
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions content/departments/engineering/product-planning.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,21 @@ or another review meeting will be scheduled to follow up until there is alignmen
Note, not every team will have work to do that applies to every goal every
quarter. Likewise, not every work item is expected to meet a strategic goal.

## Review Effectiveness

Some tips for having an effective review:

- Make sure the priorities for your work is clear -- what's Must Have (P0),
Want To Have (P1) and Nice To Have (P2)? What could get cut?
- Make sure the customer (internal and/or external) impact is clear -- if we do
this work, what's going to be the value to the customer?
- Make sure the business impact is clear -- if we do this work, how does that
help us achieve our strategic goals?
- In addition to ensuring that the EPD team is aligned before heading into the
review, try to get as much alignment with execs ahead of time as possible.

I've noticed that the teams the follow this tips have a smoother review process.

## Engineer Scoping

For any launch, we have a finite amount of time and a finite number of engineers.
Expand Down

0 comments on commit d454584

Please sign in to comment.