Artwork

Contenido proporcionado por Agile for Humans, LLC, Agile for Humans, and LLC. Todo el contenido del podcast, incluidos episodios, gráficos y descripciones de podcast, lo carga y proporciona directamente Agile for Humans, LLC, Agile for Humans, and LLC o su socio de plataforma de podcast. Si cree que alguien está utilizando su trabajo protegido por derechos de autor sin su permiso, puede seguir el proceso descrito aquí https://es.player.fm/legal.
Player FM : aplicación de podcast
¡Desconecta con la aplicación Player FM !

Scrum is Hard and Disruptive 11 - Scrum is Harder than Waterfall

8:18
 
Compartir
 

Manage episode 413391456 series 2854678
Contenido proporcionado por Agile for Humans, LLC, Agile for Humans, and LLC. Todo el contenido del podcast, incluidos episodios, gráficos y descripciones de podcast, lo carga y proporciona directamente Agile for Humans, LLC, Agile for Humans, and LLC o su socio de plataforma de podcast. Si cree que alguien está utilizando su trabajo protegido por derechos de autor sin su permiso, puede seguir el proceso descrito aquí https://es.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 eleventh statement from Ken:

"Iterative, incremental development is much harder than waterfall development; everything that was hard in waterfall engineering practices now has to be done every iteration, which is incredibly hard. It is not impossible, but has to be worked toward over time."

Iterative and incremental development in Scrum is more challenging than traditional waterfall development, requiring constant attention to engineering practices and frequent iterations.

Extensive upfront design and architecture planning in waterfall development is believed to reduce future risks. However, software development often leads to outdated designs as customer needs and market conditions change over time.

Scrum emphasizes quick decision-making on basic architecture, like frameworks and databases, while building the product incrementally. It demands disciplined, professional attention to ongoing architectural and design decisions in response to evolving customer demands.

The Scrum approach challenges traditional development models like waterfall, where work often expands to fill the allotted time, leading to over-engineered solutions. Scrum requires a shift in mindset, focusing more on doing and building features rather than extensive planning and discussion.

Adopting Scrum effectively requires gradual, sustained effort to improve engineering practices and architecture. Teams and organizations need to develop this skill set over time, including a solid understanding of their definition of "done" to reflect the maturity of their Scrum implementation.

👉 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

671 episodios

Artwork
iconCompartir
 
Manage episode 413391456 series 2854678
Contenido proporcionado por Agile for Humans, LLC, Agile for Humans, and LLC. Todo el contenido del podcast, incluidos episodios, gráficos y descripciones de podcast, lo carga y proporciona directamente Agile for Humans, LLC, Agile for Humans, and LLC o su socio de plataforma de podcast. Si cree que alguien está utilizando su trabajo protegido por derechos de autor sin su permiso, puede seguir el proceso descrito aquí https://es.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 eleventh statement from Ken:

"Iterative, incremental development is much harder than waterfall development; everything that was hard in waterfall engineering practices now has to be done every iteration, which is incredibly hard. It is not impossible, but has to be worked toward over time."

Iterative and incremental development in Scrum is more challenging than traditional waterfall development, requiring constant attention to engineering practices and frequent iterations.

Extensive upfront design and architecture planning in waterfall development is believed to reduce future risks. However, software development often leads to outdated designs as customer needs and market conditions change over time.

Scrum emphasizes quick decision-making on basic architecture, like frameworks and databases, while building the product incrementally. It demands disciplined, professional attention to ongoing architectural and design decisions in response to evolving customer demands.

The Scrum approach challenges traditional development models like waterfall, where work often expands to fill the allotted time, leading to over-engineered solutions. Scrum requires a shift in mindset, focusing more on doing and building features rather than extensive planning and discussion.

Adopting Scrum effectively requires gradual, sustained effort to improve engineering practices and architecture. Teams and organizations need to develop this skill set over time, including a solid understanding of their definition of "done" to reflect the maturity of their Scrum implementation.

👉 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

671 episodios

Todos los episodios

×
 
Loading …

Bienvenido a Player FM!

Player FM está escaneando la web en busca de podcasts de alta calidad para que los disfrutes en este momento. Es la mejor aplicación de podcast y funciona en Android, iPhone y la web. Regístrate para sincronizar suscripciones a través de dispositivos.

 

Guia de referencia rapida