3 ms·

Whatever you do, DO NOT ADD new team members to an already delayed project. It will delay it further. Break down the project into simpler tasks that can be assi

by patan2 8y ago

Whatever you do, DO NOT ADD new team members to an already delayed project. It will delay it further. Break down the project into simpler tasks that can be assigned to a team member and be tracked. Attach strict responsibility of task to team member. And last and most important, talk to your Management about timelines. Make it very upfront that it will take X number of days and no lesser.

Double_a_92 8y ago
That's rather stressful for your team members though. Especially if the tasks are too much outside of everyones comfort zone. At best you will get hacky code that only properly works on first sight, just so they fullfil their task. It's like telling you that you have 3 months to achieve world peace, otherwise all the wars are your fault.
muzani 8y ago
3 months is actually enough time to add people, especially if there's the possibility of a deadline extension. I normally consider 1 month the break even point. You do have to schedule training and all. Another way to look at it is that programmers hate death marches. Projects like this could lose people, and sometimes it's good to have some backup.
- jcadam 8y ago
  Depends on the project. In aerospace (my industry), 3 months is not enough time. There's so much process and bureaucracy that everything moves very slowly. At 3 months, the new person may be just starting to look at source code. But of course, they still try it anyway. Lead: "We're in serious danger of missing our delivery date in 6 months." Suit: "Egads! Here, have 5 new grads with no experience for your team, get it done!"
yitchelle 8y ago
Instead of not adding new members, I would suggest to add new members to close out the current team's lack of knowledge. The OP indicated that the team is outside of their comfort zone, I recommend to add an expert domain into the team as a mentor to close out the gap.
wolco 8y ago
Or hire seniors devs who can make the learning curve shorter.

by patan2 8y ago

Double_a_92 8y ago

That's rather stressful for your team members though. Especially if the tasks are too much outside of everyones comfort zone. At best you will get hacky code that only properly works on first sight, just so they fullfil their task. It's like telling you that you have 3 months to achieve world peace, otherwise all the wars are your fault.

muzani 8y ago

3 months is actually enough time to add people, especially if there's the possibility of a deadline extension. I normally consider 1 month the break even point. You do have to schedule training and all. Another way to look at it is that programmers hate death marches. Projects like this could lose people, and sometimes it's good to have some backup.

jcadam 8y ago
Depends on the project. In aerospace (my industry), 3 months is not enough time. There's so much process and bureaucracy that everything moves very slowly. At 3 months, the new person may be just starting to look at source code. But of course, they still try it anyway. Lead: "We're in serious danger of missing our delivery date in 6 months." Suit: "Egads! Here, have 5 new grads with no experience for your team, get it done!"

yitchelle 8y ago

Instead of not adding new members, I would suggest to add new members to close out the current team's lack of knowledge. The OP indicated that the team is outside of their comfort zone, I recommend to add an expert domain into the team as a mentor to close out the gap.

wolco 8y ago

Or hire seniors devs who can make the learning curve shorter.