Topic Title: Kanban Cannot Save You: Overcoming Scrum Antipatterns without Abandoning Scrum
Initiator: Sam Falco
Participants: Denise Duggan, Jamie Leatherman, Joey deVilla, Abbie Field, Lemont Chambliss, Eileen Cease, Laynn flannery, Ed Brunner, Albia Santiago, Charlie Neighbors, Marilyn Brislin, Liasa de Almerde, Anne Jones, Adam Ullery, Richard Martinez, Tom Clemente, Michael C. McGreevy
Discussion Highlights:What problems do we see in Scrum that lead teams to say, “Let’s do Kanban,” and how can we solve them?
Antipatterns:
- Constantly carrying over stories into the next sprint
- “We’re a service organization, we have to do product support issues the minute they come in.” (Kanban is actually good for this type of problem… if that’s really the problem)
- Priorities change
- Management does not value team focus
- Role alignment != actual skills
- Environments don’t match (structural issues)
- Team member churn
- Team member attrition
Ideas for Action/Next Steps:
Correcting Course – addressing the antipatterns
- Continuing education – outsider or internal
- Validate whether executives really commit to Scrum
- Enforce and respect the Product Owner role
- Relaunch the Scrum Team(s)
- Listen to your coaches
- Don’t have a coach? Get one.
- Can’t get a coach? Get a mentor:
- Local Agile meetups
- Slack Channel – AgileFlorida.slack.com
- Take the Valpak Agile Tour
- Read/Understand Agile books and apply the lessons
- Pick your battles–don’t try to fix everything at once
- Find your “why”
- Solve your people problems