Artwork

Sisällön tarjoaa Agile for Humans, LLC, Agile for Humans, and LLC. Agile for Humans, LLC, Agile for Humans, and LLC tai sen podcast-alustan kumppani lataa ja toimittaa kaiken podcast-sisällön, mukaan lukien jaksot, grafiikat ja podcast-kuvaukset. Jos uskot jonkun käyttävän tekijänoikeudella suojattua teostasi ilman lupaasi, voit seurata tässä https://fi.player.fm/legal kuvattua prosessia.
Player FM - Podcast-sovellus
Siirry offline-tilaan Player FM avulla!

Scrum is Hard and Disruptive 12 - Maximize Value

9:30
 
Jaa
 

Manage episode 414060575 series 75660
Sisällön tarjoaa Agile for Humans, LLC, Agile for Humans, and LLC. Agile for Humans, LLC, Agile for Humans, and LLC tai sen podcast-alustan kumppani lataa ja toimittaa kaiken podcast-sisällön, mukaan lukien jaksot, grafiikat ja podcast-kuvaukset. Jos uskot jonkun käyttävän tekijänoikeudella suojattua teostasi ilman lupaasi, voit seurata tässä https://fi.player.fm/legal kuvattua prosessia.

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

The twelfth statement from Ken:

"Managing a release or project to deliver only the highest value functionality and not deliver the rest optimizes value [and] is the job of product management and customers."

The 12th episode of "Scrum is Hard and Disruptive" discusses the importance of delivering only high-value functionality in project management, emphasizing the role of product management and customer input.

The hosts, Todd and Ryan, stress the need for product owners to say "no" to unnecessary features, highlighting the importance of avoiding waste and focusing on what's truly needed.

They discuss using Evidence-Based Management (EBM) to validate the usefulness of features in production and advocate for objective decision-making in product development.

The episode touches on the customer's responsibility in the development process, encouraging their involvement and accountability in deciding the essential features.

The conversation also covers the importance of being ruthless in backlog management, akin to Steve Jobs with the iPhone, and the value of saying "not yet" to lower-priority items to maximize return on investment.

👉 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

714 jaksoa

Artwork
iconJaa
 
Manage episode 414060575 series 75660
Sisällön tarjoaa Agile for Humans, LLC, Agile for Humans, and LLC. Agile for Humans, LLC, Agile for Humans, and LLC tai sen podcast-alustan kumppani lataa ja toimittaa kaiken podcast-sisällön, mukaan lukien jaksot, grafiikat ja podcast-kuvaukset. Jos uskot jonkun käyttävän tekijänoikeudella suojattua teostasi ilman lupaasi, voit seurata tässä https://fi.player.fm/legal kuvattua prosessia.

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

The twelfth statement from Ken:

"Managing a release or project to deliver only the highest value functionality and not deliver the rest optimizes value [and] is the job of product management and customers."

The 12th episode of "Scrum is Hard and Disruptive" discusses the importance of delivering only high-value functionality in project management, emphasizing the role of product management and customer input.

The hosts, Todd and Ryan, stress the need for product owners to say "no" to unnecessary features, highlighting the importance of avoiding waste and focusing on what's truly needed.

They discuss using Evidence-Based Management (EBM) to validate the usefulness of features in production and advocate for objective decision-making in product development.

The episode touches on the customer's responsibility in the development process, encouraging their involvement and accountability in deciding the essential features.

The conversation also covers the importance of being ruthless in backlog management, akin to Steve Jobs with the iPhone, and the value of saying "not yet" to lower-priority items to maximize return on investment.

👉 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

714 jaksoa

All episodes

×
 
Loading …

Tervetuloa Player FM:n!

Player FM skannaa verkkoa löytääkseen korkealaatuisia podcasteja, joista voit nauttia juuri nyt. Se on paras podcast-sovellus ja toimii Androidilla, iPhonela, ja verkossa. Rekisteröidy sykronoidaksesi tilaukset laitteiden välillä.

 

Pikakäyttöopas