The first thing I did when I started building Savoir was not to write code, but to plan my sprints with a tool called Codetree. I highly recommend them by the way, if you're looking for a good GitHub powered project management tool. I planned my entire feature set through epics, and I would break things down into smaller issues on a bi-weekly basis. I personally really like working in more structured environments.... - Source: dev.to / over 1 year ago

Very much agree, most projects I work on these days have components in multiple repositories and trying to coordinate work among them is challenging. We use Github Issues as a source of truth but have resorted to using third-party software on top of them to help get a bigger-picture view. Currently we're using Codetree: https://codetree.com/. - Source: Hacker News / almost 3 years ago

I started using Metroretro a few months ago and it's really nice, except for the ability to export retro items I think it covers everything you listed. Also it's free and it comes with some useful templates. Source: about 3 years ago

To improve the developer experience, I needed to understand the real problems the engineers were facing, so I scheduled a brainstorming meeting. In this meeting, I explained my project and shared a Metro Retro board to write down all issues our application had at that time, what was the bad DX we had, and doubts related to this application (e.g. How do we handle data fetching?; how do we handle error handling?;... - Source: dev.to / about 3 years ago