Artwork

Contenuto fornito da Agile for Humans, LLC, Agile for Humans, and LLC. Tutti i contenuti dei podcast, inclusi episodi, grafica e descrizioni dei podcast, vengono caricati e forniti direttamente da Agile for Humans, LLC, Agile for Humans, and LLC o dal partner della piattaforma podcast. Se ritieni che qualcuno stia utilizzando la tua opera protetta da copyright senza la tua autorizzazione, puoi seguire la procedura descritta qui https://it.player.fm/legal.
Player FM - App Podcast
Vai offline con l'app Player FM !

Scrum is Hard and Disruptive 10 - Leave Scrum Along

8:35
 
Condividi
 

Manage episode 413135368 series 2854678
Contenuto fornito da Agile for Humans, LLC, Agile for Humans, and LLC. Tutti i contenuti dei podcast, inclusi episodi, grafica e descrizioni dei podcast, vengono caricati e forniti direttamente da Agile for Humans, LLC, Agile for Humans, and LLC o dal partner della piattaforma podcast. Se ritieni che qualcuno stia utilizzando la tua opera protetta da copyright senza la tua autorizzazione, puoi seguire la procedura descritta qui https://it.player.fm/legal.

Ryan and Todd look back at a 2006 post by Ken Schwaber, which covers 15 ways Scrum is both hard and disruptive.

The tenth statement from Ken:

"Scrum is not a methodology that needs enhancing. That is how we got into trouble in the first place, thinking that the problem was not having a perfect methodology. Effort centers on the changes in the enterprise that is needed."

Scrum's Nature and Misunderstandings: The discussion emphasizes that Scrum is not a methodology needing enhancement, as attempting to perfect it led to initial troubles. It’s highlighted that Scrum is a framework, not a methodology, and should not be altered excessively.

Scrum's Simplicity and Accessibility: When Compared to more complex methodologies and frameworks, Scrum’s guide is concise (13 pages), making it easily understandable without the need for extensive training, unlike more elaborate methods that require significant learning and interpretation.

Adaptability and Contextual Use of Scrum: The speakers discuss the importance of adapting Scrum practices based on specific team and project contexts. They share personal experiences where certain practices were effective in one situation but not in another, illustrating Scrum’s flexibility and the need for situational awareness.

Evolution of the Scrum Framework: The evolution of Scrum is discussed, noting that over time, the framework has become more streamlined, with a focus on removing unnecessary elements rather than adding new ones. This evolution aims to prevent dogmatic adherence to processes and encourage teams to focus on the intent of each Scrum event.

Focus on Organizational Change Over Scrum Modification: The conversation shifts to the idea that efforts should be directed toward changing organizational structures and practices that hinder agility, rather than trying to improve Scrum itself. Emphasis is placed on overcoming organizational impediments to enhance the delivery of value to customers and gain competitive advantages.

👉 Follow our journey through all 15 insights in Ken Schwaber's white paper, revealing the enduring relevance of Scrum principles.

💬 Share your perspectives in the comments and remember to like and subscribe for more in-depth Scrum discussions. 🔔

🔗 Here is the original white paper: https://www.verheulconsultants.nl/ScrumIsHardandDisruptive.pdf

🔗 Join Ryan & Todd's Scrum.org course: https://buytickets.at/agileforhumansllc

Explore more:

📖 "Unlocking Business Agility with Evidence-Based Management: Satisfy Customers and Improve Organizational Effectiveness" on Amazon -- https://amzn.to/4690qJy

📖 "Fixing Your Scrum: Practical Solutions to Common Scrum Problems" on Amazon -- https://amzn.to/46dAQTC

✅ Subscribe to this channel for Agile, Scrum, and Kanban insights: https://www.youtube.com/agileforhumans?sub_confirmation=1

Learn more about your ad choices. Visit megaphone.fm/adchoices

  continue reading

673 episodi

Artwork
iconCondividi
 
Manage episode 413135368 series 2854678
Contenuto fornito da Agile for Humans, LLC, Agile for Humans, and LLC. Tutti i contenuti dei podcast, inclusi episodi, grafica e descrizioni dei podcast, vengono caricati e forniti direttamente da Agile for Humans, LLC, Agile for Humans, and LLC o dal partner della piattaforma podcast. Se ritieni che qualcuno stia utilizzando la tua opera protetta da copyright senza la tua autorizzazione, puoi seguire la procedura descritta qui https://it.player.fm/legal.

Ryan and Todd look back at a 2006 post by Ken Schwaber, which covers 15 ways Scrum is both hard and disruptive.

The tenth statement from Ken:

"Scrum is not a methodology that needs enhancing. That is how we got into trouble in the first place, thinking that the problem was not having a perfect methodology. Effort centers on the changes in the enterprise that is needed."

Scrum's Nature and Misunderstandings: The discussion emphasizes that Scrum is not a methodology needing enhancement, as attempting to perfect it led to initial troubles. It’s highlighted that Scrum is a framework, not a methodology, and should not be altered excessively.

Scrum's Simplicity and Accessibility: When Compared to more complex methodologies and frameworks, Scrum’s guide is concise (13 pages), making it easily understandable without the need for extensive training, unlike more elaborate methods that require significant learning and interpretation.

Adaptability and Contextual Use of Scrum: The speakers discuss the importance of adapting Scrum practices based on specific team and project contexts. They share personal experiences where certain practices were effective in one situation but not in another, illustrating Scrum’s flexibility and the need for situational awareness.

Evolution of the Scrum Framework: The evolution of Scrum is discussed, noting that over time, the framework has become more streamlined, with a focus on removing unnecessary elements rather than adding new ones. This evolution aims to prevent dogmatic adherence to processes and encourage teams to focus on the intent of each Scrum event.

Focus on Organizational Change Over Scrum Modification: The conversation shifts to the idea that efforts should be directed toward changing organizational structures and practices that hinder agility, rather than trying to improve Scrum itself. Emphasis is placed on overcoming organizational impediments to enhance the delivery of value to customers and gain competitive advantages.

👉 Follow our journey through all 15 insights in Ken Schwaber's white paper, revealing the enduring relevance of Scrum principles.

💬 Share your perspectives in the comments and remember to like and subscribe for more in-depth Scrum discussions. 🔔

🔗 Here is the original white paper: https://www.verheulconsultants.nl/ScrumIsHardandDisruptive.pdf

🔗 Join Ryan & Todd's Scrum.org course: https://buytickets.at/agileforhumansllc

Explore more:

📖 "Unlocking Business Agility with Evidence-Based Management: Satisfy Customers and Improve Organizational Effectiveness" on Amazon -- https://amzn.to/4690qJy

📖 "Fixing Your Scrum: Practical Solutions to Common Scrum Problems" on Amazon -- https://amzn.to/46dAQTC

✅ Subscribe to this channel for Agile, Scrum, and Kanban insights: https://www.youtube.com/agileforhumans?sub_confirmation=1

Learn more about your ad choices. Visit megaphone.fm/adchoices

  continue reading

673 episodi

Tutti gli episodi

×
 
Loading …

Benvenuto su Player FM!

Player FM ricerca sul web podcast di alta qualità che tu possa goderti adesso. È la migliore app di podcast e funziona su Android, iPhone e web. Registrati per sincronizzare le iscrizioni su tutti i tuoi dispositivi.

 

Guida rapida