Your 3 factors are sort of a rephrasing of the old refrain: "Fast, good, and cheap. Pick 2."
The issue, however, is that the "size of the team" factor ignores Brook's law: adding manpower to a late software project makes it later. I think it's even worse than that, that in a real-world scenario, adding people can never pull forward a delivery date but has a high chance of pushing it back, even if the project is on time or ahead of schedule. There are obviously caveats to this, mostly for long-term planning.
I've seen others say recently that Scrum in general is guilty of the same mistake that so many others make in forgetting the lessons laid out in The Mythical Man-Month, and I'm starting to thing they might be right. I have a lot of criticisms of Scrum, but I think this might be the source of many of them.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Your 3 factors are sort of a rephrasing of the old refrain: "Fast, good, and cheap. Pick 2."
The issue, however, is that the "size of the team" factor ignores Brook's law: adding manpower to a late software project makes it later. I think it's even worse than that, that in a real-world scenario, adding people can never pull forward a delivery date but has a high chance of pushing it back, even if the project is on time or ahead of schedule. There are obviously caveats to this, mostly for long-term planning.
I've seen others say recently that Scrum in general is guilty of the same mistake that so many others make in forgetting the lessons laid out in The Mythical Man-Month, and I'm starting to thing they might be right. I have a lot of criticisms of Scrum, but I think this might be the source of many of them.