YDS: Help! A Scrum Developer Keeps Taking the Easy Work!

Help! A Scrum Developer Keeps Taking the Easy Work! Let's explore the options this situation presents. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley.

What do you think? Let us know in the comments!

Buy Fixing Your Scrum: Practical Solutions to Common Scrum Problems -

Join Ryan and Todd in a Professional Scrum Master course:

And make sure you subscribe to the channel!

DISCLAIMER: Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide, I may receive a small commission. There is no additional charge for you! Thank you for supporting the channel so we can continue to provide you with free content each week!

FTC DISCLAIMER: This video is not sponsored by anyone.

Sharing Scrum knowledge to help you grow as a Scrum Practitioner and to solve complex problems.

#scrum #agile #scrummaster

[MarkBurville]

Love it, great question, excellent insights, "all for one, one for all" One Team, thanks RR+TM.

[itspiikaa]

Great episode ! Thank you guys !
Please add this to your questions' backlog : how does a scrum master contribute in the release planning and budgeting ?

[MrAkkim]

This topic touches on a concern any new team that is in its formation stage could or is likely to experience. I appreciate the examples offered by RR & TM around this topic. Very helpful.

[osnyzinho]

Hi Ryan and Todd! love your show! One question: I am a SM in a huge company and in the developer's team there are some (not all) third party people. They want to work by their own, not considering my warnings to help each other, keep WIP low, Little's Law and the classical moto "stop starting, start finishing". How should I handle third party fellows in the developer's team? How engage them to understand the importance to work together (Scrum values), regardless the fact them work in another company?

[Timaz]

Hello, guys! Loved the latest show 😊 My ask would be to bring key changes from Scrum Guide 2020, and talk through them.

Thanks

[Batlas]

Coming from software, the concept of all devs own all the work is hard to grasp. Like I understand it from a fundamental level, but in your example, you mention devs working on items together.. e.g. something akin to paired programming, which works for helping one dev understand something, but isn't something really scalable. You run into a lot of issues when committing code that is touched by multiple people. How do you recommend "sharing" tickets for lack of a better word? (Also, I realize this is a 2 year old topic, so could have been answered in future question, but I only recently found you guys. Love the content)