Why Your Software Project Sucks and How To Fix It
Reason 8 of 8: Vagueness
When specifications are still in flux, your ongoing definition of success becomes "delivering working software while refining the requirements." Your path starts with the business goal that the project is supposed to help accomplish, and from there works backwards to implementation details.
You will never know less about the implementation than at the beginning of the work, and your knowledge will increase throughout the project, so it makes sense to save those details for last. Don't make premature decisions.
When all they give you is a vague destination, turn it to your advantage. Learn how, and get further help for free every month, by picking up Don't Do That! A Contrarian Guide to Making Software Projects Not Suck. Right now.
The eZine comes out more or less once a month, and I also send out announcements as well as reminders of offers and programs from time to time--but not more than once a week.
Privacy Notice: I will not rent, lend, or give your email address to any third party, nor will I publish your name, without your prior written consent. You'll never get unsolicited email from a stranger as a result of your relationship with me. You can unsubscribe whenever you want.