Coding, Tech and Developers Blog
Today, even in the age of agile, people still tend to use terms like the “man month” in software engineering. Customer deadlines, tight schedules often lead to the conclusion that, to make up for something misplanned in the past, you can always put more manpower into a project and everything will be fine.
Needless to say, this is a management perspective (or, rather, a consultant perspective). Now, of course, software developing can be a parallel process, but when it comes to integrating those parallel tracks into one, the whole thing becomes very linear, especially in terms of debugging.
Being a developer myself, I tend to feel that putting more personnel into a late project is a very risky thing to do. When discussing these things with the persons in charge, the question will eventually come up of how much developers a project or, more precisely, code base, can stomach. Second, being a physicist originally, I also like numbers and statistics. This is why I am writing this post.
I would like to get a grip on answering this question with more data than only from my own experience. For this I need the help of the community. I feel that some of you might find this topic interesting as well.
So, in order not to compare apples and oranges, we need a few rules.
I will of course provide the first data myself:
Language: C# Project type: Rich-client, multi-app solution Number of active devs: 25 Number of software testers: 10 Code base: 10,000 files and growing.
I will be happily reading your comments!
Be the first to know when a new post was released