1 - Draft up a Gannt of the project, you can use Microsoft project, or Open project, but make sure you use a proper project management tool. Also, put everything into it - not just the software and trac items but everything - including all future plans, such as Dolphin 8. Include your resources and their availability too. Make sure that you map the dependencies correctly as well. You will easily be able to see what you can achieve, and where you are kidding yourself. Make sure that you put in realistic see more estimates for time, or the whole thing is worthless - if you ask a softie to give you an estimate - double it - and I'm not joking on this point. Assign the tasks to the resources, making sure that you take into account their strengths, weaknesses and availability. Also make sure you map out some realistic milestones these are what you should be pushing for. Forget putting an end date at this stage - just map everything out and see where the end date ends up - also realise that to bring this date forwards requires applying additional resources. I think that you will be very surprised at how long it will take to get to where you want to be when it is all formally laid out. And don;t forget to allow a little for contingency too.

2 - Maintain a 'shit list' - a list of issues - these are usually things that prevent you from achieving the tasks on the Gannt - the two work hand in hand - the shit list helps you to proritise what needs to happen. Each issue has a priority, a percentage finished, a due date and an assignee, This determines the day to day activities - once an item is finished it comes off of the list. If a new item get added with a higher priority - it gets precedence. Issue this to everyone so that everyone is aware of the current issues and what they are supposed to be working on. The shit list ideally applies to current tasks but may also have long term impact issues on there as well.