Maybe this is your problem. Trying to focus on one project while you have 3 on a board right in front of you at all times. Why three projects? Why not one? How about try just focusing on one? Surely there's one that's been up there the entire time, one that you feel is more significant than all the others.
I've come up with few ideas on how to stay focused based on my working methods. I too have just started working on my own project, it's my first that I've actually started, and I haven't yet finished it so feel free to take everything I say with a grain of salt.
I'm not sure if this is good advice but if you get an idea don't write it down (or record it for that matter), the reason I'm not sure it's good advice is I have bad habit of not recording any of my thoughts. I get new ideas for projects all the time but I treat them all as something passing and insignificant, no matter how great it appears it'll always sounds great the first time it strikes your mind. I still spend the whole day (or sometimes many days) thinking about it, that's unavoidable but I never write it down. The advantage of this is if it's not a good idea you'll probably never think of it again especially considering there's nothing you've created to remind you of it. If it is truly great idea than it'll come back to you and by means of something that exists in the real world, (thus justifying its significance) not something you've written down.
When it comes down planning. I would only do things on a week by week basis. Planning for a year long project just turns it into one big daunting task. Just set small goals for the end of the week then use that as springboard for the next task. I'm sure you know what you're working towards without planning it in its entirety. I find planning the project soon makes it boring to work on.
Work not to a planned schedule but to what you find to be the most interesting thing to work on at the time.
Also identify the core of you project. What is it what are most important things it needs to function. If you're building a wiki maybe the ability to create and edit pages should the first thing you create. After you've built the core it could very well be considered a finished project and be released tomorrow and than you can start working on additional features like user accounts and what not.
I guess what I'm saying is (and I tend to do this). It's waste of time work on a feature for an app when it isn't necessary for it to function. Spend less time thinking about all the things your project could do and spend more time working on what is necessary for your project to achieve its intended purpose.
I like to to remind myself that facebook took only 2 weeks to build, and it certainly wasn't the beast it is now when it first started. But considering that, if an experienced programmer took more than year to build web app they must certainly be wasting their time on something besides their regular work/social life, right?