The tool should be shaped around the team's best way of working. The problem is that everyone thinks project/backlog organization is the silver bullet to getti

The tool should be shaped around the team's best way of working. The problem is that everyone thinks project/backlog organization is the silver bullet to getting things done. It's not. What they don't realize is that too much process or too little process can make or break team's autonomy. I like GitHub projects. It is simple, Airtable/Notion inspired, and makes it very easy to see a backlog like a spreadsheet. The views are especially helpful for different projects, statuses, and dependencies. The best part about it? It's native to teams who work exclusively in GitHub. I work on a suite of GitHub OSS repos, and this tool alone looks extremely promising. Even using the beta for a few months now has helped me put everything in one place with many views instead of having to use alternatives like ZenHub. I do everything in the open and need solutions that can be transparent with the very communities I build for. This is looking good despite the bugs like editing titles in projects beta changes the issue's title on keystroke. It makes it quite easy to quickly create new issues and manage them from a single screen on the web. Big fan so far.