Creating a Product Backlog of User Stories for Agile Development using GitHub

We create a list of User Stories - i.e. a list of features - for a product or project that we are developing. We do this using GitHub's built in Issues tracker, making sure to label our User Stories nicely so we can find them easily later one we have other kinds of Issues mixed in.

[renem]

I like the scope of how you wrote your user story. It is not too broad and it is not too narrow.

[victoria-exito]

Excellent! Thank you so much. You have educated me and my group (6 more people). God bless you.

[marsdwarf]

Loved it, thanks for making this series!

[Zikos]

Isn't it better to set user stories as milestones so that the tasks can be converted to issues without being mixed up with the user stories (as issues)?

[GretSeat]

Gotta love how none of the terminology of "Scrum" and "Agile" flow together.

Spike, Task, User Stories, Product Backlog, Scrum...

Did no one take the time to actually think of names that work? "Meeting" "Task" "Wanted Features" "Internal Work" anything like that... like come on. I listen to people talk about scrum and it's just so confusing because none of the terms make sense.