TL; DR: How Elon Musk Would Run YOUR Business with Joe Justice
Joe Justice worked for Bill Gates, Jeff Bezos, and Elon Musk.
In this Hands-on Agile meetup, Joe shared DX, or Digital Transformation, the agile operating system for TeslaSpeed—a term coined by the EU Commission to talk about how fast Tesla moves and how fast they need to move now.
📺 Watch the video now: How Elon Musk Would Run YOUR Business mit Joe Justice — Hands-on Agile EXTRA.
🎓 Join Stefan in one of his upcoming Professional Scrum training classes!
📖 Get notified when the Scrum Anti-Patterns Guide book is available!
Abstract: DX, or Digital Transformation
Joe shared DX, or Digital Transformation, the agile operating system for TeslaSpeed—a term coined by the EU Commission to talk about how fast Tesla moves and how fast they need to move now.
The 12-step DX process brings companies from where they are now toward their manifest destiny.
Meet Joe Justice
Joe Justice is a TED.com speaker and guest lecturer at MIT and Oxford University in England. He has been featured in Forbes five times to date, including as owner of a “Company to watch” by the Forbes Billionaire Club, cited in more than eight business paperbacks and hardcovers, and is the subject of a Discovery Channel documentary for his work creating the disciplines “Extreme Manufacturing,” “Agile Hardware,” and “The Justice Method.”
Joe Justice founded WIKISPEED and operated Agile@Tesla from the global headquarters of Tesla‘s Fremont, California.
Watch the recording of Joe Justice’s talk on How Elon Musk Would Run YOUR Business now:
Q&A Session with Joe Justice
During the Q&A session, Joe Justice answered the following questions from attendees:
Who sets the rules for limiting autonomy?
What patterns or principles did the Musk companies use to reduce the cost of change in hardware development? Regression testing and integration testing, I’d presume to be the first few mentioned, but what else?
What is your view on Scrum or whatever framework at scale? Fundamentally, what considerations should you make once your organization can be expressed only in terms of the power of 3?
What is your advice on bringing together teams who develop software components with other teams who develop hardware components of a common product (everything has to come together, but these teams have different working methods)?
(Please note that the questions have been slightly edited to improve legibility.)