New Product Development Methodologies
July 12, 2005 8:48 AM Subscribe
I'm looking for an article I once read that described the best way to develop a new software product within a company that must continue to build/support its legacy applications.
The premise was, I believe, that you must isolate the developers you assign to the new project and treat them as if they work for a new and different company. No resouce sharing, no pulling them back into support for the older stuff. I looked at Joel on Software (an obvious source) but I couldn't find it. Any ideas on where I might have read this?
It was most likely a fairly mainstream site so I don't think its a wild goose chase here.
The premise was, I believe, that you must isolate the developers you assign to the new project and treat them as if they work for a new and different company. No resouce sharing, no pulling them back into support for the older stuff. I looked at Joel on Software (an obvious source) but I couldn't find it. Any ideas on where I might have read this?
It was most likely a fairly mainstream site so I don't think its a wild goose chase here.
This thread is closed to new comments.
posted by andrew cooke at 3:38 PM on July 12, 2005