Agile without a Backlog - What Is a Backlog and Do I Need one?
As an exercise, try to completely eliminate your project's backlog and think about what effects this would have on your team. Could this be a way to improve?
Contents:
0:00 Introduction
1:48 Obstacles to Planning
3:33 How to Fill a Backlog
6:43 The Customer
10:34 How large Should the Backlog Be?
13:29 The Overhead of Releases
15:52 The Backlog as a Measurement
18:02 What about Scrum?
21:57 What about Sprints?
23:46 Sprints vs Agile Architecture
27:00 Closing
► Donate a Coffee: https://ko-fi.com/lode
► Agile Coaching: https://www.lode.de/product/agile-coa... (half-price if public)
► Blog-Article: https://www.lode.de/blog/agile-withou...
► Technology: https://kit.co/clemenslode/streaming
► Chatting on Discord: / discord
Summary:
► Product backlogs are similar to shopping lists.
► Each item on the backlog is an assumption whose validity is tested only once we start implementing it.
► Each item is the result of a conversation with the customer.
► To react quickly, involve the customer in the development process.
► Put only as much into the backlog as you can immediately implement.
► Everything else is wasted time with the customer as the situation might change in the future.
► The backlog is not a roadmap.
► Scrum's idea of a backlog seems to be more like a workaround to problems when trying to work in an agile way.