Note: When clicking on a Digital Object Identifier (DOI) number, you will be taken to an external site maintained by the publisher.
Some full text articles may not yet be available without a charge during the embargo (administrative interval).
What is a DOI Number?
Some links on this page may take you to non-federal websites. Their policies may differ from this site.
Study explores Scrum, a comprehensive team performance process based on Agile engineering principles, through an I/O lens. Study focuses on impact of Scrum implementation on team performance, organizational culture, and change management. Role of I/O in implementing engineering process improvement programs is discussed, as well as need for greater I/O involvement in engineering process management.
This RESEARCH paper examines faculty perceptions regarding the use of Scrum for departmental operations. Scrum is an agile methodology that applies processes and procedures that encourage transparency, inspection, and adaptation in the creation of a product. Across the literature for engineering education change, there has been a focus on identifying the barriers and affordances to cultural change in engineering departments. The objective of this paper is to examine the driving factors and barriers to implementing Scrum for departmental operations. The paper will specifically address how a group of faculty about to adopt Scrum perceive the impact of that adoption on potential changes to departmental operations and culture. Findings indicate concerns with the traditional barriers of time and workload. However, they also indicate that there is some expectation for Scrum to decrease elements of the faculty workload and reduce time to complete tasks. These findings also build on the understanding of how faculty collaboration is perceived as both a barrier and affordance to departmental change.
What might it mean to be an agile academic department? An agile college? An agile university? “Agile”, as used here, refers to practices and frameworks in software development and deployment, such as Scrum, Extreme Programming, and Crystal Clear. The Agile movement’s founding documents, the Agile Manifesto and its accompanying Agile Principles [https://agilemanifesto.org/], were published by leading software engineering researchers in February of 2001. The Manifesto staked out distinction with the prevailing software development approach at the time, called planned development and otherwise known as waterfall. The Agile Manifesto states, "We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: "Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan "That is, while there is value in the items on the right, we value the items on the left more.” Since the Manifesto’s publication, Agile use has expanded from its then primarily application in software development into a wide range of activities, from rocket motors (Space X), to race car development (Wikispeed), to finance (World Bank), to human resources (ING). Denning postulates Threemore »