Mitigating Project Failures & Turnaround

Lecture 12 presents proactive mitigation strategies, project recovery planning, and turnaround methodologies for troubled software projects. When a project exhibits critical schedule slippage or budget overrun, standard management intervention is required to avoid total collapse. The lecture details project triage procedures: re-evaluating core requirements, discarding non-essential features, re-baselining delivery milestones, and negotiating trade-offs with stakeholders. Students explore the dangers of Brooks' Law (adding manpower to a late software project makes it later) and learn constructive recovery practices including stabilizing requirements and establishing achievable recovery milestones. Hands-on analysis of milestone deliverables equips students with practical competency in tracking project health and managing stakeholder expectations. Clear definitions of project charter elements, milestone schedules, and acceptance criteria ensure governance alignment from project kickoff to closure. Quantitative productivity benchmarks and complexity adjustment factors are evaluated to calibrate estimation accuracy across diverse project domains. Comprehensive review of Virtual University exam patterns and past paper topics consolidates theoretical mastery and practical problem-solving capability. In this lecture, students examine essential project management governance principles and PMBOK knowledge areas to ensure structured engineering delivery. Through detailed analytical walkthroughs, the lesson explores quantitative metrics, resource allocation trade-offs, and critical path scheduling. Special emphasis is placed on stakeholder alignment, communication planning, and proactive software risk management strategies. Mastering these foundational management frameworks empowers prospective software project managers to deliver complex systems within budget and schedule baselines. Analytical exercises and real-world case evaluations help students prepare thoroughly for Virtual University midterm and final term examinations. The curriculum systematically aligns practical industry workflows with formal IEEE software engineering standards and CMMI process maturity levels. Reviewing the accompanying lecture handouts and conceptual diagrams reinforces understanding of project monitoring, earned value analysis, and quality assurance. Consistent evaluation of planning templates, estimation equations, and decomposition hierarchies ensures robust preparation for academic assessments. Students investigate the role of the Software Development Plan in synchronizing development activities across multidisciplinary engineering teams. The discussion highlights how requirements traceability matrices prevent scope creep and ensure adherence to agreed software specifications.