The programming activities of a project were planned to last 35 days per module, but the programming of the first module has taken 45 days. What should the project manager do?

While asking the team to work overtime may provide a temporary solution, it does not address the underlying issues causing the delay and can lead to burnout or decreased productivity among team members. This approach is often not sustainable and may not ultimately meet project deadlines without risking quality.

Submitting a change request only to adjust the schedule can be a reactive measure that does not consider the potential for recovery without altering the project plan. It may also prolong the project approval process, delaying necessary actions to get back on track. A schedule change should be a last resort after exploring other options.

While verifying scope creep is important, this option focuses on identifying problems rather than implementing solutions. It may lead to delays in addressing the current timeline issue and does not actively propose ways to bring the project back on schedule, which is essential in this scenario.