Software engineering in the Philippines: A survey and analysis of the academe and industry practices
G. Tongco-Rosario, C. Estabillo, Lázaro Figueroa
Abstract
G. Tongco-Rosario, C. Estabillo, Lázaro Figueroa
Abstract
This paper studied the state of software engineering practices in the Philippines. Survey, analysis of projects and interviews were conducted in the industry as well as the academe. Based on the survey results, most companies use agile method with scrum as the most preferred variant. Waterfall, prototyping and timeboxing are also evident in these companies, at times used together (e.g agile scrum-waterfall). The most common method used by students in software development projects is waterfall, followed by prototyping. There is a general awareness of agile-scrum in the universities studied, with the method implemented in one of the student projects. For companies, time-constraint and re-work due to requirement change or additional requirement remains to be the most common challenge. Planning in using agile method and frequency of scrum meetings can also be improved. In the academe, risk management can be complemented with issue management as a way to handle realized risks.
A significance statement is not available in the OpenAlex record.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
This paper studied the state of software engineering practices in the Philippines. Survey, analysis of projects and interviews were conducted in the industry as well as the academe. Based on the survey results, most companies use agile method with scrum as the most preferred variant. Waterfall, prototyping and timeboxing are also evident in these companies, at times used together (e.g agile scrum-waterfall). The most common method used by students in software development projects is waterfall, followed by prototyping. There is a general awareness of agile-scrum in the universities studied, with the method implemented in one of the student projects. For companies, time-constraint and re-work due to requirement change or additional requirement remains to be the most common challenge. Planning in using agile method and frequency of scrum meetings can also be improved. In the academe, risk management can be complemented with issue management as a way to handle realized risks.
Key concepts: Scrum, Agile software development, Waterfall, Waterfall model, Software prototyping, Engineering management, Engineering, Work (physics)