Artwork

Content provided by Tom Johnson and Lighthouse London. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Tom Johnson and Lighthouse London or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

#46: Weighting and Rating - How To Manage Your Backlog

17:46
 
Share
 

Archived series ("Inactive feed" status)

When? This feed was archived on August 01, 2022 16:54 (2y ago). Last successful fetch was on July 15, 2021 11:10 (3y ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Manage episode 241998429 series 1402906
Content provided by Tom Johnson and Lighthouse London. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Tom Johnson and Lighthouse London or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Prioritising the contents of your feature backlog is a vital part of determining your product roadmap. Tom and infrequent co-host Russ talk us through how to go about backlog weighting in order to work out what you should be building next. They cover:

  • Weighting by perceived value - Chatting to your users, stakeholders and frontline customer service team about what people are lacking, longing for or frustrated by.
  • Weighting by analytics - Using Google Analytics etc to provide the least subjective picture of what's needed.
  • Weighting by cost/resource - Working out the effort needed by teams to get the feature completed.
  • The tension between prioritising fixing bugs and building new things.

We also find out why sorting tasks alphabetically isn't a sensible framework!

Grab our backlog weighting template here (we've added some example features and scored them to get you started) 👉Google Sheets / Excel

  continue reading

52 episodes

Artwork
iconShare
 

Archived series ("Inactive feed" status)

When? This feed was archived on August 01, 2022 16:54 (2y ago). Last successful fetch was on July 15, 2021 11:10 (3y ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Manage episode 241998429 series 1402906
Content provided by Tom Johnson and Lighthouse London. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Tom Johnson and Lighthouse London or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Prioritising the contents of your feature backlog is a vital part of determining your product roadmap. Tom and infrequent co-host Russ talk us through how to go about backlog weighting in order to work out what you should be building next. They cover:

  • Weighting by perceived value - Chatting to your users, stakeholders and frontline customer service team about what people are lacking, longing for or frustrated by.
  • Weighting by analytics - Using Google Analytics etc to provide the least subjective picture of what's needed.
  • Weighting by cost/resource - Working out the effort needed by teams to get the feature completed.
  • The tension between prioritising fixing bugs and building new things.

We also find out why sorting tasks alphabetically isn't a sensible framework!

Grab our backlog weighting template here (we've added some example features and scored them to get you started) 👉Google Sheets / Excel

  continue reading

52 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide