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

Daily Flow - where does Scrum Master end and agile leader begin

Daily meetings are common in Product Management, DevOps, Lean, Agile, and Lean/Agile. Kanplexity™ is no exception. Stop starting, start finishing. 

If you'd like to ask a question, leave a voice message via https://anchor.fm/dailyflow/message. 

John Coleman - top 10 Thinkers360.com - sweet spots are Scrum, Kanban, Kanplexity™, Lean-UX, and LeSS.

https://orderlydisruption.com

https://kanbanguides.org

https://www.linkedin.com/in/johncolemanagilitychef/

https://www.instagram.com/johncolemanagilitychef/

https://www.youtube.com/JohnColemanagilitychef

https://twitter.com/JohnColemanIRL

Business

Investing

Careers

Management & Marketing

Business News

Shopping

Management

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

Daily Flow: Scrum definition of done for non-software, Kanban board & column exit criteria

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

Daily Flow: Product backlog refinement and why is it encouraged?

Projects are artificial constructs to get money to get some work done. Key metric include time, scope, and cost. Products don't have scope. Scrum is for product development and works even better with Lean UX and Kanban as a powerful combination. Should we set up Scrum Teams dedicated to projects? 
0:34 What is a project? 
1:01 Deciding whether to use Scrum or not 
3:17 Problems with using Scrum for projects 
9:01 Managing expectations 
10:12 Scrum teams for each project - good idea?


Watch the video format here: https://youtu.be/VnahFNJgS-g

--- 

Send in a voice message: https://anchor.fm/dailyflow/message

Daily Flow: How do projects and Scrum go together?

Daily Flow - what is LeSS and why is it needed?

--- 

Send in a voice message: https://anchor.fm/dailyflow/message

Daily Flow - where does Scrum Master end and agile leader begin

Download our free app to listen on your phone