Is a project management tool really necessary when a team consists of only one person?
by•
At the very least, it was something I didn't need when I was doing a project alone. Most of my projects are just me. Only the client's team used such a tool, since there were 5 or more people working simultaneously and, starting from a free board tool, they had to track the hours of outside contractors too.
Later on, I found out that I do need it too. Now I have more than 30 projects going with AI agents and honestly can't keep track of where each one is, so all of it goes on a kanban board, the same way the client's team does it. My daughter's homework and class schedule are on a board as well.
How many people were on your team when you started using one?
10 views
Replies
Still one person, and still no board. Each project has a roadmap file in the repo with a tag for "decided but not coded yet", so the agents read the same list I do. 30 projects would break that, though. That's where a board starts to make sense.
@wwenioaguiar Yeah, that's about where it broke for me. With 30+ going I can't hold it in my head anymore, so every project sits on one board and I can see where each agent is at a glance.
No board here either, a handful of repos and a lot of parallel agent sessions. What works for me is that the repo is the board: every finished stage gets committed and pushed right away, so git log is the "done" column, and a dated research folder holds the "what to build next" list with the reasons. The agents read both before they start. Where it falls apart is anything outside code, like store reviews, ads tests, a support reply I promised. Those slip because no file in a repo reminds me. So maybe the line isn't team size, it's how much of the work lives outside the code.
@gbasovv That's a good way to put it. The repo works as a board for code, but the stuff I promise outside the repo just slips. For me that's what pushed everything onto one kanban board. With 30+ projects going I couldn't hold them in my head anymore.