Every software project begins with fanfare and gleeful optimism. Even the smallest side hustle hacked together late at night is born of starry-eyed dreams. The team is convinced that with just a few lines of code and some open source libraries we’ll be done and accepting bonuses for our elegant, faultless work.
But then a few weeks or months in and we wake from our dreams to find git repositories filled with decisions and revisions and reversions. Is it good enough? Is it close enough to the specs? Will anyone actually use it? All too often software teams get deep into a project only to find at least some of the answers to these questions coming back as “no.” Is there any way to see it coming?
To read this article in full, please click here
(Insider Story)
Read More from This Article: 13 signs your software project may be doomed
Source: News