Revenant

Has anyone have or had experience with a development setup where the team works on the project 24/5? Is it common practice?

@Dimitrimx Kantai Collection.

Even though there aren't much numerical estimates given, I can see that most people here have reached a consensus: writing TDD'd code would be slower than untested at first, but this gap closes over time and it's possible to go beyond that and develop faster with TDD than developing untested.

@Buhb That's something I (or even my superiors) can't really control completely; we have free rein over dates for certain projects, while some we do as soon as possible. It usually depends on how urgent the need for said software is.

@DocBrown There is. My work is around 60% new projects, 40% maintenance (both bug fixes and new features).

@DocBrown Maintenance for projects I develop is still my responsibility, albeit a secondary one. My main focus is the development project at hand. I do not have the luxuries of having a software QA team and/or maintenance programmers, otherwise I wouldn't have asked this question.