The construction of scientific papers is performed in service of the greater scientific community. This iterative process is, in effect, an academic economy, where all members benefit from well-written papers. However, many published scientific papers are poorly written; they often lack sufficient detail to allow replication, there is improper usage of citations or a lack of regard to relevant work, reporting is vague or without linked empirical data to allow verification, figures do not correspond to text or are non-sensical, literary elements, e.g., bulleted lists, are used ineffectively, formatting renders certain sections unreadable, and grammatical errors abound. The issues of paper quality are widespread and of varying concern. Similarly, the development of software systems is rife with many processual issues, from high-level architectural flaws to small developer errors, e.g., setting a Boolean value to true instead of false, which can be disastrous in large systems. As an answer to these longstanding concerns, software development methods have emerged over decades, most notably, the Waterfall and Agile approaches. These methods have established software engineering as a professional discipline backed by rigorous, empirical evaluation on many systems. A scientific paper is, conceptually, a system to be developed, much like a software system: it has a name, particular sections codified for different purposes, e.g., as the abstract summarizes and the conclusion concludes, it has an author or authors, it goes through several iterations of refinement, it may reference outside systems and it is eventually released to the public, and possibly maintained in future versions. It is posited that, due to the relatively small nature of most scientific papers (4-20 pages), the Agile method of software development can be used to produce more reliable scientific papers, in a more efficient manner and with better availability to readers, by employing the principles of open-source software, and a version control system, e.g., Git. Agile methods consistently provide deliverables of higher quality; this work intends to demonstrate that Agile can be adapted to streamline the scientific writing process and improve publication quality.
","abstract_html":"<p>The construction of scientific papers is performed in service of the greater scientific community. This iterative process is, in effect, an academic economy, where all members benefit from well-written papers. However, many published scientific papers are poorly written; they often lack sufficient detail to allow replication, there is improper usage of citations or a lack of regard to relevant work, reporting is vague or without linked empirical data to allow verification, figures do not correspond to text or are non-sensical, literary elements, e.g., bulleted lists, are used ineffectively, formatting renders certain sections unreadable, and grammatical errors abound. The issues of paper quality are widespread and of varying concern. Similarly, the development of software systems is rife with many processual issues, from high-level architectural flaws to small developer errors, e.g., setting a Boolean value to true instead of false, which can be disastrous in large systems. As an answer to these longstanding concerns, software development methods have emerged over decades, most notably, the Waterfall and Agile approaches. These methods have established software engineering as a professional discipline backed by rigorous, empirical evaluation on many systems. A scientific paper is, conceptually, a system to be developed, much like a software system: it has a name, particular sections codified for different purposes, e.g., as the abstract summarizes and the conclusion concludes, it has an author or authors, it goes through several iterations of refinement, it may reference outside systems and it is eventually released to the public, and possibly maintained in future versions. It is posited that, due to the relatively small nature of most scientific papers (4-20 pages), the Agile method of software development can be used to produce more reliable scientific papers, in a more efficient manner and with better availability to readers, by employing the principles of open-source software, and a version control system, e.g., Git. Agile methods consistently provide deliverables of higher quality; this work intends to demonstrate that Agile can be adapted to streamline the scientific writing process and improve publication quality.</p>","abstract_has_math":false,"creators":["Procko, Tyler"],"institution":null,"degree_name":"Master of Software Engineering","degree_level":"Thesis - Open Access","degree_discipline":"Electrical, Computer, Software, and Systems Engineering","degree_department":null,"school":null,"contributors":[],"advisors":[],"committee_chairs":[],"committee_members":[],"year":2023,"date_issued":"2023-10-01T07:00:00Z","date_published":"2023-10-01T07:00:00Z","updated_at":"2026-07-27T19:25:52Z","subjects":["agile","software engineering","research","metascience","process development","scientific writing","Computer Engineering","Linguistics","Management Information Systems","Publishing","Scholarly Communication","Scholarly Publishing","Strategic Management Policy","Systems Engineering","Systems Science"],"languages":[],"rights":[],"rights_urls":[],"identifier_entries":[]},"links":{"outbound_url":"https://commons.erau.edu/edt/784","outbound_label":"Repository record","outbound_source":"dc:identifier"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:creator","label":"Author","values":["Procko, Tyler"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"thesis:degree_discipline","label":"Discipline","values":["Electrical, Computer, Software, and Systems Engineering"]},{"key":"thesis:degree_level","label":"Degree Level","values":["Thesis - Open Access"]},{"key":"thesis:degree_name","label":"Degree Name","values":["Master of Software Engineering"]}]},{"id":"subjects_keywords","label":"Subjects and Keywords","entries":[{"key":"dc:subject","label":"Dc Subject","values":["agile","software engineering","research","metascience","process development","scientific writing","Computer Engineering","Linguistics","Management Information Systems","Publishing","Scholarly Communication","Scholarly Publishing","Strategic Management Policy","Systems Engineering","Systems Science"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier","label":"Identifier","values":["https://commons.erau.edu/edt/784"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description.abstract","label":"Abstract","values":["The construction of scientific papers is performed in service of the greater scientific community. This iterative process is, in effect, an academic economy, where all members benefit from well-written papers. However, many published scientific papers are poorly written; they often lack sufficient detail to allow replication, there is improper usage of citations or a lack of regard to relevant work, reporting is vague or without linked empirical data to allow verification, figures do not correspond to text or are non-sensical, literary elements, e.g., bulleted lists, are used ineffectively, formatting renders certain sections unreadable, and grammatical errors abound. The issues of paper quality are widespread and of varying concern. Similarly, the development of software systems is rife with many processual issues, from high-level architectural flaws to small developer errors, e.g., setting a Boolean value to true instead of false, which can be disastrous in large systems. As an answer to these longstanding concerns, software development methods have emerged over decades, most notably, the Waterfall and Agile approaches. These methods have established software engineering as a professional discipline backed by rigorous, empirical evaluation on many systems. A scientific paper is, conceptually, a system to be developed, much like a software system: it has a name, particular sections codified for different purposes, e.g., as the abstract summarizes and the conclusion concludes, it has an author or authors, it goes through several iterations of refinement, it may reference outside systems and it is eventually released to the public, and possibly maintained in future versions. It is posited that, due to the relatively small nature of most scientific papers (4-20 pages), the Agile method of software development can be used to produce more reliable scientific papers, in a more efficient manner and with better availability to readers, by employing the principles of open-source software, and a version control system, e.g., Git. Agile methods consistently provide deliverables of higher quality; this work intends to demonstrate that Agile can be adapted to streamline the scientific writing process and improve publication quality.
"]},{"key":"dc:title","label":"Title","values":["Towards Agile Academia: An Approach to Scientific Paper Writing Inspired by Software Engineering"]}]}],"canonical_facts":{"dc:creator":["Procko, Tyler"],"dc:description.abstract":["The construction of scientific papers is performed in service of the greater scientific community. This iterative process is, in effect, an academic economy, where all members benefit from well-written papers. However, many published scientific papers are poorly written; they often lack sufficient detail to allow replication, there is improper usage of citations or a lack of regard to relevant work, reporting is vague or without linked empirical data to allow verification, figures do not correspond to text or are non-sensical, literary elements, e.g., bulleted lists, are used ineffectively, formatting renders certain sections unreadable, and grammatical errors abound. The issues of paper quality are widespread and of varying concern. Similarly, the development of software systems is rife with many processual issues, from high-level architectural flaws to small developer errors, e.g., setting a Boolean value to true instead of false, which can be disastrous in large systems. As an answer to these longstanding concerns, software development methods have emerged over decades, most notably, the Waterfall and Agile approaches. These methods have established software engineering as a professional discipline backed by rigorous, empirical evaluation on many systems. A scientific paper is, conceptually, a system to be developed, much like a software system: it has a name, particular sections codified for different purposes, e.g., as the abstract summarizes and the conclusion concludes, it has an author or authors, it goes through several iterations of refinement, it may reference outside systems and it is eventually released to the public, and possibly maintained in future versions. It is posited that, due to the relatively small nature of most scientific papers (4-20 pages), the Agile method of software development can be used to produce more reliable scientific papers, in a more efficient manner and with better availability to readers, by employing the principles of open-source software, and a version control system, e.g., Git. Agile methods consistently provide deliverables of higher quality; this work intends to demonstrate that Agile can be adapted to streamline the scientific writing process and improve publication quality.
"],"dc:identifier":["https://commons.erau.edu/edt/784"],"dc:subject":["agile","software engineering","research","metascience","process development","scientific writing","Computer Engineering","Linguistics","Management Information Systems","Publishing","Scholarly Communication","Scholarly Publishing","Strategic Management Policy","Systems Engineering","Systems Science"],"dc:title":["Towards Agile Academia: An Approach to Scientific Paper Writing Inspired by Software Engineering"],"thesis:degree_discipline":["Electrical, Computer, Software, and Systems Engineering"],"thesis:degree_level":["Thesis - Open Access"],"thesis:degree_name":["Master of Software Engineering"]},"updated_at":"2026-07-27T19:25:52Z"}