What is personal project management?

Personal project management is how one person keeps track of the things they are building, fixing or finishing. A side project, a website, a product you run alone, a house you are slowly renovating. It borrows a few ideas from team project management and leaves the rest behind.

How it differs from team project management

Team tools solve coordination. Who does what, who approves it, who reports to whom. That is where the required fields, the roles, the sprints and the dashboards come from. They are there so a group of people can agree on the state of the work.

When you work alone, nobody needs a status report. You need to remember what is left, what you were in the middle of when you stopped, and what you are waiting for. That is a much smaller problem, and it deserves a much smaller tool.

What you actually need

• A list of projects. One per thing you want finished, so each has its own place.
• Tickets inside each project. One per problem or piece of work, with a short title.
• A number on every ticket. Then "ticket 12" means one thing, in your notes, your commits and your messages.
• A few statuses. Something like new, in progress, blocked and done. Enough to see what is moving.
• A thread on each ticket. What you tried and what you decided. You will read it again in three months.
• One way to mark what matters. A star is enough.

What you can skip

Story points, sprints, a due date on everything, Gantt charts, custom fields and workload views. They answer questions a team asks. If you notice that you spend more time keeping the system tidy than working on the projects, the system has grown too big.

A simple method that holds up

1. Make a project per outcome. "Launch the new site", not "Work".
2. Write a ticket the moment you notice something. A title and two lines. Do not polish it.
3. Keep one or two tickets in progress. Everything else waits as new.
4. Mark a ticket blocked with what you are waiting for. That is the one you come back to first.
5. Close what is done, and cancel what you will not do. A cancelled ticket keeps its history. A deleted one does not.
6. Once a week, open each project and read the open tickets. Star what matters this week.

Each step has its own guide: keeping a project list, prioritizing projects, managing several projects at once and the weekly review.

Where AI agents fit

More and more people build with an AI agent, such as Claude Code or another coding assistant. The agent finds bugs, finishes work, and needs somewhere to say so. A chat window forgets. A ticket does not.

Give the agent one project. Let it file a ticket per problem, write progress in the thread, mark a ticket blocked when it needs you, and done when the work is finished. You read, reply and decide. It stays personal project management: the agent is a helper, not a team. More in an AI agent for project management, when you are the whole team.

Choosing a tool

A few questions sort most tools quickly. The longer version is in how to choose personal project management tools.

• Can I add a ticket in a few seconds?
• Are there few enough fields that I actually fill them in?
• Can I see every project and what is open at a glance?
• Can an agent read and write one project without seeing the rest?
• Is it cheap enough that I never think about the cost?

Very Simple Projects is a simple personal project management app built around exactly this list: projects, numbered tickets, six statuses you can add to, a thread on every ticket, and room for your agents. It costs $0.99 a month, and the first month is free.