As an indie hacker, do you follow Agile or any other methodology to build your product?

You don't really need to go behind agile as such unless you have big projects to handle and big teams will be working on it.

Agile is more useful to break your projects into epics and then into smaller tasks/subtasks where each team member can work on a task(s). The beauty of agile is that it makes tracking these tasks very easy.

For your need, google sheet might be perfect. You can maybe upgrade to trello if you have more people working in the team and they need to be notified of task updates, etc.

For even bigger projects and teams, I am really happy with Codegiant.io (it is by a fellow indie hacker @rishikmathur )

I have everything in a Notion board called Bugs n Features. I work on them almost daily at this point. I made a short video here...

https://www.youtube.com/watch?v=QGkEQhNXi98

Agile is a framework/philosophy while Scrum/Kanban/XP (just to name some) are methodologies. :)

I do use Lean/Agile philosophy applying the Kanban method both at work and when working at home on my side projects.

The best approach is to have a board (Kanban board) to visualize your tasks.

I prefer using a Kanban tool (rather than spreadsheet/notebook), which centralizes all of my email accounts, events, meetings, to-do lists into one place. So I don't need to switch between many apps. It's time wasting.

One of the most famous tool is Trello.

Of course, since I am the co-founder of Flow-e, I use Flow-e (and because this is the only one tool to solve my problems with workflow visualization - https://flow-e.com).

I do one-week sprints tracked in my notebook. My long-range goals span about ten weeks, which I find is a good length of time for side projects.

I used to keep things on trello, but I find keeping it on paper helps keep me in offline work mode (i.e. away from digital distractions).

I don't use a board because I don't need to communicate stuff.
I use BitBucket for private version control so use their issue tracker heavily. That gives me short links I can paste into other docs including their wiki.

My process is very iterative and driven by solving user stories using the "Jobs to be done" approach (get a great book for free from https://www.intercom.com/books/jobs-to-be-done).

When I get stuck on things, I try to break features and tasks down into even smaller issues so I can mark some progress. I have found one of the biggest ways to stall is that I don't have something small on which I can make progress.

In terms of product design, I think literally "out loud" a lot - I save the recordings in Evernote and transcribe them by hand at least a day later. That gives me a second look at the idea.

I usually run with a long term ToDo list which covers all the main topics of the project and then a short term ToDo list, which is basically one point from the long term todo list broken down into small pieces. Sometimes these points on the small list take a few hours to implement.

It depends on what you mean. I break things down into projects + milestones/sprints. I have to.

1. OCD,

and more importantly
2) time management. I have a family, and limited time, so I need to break things down into small workable pieces in order to make any progress.

I recently started using notion.so to collaborate with a friend on a product. It's very similar to trello but with extra sections to enter notes/documentation.

Thinking about it, I do work in an agile manner. I essentially have a board where I move items from not started/in progress/completed as I progress through tasks.

Hi. I use trello and sprints. I have four categories, current, seccond, 3rd and backlog, with all my items and I rearrange them based on what I am looking to achieve. I try not to add anything to my current sprint before it ends.