Like with DesignJoy, only one active task at a time. We use GitHub to manage almost everything. CI/CD is configured so deployment is a breeze. Each issue is a task. We use GitHub projects (kanban-style board) to manage the backlog and task stages (todo, in-progress, done). Big projects are broken into milestones and stages; each milestone or stage corresponds to one month of work.
Another benefit I see is that the costs is clear to the customer; he can budget properly and may pause things as needed. I also don’t need to spend time preparing estimates/quotes (which I’m not good at, and I don’t enjoy doing).
I find this works well for people looking to build MVPs or small to medium web applications. There are no long-term contracts or strict project scopes.
What do you think? Any feedback and discussion is welcome.
aristofun•6mo ago
But you're expected to build a blogging software only once, and any fixes/bugs are unexpected in scope and complexity.
Unless you take advantage of your customer (nobody else can fix that complex system that you left him with) - it doesn't look sustainable to me.
gerardojbaez•6mo ago
There are instances where the customer already know what he wants, could be typical maintenance, bug fixing, etc... those things can be added to a task queue, details are agreed and work is performed, without preparing quotes every time for each task
For example, I would only use something like this if I can automate as much as possible using CI/CD, etc
aristofun•6mo ago
If you can predict how much and what issues need to be solved - why haven’t you already automated it??