TL;DR —
Product Backlist is a list of tasks required to meet strategic plans of the product road map. Product backlog is about turning sky-high thinking into actionable tasks, including how-to and by whom. This article takes a look at the different ways people interpret and prioritise the product backlog. Method 1: Impact effort matrix, Stack Ranking, MoSCoW, Weighted Shortest Job First and Data-driven prioritisation. The backlog is a nuts and bolts to-do list, writing (arguably) for those who carry out the bulk of the work.
[story continues]
Written by
@alexomeyer
Co-founder & CEO at stepsize.com, creating the AI companion for software projects
Topics and
tags
tags
software-development|programming|team-productivity|software-engineering|technical-interviews|product-backlog|backlog|hackernoon-top-story
This story on HackerNoon has a decentralized backup on Sia.
Transaction ID: gQef3co8USvMx0-SGsVbu3oesPiu4W_Yw8eJAvrG_d4
