How I manage all my projects

Recently I wrote a post on my blog about how I've kept failing for years to finish any of my side projects.

Read the post here: https://codeartisan.org/2018/11/07/unfinished-side-projects/

One of the key factors to this never ending story is over management, and mvps managed like they were a part of a multi million enterprise company. This has lead me to switch over to Workflowy which I've used for a good while already for other things. I ported my best side project ideas from memory, thinking that the ones I don't even remember probably isn't even worth my focus at this point.

So after some tinkering and gathering a bit of inspiration around the web I've come up with something I would consider a fairly solid approach to manage my projects, and I figured I should also share it here. Hopefully it'll be helpful and can at least provide inspiration to others in the same situation, or those of you who's just looking for a new way to handle this :P

One of the key features with this setup is that it splits the lists into three groups.

• launched - holds projects that has reached mvp and been released to the public
• current - is the project that has the main focus at this point
• queue - can be seen as a brainstorming list

This is the link to the template that can be imported into your own workflowy account if you have one :)

https://beta.workflowy.com/s/projects-management/a7dbOKhThVmkozlI

The projects inside launched and current can look a bit overwhelming at first, but the structure is actually really simple once you know the idea behind each sub list. I'll give them a quick introduction.

• internal - only you/team should see this list
  • research - any material you find that can be used to benefit your project
  • feature tracker - project features
    • pitch - ideas you get to new features, new stuff to existing features, etc
    • queue - features that will become a part of your project
    • requests & suggestions - stuff that comes as feedback from users, etc
  • development tracker - task manager
  • bug tracker - bug manager
  • release plan - plan each release as a sprint adding which features, tasks, bugs, etc that will be a part of the next release
  • work log - write down what has been done on each day
• external - these lists can be shared to your users to keep them in the loop
  • AppName Release Notes
  • AppName Road Map
  • AppName What's Coming

This template is based on my web development projects, but it has also taken inspiration from this post

https://blog.workflowy.com/2012/08/29/how-we-use-tags/

... and the workflowy release notes which you see here

https://workflowy.com/s/workflowy-release-notes/aaEJNvR2y2xlu3s1

If you have any questions about this, I would be more than happy to answer them. I would also appreciate feedback and suggestions for improvements, etc!