Michael Jamesis a software process mentor, team coach, and Scrum trainer with skills in Product Ownership (business), Scrum Mastery (facilitation), and the development team engineering practices (TDD, refactoring, continuous integration, pair programming) that allow Scrum to work. MJ has been involved with LeSS (Large Scale Scrum) longer than anyone else on the US West Coast. He is a recovering “software architect” with programming experience back to the late 1970s, and including control systems for aircraft and spacecraft
Edited Version (about 32 minutes)
Original Version (about 60 minutes)
We often hear that the Agile approach to multi-team development is to pre-divide products into small independent pieces for different teams to work on, perhaps using implementation approaches such as microservices and coordination approaches such as “Scrum of Scrums.” This advice illustrates widespread blind spots in the Agile coaching and training community. We will challenge those in this online discussion.
To get the most out of this session, we suggest reading the comic book that went viral Why “Scrum” Isn’t Making Your Company Very Agile, How Misconceptions About The Product Owner Role Harm Your Organization, And What To Do About It.
Related artifacts:
- Why “Scrum” Isn’t Making Your Company Very Agile, How Misconceptions About The Product Owner Role Harm Your Organization, And What To Do About It.
- You Won’t Change Your Organization Without An Optimization Goal