aupright

Did your team settle on using something else instead, or have you just given up on the idea of estimating altogether?

What did you find hardest about coming up with estimates? Was it having a baseline to compare work to?

Story point estimation seems like a really popular approach to sizing work and getting to alignment on complexity. Curious to hear from teams that have had either a positive or negative experience with estimation.

If you're looking for agile power-ups to GitHub Issues, there's a few great options in the ecosystem. Check out ZenHub if you're looking for things like issue dependencies, epics, multi-repo boards, etc. and want to stay in GitHub. GitKraken Boards are also a great option and integrate with their Git GUI.

For those worried about the data being used maliciously, it looks like most of the metrics they'll be introducing are focused around things that can actually help unblock teams and aren't focused on individual contributors. Eg. distribution of code reviews across team members for better load balancing, average code review turnaround times across the team.

It also looks like you'll be able to proactively set goals for some of these insights as well to improve over time. I can see where this can go awry, but optimistically this should help teams better measure and improve their process!

Looks like it's meant to be a substitute for Jira rather than an integration.