Daily Flow - for practitioners, coaches & leaders in Product Management, Lean, Agile and Lean/Agile

Do you think work should be handed off once it meets the definition of done? On this episode, I talk about how developers should collaborate with the 'testers' and the important role that plays overall. Tune in, you might find some useful tips.  --- Send in a voice message: https://anchor.fm/dailyflow/message

In this episode, I talk you through some of the different ways and frameworks you can use to scale scrum and agile. The first rule is of course not scale but if you must, here are some ways to do so: 3:27 LeSS - what is it and how does it work? 6:29 Disciplined agile - what is it and how does it work? 7:21 Scrum at scale - what is it and how does it work? 8:21 SAFe - what is it and how does it work? 9:55 Nexus - what is it and how does it work? 11:43 Spotify ING - what is it and how does it work? 12:29 Flight Levels - what is it and how does it work? I also wrote a blog post on this, you can find it here: https://orderlydisruption.com/blogs/grow-agility-for-your-why/mirror-mirror-on-the-wall-preamble-to-1-of-4 --- Send in a voice message: https://anchor.fm/dailyflow/message

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.  --- Send in a voice message: https://anchor.fm/dailyflow/message

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? --- Send in a voice message: https://anchor.fm/dailyflow/message

How can we better deal with complexity in a Kanban footprint? Join me in this short episode to explore how. --- Send in a voice message: https://anchor.fm/dailyflow/message

In this episode, I go through some field stories regarding story points - why you shouldn't use them and offer alternatives.  --- Send in a voice message: https://anchor.fm/dailyflow/message

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 --- Send in a voice message: https://anchor.fm/dailyflow/message

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 --- Send in a voice message: https://anchor.fm/dailyflow/message

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 --- Send in a voice message: https://anchor.fm/dailyflow/message

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 --- Send in a voice message: https://anchor.fm/dailyflow/message