KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
Lately I have seen our development team getting dangerously close to the ' second system syndrome ' type ideas while we are planning the next version of our product. While I'm all for making improvements and undoing some of the mistakes of our past, I would hate to see us stuck in an endless loop of rewriting and never launching anything. Is there a good design / development method that lends itself to building a better version 2.0 while avoiding second system scenarios?
Tags (comma-separated)
Save Edits
Cancel