What I do to overcome that is to severely reduce the scope of version 1 and to push out releases (even private ones). This works for client work and for my own

What I do to overcome that is to severely reduce the scope of version 1 and to push out releases (even private ones). This works for client work and for my own projects, too. Having a usable something pushed out completely change the remaining part, based on feedback. To cut your scope and try to keep a very small part of it, you can use the following techniques: - http://www.mountaingoatsoftware.com/tools/theme-screening http://www.mountaingoatsoftware.com/tools/theme-screening - http://www.mountaingoatsoftware.com/tools/theme-scoring http://www.mountaingoatsoftware.com/tools/theme-scoring - http://www.scrumalliance.org/resource_download/284 http://www.scrumalliance.org/resource_download/284 [pdf] -> most recommended Another tip: try to find how handling the "polish/release/promote" bits could be fun for you. For me it was: learning a bit more of css/sass, monitoring the effect of promotion etc. There's almost always a way to do it in a fun fashion.