By John Coleman PKT, PST, LSFT, Thinkers360 top 10
The podcast currently has 30 episodes available.
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
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
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
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
Daily Flow - what is LeSS and why is it needed?
Are you in an agile team? Does it feel like meeting mania? It doesn't have to be.
Timestamps:
0:00 Introduction
0:24 Meetings with agile
2:12 Three questions in the Scrum guide
4:04 The situation to strive for
7:13 Sprint planning
10:15 Product backlog refinement
13:50 Having a chat with key stakeholders
Link to YouTube video: https://youtu.be/t99iRz-h2Xs
Daily Flow hosts the amazing Steven Tendon to discuss constraints in knowledge work. This episode is packed with fun anecdotes as well as the story of Herbie.
Join us in discussing Steve's amazing work in his own Tame Flow.
1:48 - Basics of constraints in knowledge work / understanding what is a constraint
2:51 - Story of Herbie
8:53 - Finding the constraint
15:31 - Moving people around
22:33 - Rating behaviour/mental models as a constraint
Remember those three annoying questions? Thank goodness they no longer exist in the Scrum guide.
0:00 Introduction
2:05 Five domains to think about when working on problems...
3:49 What to talk about in the daily scrum
5:15 From a flow perspective...
7:58 Getting to know each other
10:57 Answering questions and comments
Nexus is Scrum.org's scaling/de-scaling pattern. It's simple and it's practical.
0:00 Introduction
1:03 The cake metaphor
4:55 A basic Nexus
7:58 Why I like Nexus
10:50 Minimising dependencies
12:49 The Nexus daily scrum
15:47 The 2021 update
18:25 A key distinction between LeSS and Nexus
21:10 Answering questions and comments
Remember those three annoying questions? Thank goodness they no longer exist in the Scrum guide.
The podcast currently has 30 episodes available.