5 ms·

Would anyone recommend this for a solo developer? Personally I'm a fan of a mix of physical sticky notes and Trello, but I'm always open to new ideas. I could

by bdibs 7y ago

Would anyone recommend this for a solo developer? Personally I'm a fan of a mix of physical sticky notes and Trello, but I'm always open to new ideas. I could see this being more of a hassle than I'd like, but I could be wrong.

TheChaplain 7y ago
It seems like it's a book, not an actual tool. If Trello or sticky notes works for you, then it's the best option.
an_opabinia 7y ago
As a solo developer, you should only be doing the things you are really excited to do, not waging psychological warfare against yourself.
- turk73 7y ago
  I don't see how this is at all realistic. If it were up to me, I would just do all POC work and nothing else. But there are bills that have to be paid, so...
- keyle 7y ago
  Ahah well written. And you're 100% on point.
chucky_z 7y ago
Try out https://gingko.io/ https://gingko.io/ When I was working solo it was really good, I used the top-level as a daily log and could easily tell what to continue working on, and what my major issues were each day. (I used the other version at https://gingkoapp.com/ https://gingkoapp.com/)
- personjerry 7y ago
  BTW the scientific spelling is ginkgo :)
erikig 7y ago
I think it is helpful to distinguish between tools and techniques. Trello and Sticky Notes are tools. GTD, Kanban, Pomodoro etc are productivity management techniques/methods. I find it helpful to first pick the technique/method then figure out how to use the tools. It is similar to programming languages and IDEs. First pick the programming language (methodology) then pick the tool (IDE). Good tools work with multiple methodologies.
- jdmichal 7y ago
  Nitpick: I might argue that at its core, Kanban is a visualization tool. I think "agile Kanban for software" has some prescribed methodologies, but you're also free to tell them where to shove it and still call what you're doing Kanban as long as you have a board.
wpietri 7y ago
I think of kanban mainly as an analytical model for things represented in sticky notes or trello cards. The main things I think you'd find useful are a) making sure you represent your actual workflow, and b) setting WIP limits. You can see a (team) implementation of this using index cards here: http://williampietri.com/writing/2015/the-big-board/ http://williampietri.com/writing/2015/the-big-board/

by bdibs 7y ago

TheChaplain 7y ago

It seems like it's a book, not an actual tool. If Trello or sticky notes works for you, then it's the best option.

an_opabinia 7y ago

As a solo developer, you should only be doing the things you are really excited to do, not waging psychological warfare against yourself.

turk73 7y ago
I don't see how this is at all realistic. If it were up to me, I would just do all POC work and nothing else. But there are bills that have to be paid, so...
keyle 7y ago
Ahah well written. And you're 100% on point.

chucky_z 7y ago

Try out https://gingko.io/ https://gingko.io/ When I was working solo it was really good, I used the top-level as a daily log and could easily tell what to continue working on, and what my major issues were each day. (I used the other version at https://gingkoapp.com/ https://gingkoapp.com/)

personjerry 7y ago
BTW the scientific spelling is ginkgo :)

erikig 7y ago

I think it is helpful to distinguish between tools and techniques. Trello and Sticky Notes are tools. GTD, Kanban, Pomodoro etc are productivity management techniques/methods. I find it helpful to first pick the technique/method then figure out how to use the tools. It is similar to programming languages and IDEs. First pick the programming language (methodology) then pick the tool (IDE). Good tools work with multiple methodologies.

jdmichal 7y ago
Nitpick: I might argue that at its core, Kanban is a visualization tool. I think "agile Kanban for software" has some prescribed methodologies, but you're also free to tell them where to shove it and still call what you're doing Kanban as long as you have a board.

wpietri 7y ago

I think of kanban mainly as an analytical model for things represented in sticky notes or trello cards. The main things I think you'd find useful are a) making sure you represent your actual workflow, and b) setting WIP limits. You can see a (team) implementation of this using index cards here: http://williampietri.com/writing/2015/the-big-board/ http://williampietri.com/writing/2015/the-big-board/