aupright's comments

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.

Hey stblack - we have that same feature in ZenHub. Feel free to check out https://www.zenhub.com/product

Thanks for this feedback ndarilek, I appreciate you taking the time to call it out. Candidly, you're absolutely right—this is an area that we need to be more considerate of as we continue to scale and I apologize that it lead to a less than ideal first experience for you.

We've started down the path of completing an accessibility audit, and are hoping to use those findings to drive highest priority areas of improvement moving forward. While I'm not certain on timelines , I definitely think there could be an opportunity to engage moving forward and would be happy to keep you involved if you're interested.

If you'd like, you can reach me directly [email protected]

ZenHub Co-founder here. On behalf of the ZenHub team we wanted to take a moment to acknowledge all of the incredible work by the Waffle.io team (past and present) over the past four years. We have nothing but respect for the team and want to wish them all the best in their next adventures!

While Waffle and ZenHub are competing products in a way, we both share similar views on the importance of project management being developer-first. It's been a fun journey building in the space along side Waffle and we continue to remain excited about the future of project management in GitHub!

If anyone is interested, you can check out ZenHub here: https://www.zenhub.com/

ZenHub cofounder here - some really good points in this response, and it didn't sound like you were throwing project management methodology to the wind at all! For a lot of teams we work with, simply getting these insights is half the battle. A team shouldn't expect a tool to solve their problems, in the vast majority of cases it comes down to people and processes. We hope that these reports can drive the types of insights that are catalysts for those larger changes.

Pricing for the marketplace was completely left up to the discretion of the integrators. There's a number of integrations (ZenHub included) that are the same price whether you buy through the marketplace or through company websites :)

Hey, I'm one of the cofounders of ZenHub - we're another popular integration on the marketplace and also sell our product separately through our own website.

From a company/integration on the marketplace, the marketplace has been great in terms of building awareness and exposure. Can confidently say that we've been able to reach new users and customers that we wouldn't have otherwise had if we weren't on the marketplace.

From the perspective of a GitHub user/team, lots of teams prefer to consolidate everything together on a single invoice. If you're using GitHub for software development, you're almost certainly going to need a CI/CD tool and PM tool, so why not bring everything together on a single bill?