4 ms·
My team can't move off of using GitHub for project management
We tried different PM software but always end up going back to just using Github issues/projects.
The main reasons are:
1. We always go to Github anyways. Might as well have the tasks written there.
2. Other software are just very complicated. They're all overkill with UI that is too fancy.
Anyone else stuck using Github for their dev team? Are we missing out on a "productivity" boost by not trying harder to use a fancier PM software?
- linkdd 5y agoAt my company, we use Trello and Pull Requests massively, Issues not so much.
- __warlord__ 5y agoWe do the same at $CURRENT_TEAM and it works just fine. Kanban + Issues are what we currently need, is easy to reason with and we don't need extra people to manage it.
- nivertech 5y agoWhat's wrong with Github? IMO being able to do everything from Github is a huge advantage, not a disadvantage. SW development is already hard enough, we had to use tens of tools even for a simple project, so if it possible to avoid new tools/services, or use a mainstream one, even if it's not as fully-featured as a specialized tool. Occam's basic rule was "Thou shalt not multiply extra entities unnecessarily". Everyone already has a Github account. You can add any external collaborator with a single click. Everything (issues, PR, releases, etc.) is super-customizable with templates. You can do any SDLC or Project Management with Github alone. - You can do Kanban with new Github Projects. - You can use TODO task lists and convert them to Github issues when needed. - I even implemented Shape Up method in Github with scopes and tasks[1] [1] https://basecamp.com/shapeup/3.3-chapter-12 https://basecamp.com/shapeup/3.3-chapter-12