YDS: Who Writes User Stories on a Scrum Team?

Who writes the user stories on a Scrum Team? 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

[g-ronnmendoza]

Can you have an episode that describes how to organize the product backlog items such as Epic, Features, Stories? Thanks in advance.

[rajkumarmfsr]

Thanks Todd and Ryan. Awesome content.

[veccher]

Talking about storys, we used the format "as <Who/Persona> i want <Feature> to achieve <goal>", at first, i personally loved the approach since it forced us to think about who will benefit from the feature, and what goal we want to achieve, and not only the feature. The user/persona is usefull to see who may be invited to the review, the goal is usefull to understand why we're doing this and what we really need to achieve, but most of the time, we needed to talk about the feature, and having this format was actually confusing, the three informations were in the title, but it made it harder to us to easily look at the PBI and understand what it's about, too much information on the title, led us to spend to much time to look for the PBIs we wanted, so now we started putting the impacted stakeholders/personas in a specific field inside the PBI, the goal is described usually in the feature/epic (azure hierarchy) level, and our base levels PBI's titles are just a simple description of the desired functionality. There's a bonus, letting the stakeholder inside a dedicated field make it easier to us to generate statistics about who is more impacted by our releases.

[mohammadesmaeilpedaran]

Thanks for your perfect podcast, I think it's time for having another Fixing your Kanban podcast

[franknyantekyi]

@agileforhumans In your experience what are you expectation for a scrum master 30, 60, 90 days of joining a new team?

[MarkBurville]

Excellent question, perfect 20/20 response. Friyay RR TM.

[sachu]

If not user story, then what are the other ways in which Product Backlog Item can be captured?

[vikassalunkhe]

Few teams expect SM creates US/Tasks for them and update each comment on it in Jira.

[dragonlordship]

Please explain that why it is called stories ? Not work items or artifacts!!!

[opmdevil]

As a product owner I want that the team will write user stories so that I can prioritize the backlog with all relevant information at any given time.

[ryanceasarborromeo]

In the real world, SM is the one getting sandwich. Hahaha. Especially if the PO thinks the SM is his or her secretary.

[kensaiyeahyeah]

What are you drinking Todd? Scrum juice? 😀