When I am teaching CSM and CSPO classes I frequently get questions from students who have trouble understanding how work flows from the release level down through product backlog items like User Stories on down to the task level. I do cover this in class but for some, it is not so easy to see.
If you'd like to reach out to Judy with follow up questions, here is her contact info:
This episode features a student question and a special appearance by Adam Weisbart.
I recently had a student in class who was struggling to get her team to participate during retrospectives. This is a fairly common problem for teams that are either trying to get the hang of how to run a retro, or teams that may have stuck with a particular tactic for so long that it has stopped working.
I invited Adam Weisbart to join me for the podcast. If Adam's name sounds familiar, it may be because you've taken a class from him, seen him speak at a conference, watched the video "Sh*t Bad Scrum Masters Say", or because you've used his Agile Adlibs or his retrospective facilitation kit, Recess. (We'll be spending time on those last two during the interview.)
If you've got teams that aren't fully engaging during your Retrospectives, you are not alone. This podcast has some ideas that should help you get that turned around.
Urs Reupke is a Certified Scrum Trainer and Agile Coach who works for the Hamburg-based Agile Consultancy It-Agile. A lot of Urs’s time and attention is focused on the work he does coaching management and providing leadership consulting as they move towards adopting a more Agile approach to work.
If you’d like to contact Urs, here is how you can reach him
This podcast features an interview with Johanna Rothman and Mark Kilby about their new book "From Chaos to Successful Distributed Agile Teams: Collaborate to Deliver"
* Update - you can download a transcript of the podcast here.
Distributed Teams present challenges for any group of people trying to work together. This is true in a traditional approach to project work, but maybe even more so in an Agile approach, where many of the frameworks are based on the idea of co-location. The challenges distributed teams face are present regardless of whether you are separated by 12 time zones or by a single flight of stairs. It can absolutely work, and there can be many benefits to working distributed. The big question is how?
In their new book “From Chaos to Successful Distributed Agile Teams: Collaborate to Deliver", Johanna Rothman and Mark Kilby deliver the practical answers we all need to help our distributed teams succeed. During the interview Mark and Johanna explain who they wrote the book for and how it can help. We also walk through a few of the most critical practices that help distributed teams work well together, and the authors share some tips that they did not include in the final version of the book.
Now... I generally try to remain objective in this blog/podcast, but...
GO BUY THIS BOOK! YOU NEED THIS BOOK!
As someone who works with and on distributed teams, I have questions of my own with respect to steps that can be taken to foster a distributed team's success. This book had answers/strategies for all my questions and it is sure to be an invaluable resource for anyone working on or with distributed teams.
Links mentioned in the podcast
"From Chaos to Successful Distributed Agile Teams: Collaborate to Deliver" can be purchased on:
Dave interviews Johanna and Mark about writing as a Distributed Team at Agile 2018 https://youtu.be/JMxEeeCtK2I
In this episode of the Reluctant Agilist, Certified Scrum Trainer and Agile Coach, Eric Tucker, and I talk through two related questions that came from students in my classes:
- What is the best way to inject defects into a sprint?
- How do you reset expectations with stakeholders if you are going to fail a sprint?
During the interview Eric and talk about why adding/removing work from a sprint is generally not something you want to do, but what you should do if it is unavoidable. We also touch on what to do if the team discovers that they will not be able to deliver on their sprint forecast, why you want to make sure the stakeholders know ahead of time and what some other options might be.
If you’d like to reach Eric with follow up questions, here is his contact information:
The Reluctant Agilist is hosted on ProjectManagement.com. This podcast may not be copied or reused without their permission.