A New Teaching Model For The Subject Of Software Project Management

Software (SW) development is a very tough task which requires a skilled project leader for its success. If the project leader is not skilled enough then project may fail. In the real world of SW engineering 65% of the SW projects fail to meet their objectives as in [1]. The main reason is lack of training of the project mangers. This extreme ratio of failure can be reduced by teaching SW project management (SPM) to the future project managers in the practical manner, so that they may be skillful enough to handle the project in a better way. This paper intends to propose a model to be used to teach SPM to the student of SW engineering to reduce the failure rate of projects.

💡 Research Summary

The paper begins by highlighting the critical role of software project management (SPM) in the success of software development initiatives and points out that a striking 65 % of projects fail to meet their objectives, largely due to insufficient managerial training. After reviewing the shortcomings of current university curricula—where SPM is taught predominantly through lectures and lacks hands‑on experience—the authors propose a comprehensive, practice‑oriented teaching model designed to bridge the gap between theory and industry. The model is structured around four sequential phases. In the first phase, students receive authentic project requirements and constraints supplied by partner companies, forcing them to conduct realistic requirement analysis and initial scoping. The second phase focuses on planning and scheduling, combining classic techniques such as Gantt charts, CPM, and PERT with agile sprint planning to expose learners to both predictive and adaptive approaches. The third phase, execution and control, immerses students in full‑stack development, continuous integration, version control, and quality‑assurance tools while simultaneously requiring them to identify risks, devise mitigation strategies, and produce regular status reports. The final phase involves project closure, formal verification of deliverables, post‑mortem analysis, and feedback collection from industry mentors. Pedagogically, the model relies on project‑based learning (PBL), industry‑partner mentorship, simulation tools, and iterative review sessions. Faculty members collaborate with seasoned practitioners to co‑teach modules, and students work in self‑organized teams that mirror real‑world dynamics. The authors argue that this immersive approach will enhance problem‑solving abilities, communication skills, and risk‑management competence, ultimately reducing the high failure rate observed in the field. While the proposal is conceptually sound, the paper lacks empirical validation; no pilot study, performance metrics, or cost‑benefit analysis are presented. Moreover, practical concerns such as the need for dedicated lab infrastructure, software licenses, and faculty development are only briefly mentioned. The authors conclude by recommending a controlled pilot implementation, systematic data collection on project success rates, schedule adherence, and quality outcomes, and a longitudinal study of graduates’ performance in professional SPM roles. This future work is essential to substantiate the model’s efficacy and to refine it for broader adoption across software engineering programs.