Agile for Humans with Ryan Ripley and Todd Miller Agile for Humans, LLC

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

🌐 Connect with Agile for Humans:

📘 Website - https://agileforhumans.com/


🐦 Twitter - https://twitter.com/agileforhumans


🔗 LinkedIn - https://www.linkedin.com/company/agile-for-humans-llc


🔍 The Evidence-Based Company - https://theevidencebasedcompany.com/


📧 Email - ryan@agileforhumans.com


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

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

Jenny Tarwater shares her journey into Scrum during an episode of "Becoming a Scrum Master" hosted by Ryan Ripley. She recalls her initial struggles at a large telecommunication company, where her early approach nearly led to her dismissal. Discovering a book on Scrum and Agile, she began applying these methodologies, transforming chaos into order with seven teams and exceeding stakeholder expectations within three sprints.

Tarwater emphasizes the importance of collaboration and listening. She recounts a pivotal moment in a coaching class when she learned the value of not just being an expert but also understanding the perspectives of those within the organization. This experience shaped her approach to Scrum, highlighting the necessity of teamwork and context.

Her perspective on the Scrum Master role evolved over time, and she stressed that there is no one-size-fits-all approach. Different organizations have varying needs, such as predictability, innovation, or quality, which require tailored approaches. She notes the challenge of adapting to other organizational structures and understanding each organization's problems.

Tarwater advises aspiring Scrum Masters to prioritize continual learning and listening. She emphasizes the ever-evolving nature of knowledge in the field, suggesting that one should never stop learning and adapting.

She recommends two books: "The Five Dysfunctions of a Team" for its insights into team dynamics and another unnamed but highly recommended book for Scrum Masters.

🔔 Stay tuned for more episodes filled with expert knowledge and intriguing discussions. We encourage you to share your thoughts and questions in the comments below. Your input is valuable to our community, and we often feature your inquiries in our future videos!

👍 Found this episode enlightening? Please LIKE and SHARE it with your network to spread the knowledge!

🔗 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

🌐 Connect with Agile for Humans:

📘 Website - https://agileforhumans.com/


🐦 Twitter - https://twitter.com/agileforhumans


🔗 LinkedIn - https://www.linkedin.com/company/agile-for-humans-llc


🔍 The Evidence-Based Company - https://theevidencebasedcompany.com/


📧 Email - ryan@agileforhumans.com


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

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

🌐 Connect with Agile for Humans:

📘 Website - https://agileforhumans.com/


🐦 Twitter - https://twitter.com/agileforhumans


🔗 LinkedIn - https://www.linkedin.com/company/agile-for-humans-llc


🔍 The Evidence-Based Company - https://theevidencebasedcompany.com/


📧 Email - ryan@agileforhumans.com


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

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

🌐 Connect with Agile for Humans:

📘 Website - https://agileforhumans.com/


🐦 Twitter - https://twitter.com/agileforhumans


🔗 LinkedIn - https://www.linkedin.com/company/agile-for-humans-llc


🔍 The Evidence-Based Company - https://theevidencebasedcompany.com/


📧 Email - ryan@agileforhumans.com


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

📖 "Unlocking Business Agility with Evidence-Based Management: Satisfy Customers and Improve Organizational Effectiveness" on Amazon -- https://amzn.to/4690qJy
Ryan and Todd, along with Patricia Kong and Kurt Bidner, released a new book, "Unlocking Business Agility with Evidence-Based Management" (EBM), on October 31st. This book encapsulates over 10 years of their combined experience in EBM.
The book, which spans eight chapters and is 166 pages long, covers EBM at various levels, including portfolio, project, and organizational levels. It aims to provide new theories and novel ideas about what EBM can offer organizations.
The authors expressed their enthusiasm for the book's physical publication and discussed how it incorporates numerous real-life stories and experiences. They aim to clarify misconceptions about EBM and further its application in the business world.
Ryan and Todd reflected on the unique aspects of writing this book compared to their previous work, "Fixing Your Scrum." They highlighted that "Unlocking Business Agility with EBM" offers fresh insights and elaborations on EBM rather than following an established path.
The book is available in both eBook and paperback formats. The authors encourage readers to check it out, leave reviews, and share their thoughts. They also invite discussions and questions about EBM, intending to continue creating content and engaging with the community.
🔗 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

🌐 Connect with Agile for Humans:

📘 Website - https://agileforhumans.com/


🐦 Twitter - https://twitter.com/agileforhumans


🔗 LinkedIn - https://www.linkedin.com/company/agile-for-humans-llc


🔍 The Evidence-Based Company - https://theevidencebasedcompany.com/


📧 Email - ryan@agileforhumans.com



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

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

The ninth statement from Ken:

"The focus of using Scrum is the change from old habits to new ways of doing business. Scrum is not implemented or rolled-out as a process; it is used to foment change. "

Podcast Focus: The podcast "Scrum is Hard and Disruptive" by professional scrum trainers Todd Miller and Ryan Ripley explores a white paper published by Ken Schwaber, co-creator of Scrum, in 2006. They assess 15 statements about Scrum to see if they remain relevant 17 years later.

Scrum's Purpose: The primary focus of Scrum is to facilitate a transition from old habits to new ways of conducting business. It is emphasized that Scrum should not just be implemented as a new process but should be used to instigate significant organizational change.

Common Misconceptions: There's a critique of how many organizations misunderstand Scrum, often using it merely as a new process rather than a tool for real change. This leads to maintaining old habits instead of adopting genuinely new ways of doing business.

Technology and Business Integration: A key point discussed is the need to stop viewing IT departments as separate from the rest of the business. In the modern world, where technology is central, IT should be integrated into the core business processes.

Challenges of Implementing Scrum: The podcast underscores that implementing Scrum can be challenging and disruptive, as it requires significant changes in organizational behavior and mindset. The goal is to move beyond superficial adoption of Scrum as a process to deeply ingrained changes in how businesses operate.

👉 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

🌐 Connect with Agile for Humans:

📘 Website - https://agileforhumans.com/


🐦 Twitter - https://twitter.com/agileforhumans


🔗 LinkedIn - https://www.linkedin.com/company/agile-for-humans-llc


🔍 The Evidence-Based Company - https://theevidencebasedcompany.com/


📧 Email - ryan@agileforhumans.com


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