The Deadline Conflict
You are a project manager at a software company. Your team is developing a new mobile app. The client has requested a feature that will take an estimated 120 developer-hours to implement. Your team has 3 developers available, each working 40 hours per week. However, one developer is on vacation for the next two weeks. The project deadline is in 4 weeks. Currently, the team is also working on another project that requires 60 hours per week from the team. The client insists the new feature is critical and must be included in the initial release.
1. Calculate the total available developer-hours for the new feature over the next 4 weeks, considering the vacation and the ongoing project.
Read the worked answer
Total developer-hours available in 4 weeks: 3 developers * 40 hours/week * 4 weeks = 480 hours. Subtract vacation: one developer is away for 2 weeks, so 1 * 40 * 2 = 80 hours lost. Net available: 480 - 80 = 400 hours. Subtract ongoing project: 60 hours/week * 4 weeks = 240 hours. Remaining for new feature: 400 - 240 = 160 hours. The feature requires 120 hours, so 160 > 120, so it is feasible if all remaining time is allocated to the feature.
2. What are the risks and possible mitigation strategies?
Read the worked answer
Risks: The estimate may be optimistic; developers may be pulled to other tasks; vacation could be extended; the ongoing project may require more time. Mitigation: Prioritize the feature, possibly reduce scope of ongoing project, bring in a contractor for 40 hours, or negotiate a phased release. Also, monitor progress weekly and adjust.