I can relate to your post very well. I have been such projects a few times now. For me,there is a communication barrier between non-techincal manager and developers. Budget planning also seems to be an issue, and there is usually more responsibility/pressure for a single developer. Most importantly, stakeholders have vague ideas of the products they want to build, and result in feature creeps or less than MVP product.
I am a developer with a passion for testing. I've been coding for 14 years and I want to share my experience and learnings with other developers to help them write better software.
I can relate to your post very well. I have been such projects a few times now. For me,there is a communication barrier between non-techincal manager and developers. Budget planning also seems to be an issue, and there is usually more responsibility/pressure for a single developer. Most importantly, stakeholders have vague ideas of the products they want to build, and result in feature creeps or less than MVP product.
Glad it's useful. It is essential you work with clients to clearly define what they want before you begin building. Vagueness is a killer.
As a developer, I feel bad when I had to make shortcuts to just make it work and meet the deadline, thus producing less maintainable code.