Planning at Scale with Issues - GitHub Universe 2021

Presented by Mario Rodriguez, VP, Product Management
As always, feel free to leave us a comment below and don't forget to subscribe: bit.ly/subgithub
Thanks!
Connect with us.
Facebook:
Twitter: / github
LinkedIn: / github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to github.com

[@bergerblancsuisse.]

Showcasing an agile workflow would really help sell this.

[@DamianBrady]

That's a really good idea. Hypothetically, would a "Here's how to implement Scrum with GitHub Issues" walkthrough be useful?

[@bergerblancsuisse.]

@@DamianBrady 100% and appreciated. It would be a fantastic starting point for migration and to show additional benefits moving agile workflows to GitHub Issues where code is located rather than other 3rd party tools.

[@Scoutjoe108]

I would love to see GitHub decide whether it wants to appeal to developers or enterprises. I know that GitHub has locked in on the idea that every planning item is an "issue". Given that the original focus of GitHub was developers then calling everything an issue makes sense. If you're going to become an enterprise planning tool, you're going to have to let go of everything being an issue. As I see it the "issue" is that you can't plan issues at scale because an issue isn't an Epic, an issue isn't a feature, a user story isn't an issue and if you're going to be flexible and accommodate other than agile planning a requirement and an issue aren't the same thing. Call them planning items, or work, or an idea but issues are issues and nothing else. When can we begin seeing work hierarchies; Epics decomposed to features and features decomposed to product backlog items with a traceability view?

[@erdemgsu]

Great session, awesome to see the evolution of GitHub Issues!

[@tedmoyses2942]

Nice to see innovation on issues! I wonder if Jira will be worried? Lol

[@sergelachapelle7992]

They should... 😁

[@KarthickSelv]

I do use Githib issues for project management

[@mystic_monk55]

Can't we have fixed header 🙂

[@KlMJONG-UN]

Pls have notifications for people who reply to your fix on issues 🙂 i have to do Author:myname to find it

[@marcellosharp]

Jira who?

[@frozenintime]

I'd stick with jira. It still has the smoothest planning systems and metrics built into it without being locked to any repository vendor.
Plus kanban imo isn't pleasant for an at scale project.