The only email you need to read to become a better product manager

Every week, I spend 50+ hours researching an important product management topic.

I summarize the learning into a practical guide.

I share it in this newsletter.

    No spam. Unsubscribe any time.

    Backlog grooming - this is how you should do it
    1 min read

    Backlog grooming - this is how you should do it

    If you do not say the words "Backlog Grooming" at least five times a week, you are not a cool product manager. Just kidding.

    Many companies think to have mastered the art of backlog grooming. However, few have understood it and reaped its benefits. Today, I share thoughts on what is backlog grooming, why is it essential, and how to do it effectively.

    What is it:

    Backlog, in simple terms, is a list of product features that you need to build to achieve product vision. Grooming, in this context, is the process of regularly refining, pruning and prioritizing your backlog.

    Why is it essential:

    The backlog communicates product priorities across the organization. Good backlogs are broad enough to capture new ideas. But, they are specific enough for engineers to plan the next sprint.

    How to do it effectively:

    1. Always keep the top priority items on the top. When the backlog gets large, group the backlog into near-term and long-term items.
    2. Groom at least once before a new sprint. I schedule two-hour meetings. But, this can be different for different teams. Work with engineers to decide the best duration for your team.
    3. Include all relevant leaders in the meetings. Encourage them to share their opinions and to agree or disagree with your prioritization decisions.
    4. Follow a set agenda for each meeting. My discussions include, but are not limited to:
    5. Deciding the priority of each item and the reason for selecting that priority.
    6. Creating dev estimates for prioritized items, including bugs and fixes.
    7. Clarifying details for more complex features
    8. Identifying risks, blockers and dependencies, if any.
    9. Removing redundant items from the list
    10. Define detailed requirements and acceptance criteria for prioritized items.