Search code examples
project-planning

Looking for a good approach to "spec" a project


I have noticed that when writing specs you waste a lot of time on things, that later, when you write your app are negligible, and you forget some important stuff.
I have found it to be faster (for me) to write a proof-of-concept application (no good error handlers and security stuff, minor gliches in the style etc) and use that as a spec for those who join me.

Still, I feel I am wasting time in this method too, any good ideas on how this should be done?


Solution

  • Seems like you're arguing in favor of Agile Development

    Using this iterative process, our team is able to "rank" features on a scale of importance and then weigh the release date with the features they want (in a nutshell)