Are you writing this on your own? If you are on your own then any methodology will probably be inappropriate. Most methodologies expend most of their energy (and rightly so) coordinating communication between team members, stake holders.
For my solo projects I just hack. I would recommend the following highlights (for me personally). On your solo project you can now DO all TODOs. Litter the code base with those little buggers. TODOs can make a very effective replacement (or supplement) to bug/task tracking systems.
Make sure you have a fast build. I will make the assumption that you are writing unit tests and say, optimise those so they whizz by after new feature is coded up. When they get slow, refactor them like a monster until they are fast again.
All in all (and the list above is really specific to me) you can now optimize for your development pleasure. Do this! That is the best methodology I know.
For my solo projects I just hack. I would recommend the following highlights (for me personally). On your solo project you can now DO all TODOs. Litter the code base with those little buggers. TODOs can make a very effective replacement (or supplement) to bug/task tracking systems.
Make sure you have a fast build. I will make the assumption that you are writing unit tests and say, optimise those so they whizz by after new feature is coded up. When they get slow, refactor them like a monster until they are fast again.
All in all (and the list above is really specific to me) you can now optimize for your development pleasure. Do this! That is the best methodology I know.