Value and Kanban: isn't Kanban just about outputs? Isn't Kanban missing a trick with value and organizational capability?
How do we deliver value in Kanban? In this episode, John starts off by talking about by briefly introducing evidence-based management (EBM) and explains its 4 key values: time to market, ability to innovate, current value and unrealized value. John then moves on to look at how these values operate in the context of Kanban (2:35) and things that may actually harm your ability to deliver value. John then goes on to talk about classes of service in Kanban and why in his opinion, intangible is the preferred class of service.
25 Apr 202213min
Balancing UX with shipping fast in scrum? A deeper look into each box of the Lean UX canvas - are you doing User Experience the right way?
Is there such thing as balancing UX with shipping fast in scrum? Is there even such thing as shipping fast in scrum? How can we know what is value when we don't know the end-user? What happens in each box of the Lean UX canvas?
12 Apr 202216min
Daily Flow - dealing with complexity in a Kanban footprint
How can we better deal with complexity in a Kanban footprint? Join me in this short episode to explore how.
30 Mar 20229min
Daily Flow - a story about story points and an alternative, throughput
In this episode, I go through some field stories regarding story points - why you shouldn't use them and offer alternatives.
29 Mar 202214min
Daily Flow: Sizing & Forecasting
Popular patterns for sizing including "exact" time/cost, relative, right-sizing, and #noestimates. Popular patterns for forecasting include Gantt charts(ugh!), burnup/down charts(hmmm), and probabilistic forecasting(oooo). An emerging trend is with right-sizing and probabilistic forecasting. It's not all sunshine and honey, context matters, and it's dangerous to over-simplify. Let's laser focus on the upsides and downsides of each of these options. Time Stamps: 0:00 Approaches & Their Upsides 9:00 Downsides of Approaches 19:02 Approaches for Forecasting
29 Mar 202220min
Daily Flow - where does Scrum Master end and agile leader begin
Timestamps: 0:00 Introduction 0:22 scrum master vs agile coach 1:46 The conversations you might have as a leader/scrum master/agility coach 3:48 What I expect a scrum master or agility coach to do 10:00 What about a leader? 13:17 Some things to consider stopping Watch the video version of this episode here: https://youtu.be/9n90oOChNQY
9 Nov 202117min
Daily Flow: Scrum definition of done for non-software, Kanban board & column exit criteria
Let's focus on non-software - let's consider a people recruitment process as an example. What does "done" mean? Valuable, useful, and usable in Scrum, whatever the organization/team decides it is. "When someone's need was met" in Agendashift. Maybe a near to exit stage on a Kanban board... How is "done" different from acceptance criteria for a Scrum product backlog item or subtasks on a Kanban work item? 0:00 Introduction 3:42 The definition of "done" 5:27 Definition of done in Kanban & subtasks 7:05 Acceptance criteria may become obsolete 7:53 Different categories of quality standards 10:44 Recruitment example 18:07 Definition of Done in Kanban for non-software 20:17 One of the things I love about kanban 24:28 Answering questions and comments Watch the video version of this episode here: https://youtu.be/CZTarEzFvBc
3 Nov 202130min
Daily Flow: Product backlog refinement and why is it encouraged?
Product Backlog Refinement is an activity in (single team) Scrum, with supporting events for multi-team Scrum in Nexus and LeSS. Why is it encouraged? Is there something equivalent in Kanban? 0:00 Introduction 0:27 Product backlog refinement in Scrum 8:03 How do we obtain a common understanding 9:06 A nerve centre for discovery 15:00 Optional practices 15:11 Misunderstandings of product backlog refinement Watch this in the video format here: https://www.youtube.com/watch?v=Gti64RAlVL4
29 Okt 202116min
