scholarly journals A Framework for Requirements Prioritisation Process in an Agile Software Development Environment: Empirical Study

2016 ◽  
Vol 6 (6) ◽  
pp. 846 ◽  
Author(s):  
Rami Hasan Al-Ta’ani ◽  
Rozilawati Razali
Keyword(s):  
Empirical Study ◽  
Software Development ◽  
Agile Software Development ◽  
Development Environment ◽  
Software Development Environment ◽  
Agile Software

ACSESim: Agile and Lean software development in practice

2018 ◽  
Vol 8 (1) ◽  
pp. 1-25
Author(s):  
Andries Maritz ◽  
Fatima Hamdulay
Keyword(s):  
Software Development ◽  
Knowledge Work ◽  
Agile Software Development ◽  
Point Of View ◽  
Development Environment ◽  
Lean Thinking ◽  
Content Type ◽  
Software Development Environment ◽  
Agile Software ◽  
The Impact

Subject area Agile software development, Knowledge workers and Lean thinking as a management system Study level/applicability The case lends itself to students of business management, or aspiring consultants, who have been exposed to operations management in general and Lean thinking specifically. It is an advanced case study, assuming prior knowledge in these subjects and approaches the subject matter from an organisational development point of view, rather than a pure operations point of view. It is thus well suited to an elective on operational excellence on an MBA or in executive education courses in Lean thinking Case overview The case starts with Mark, manager of a software development team, hearing that he will have budget for two new developers who will join his team in the coming year. While the extra help could be useful, he was considering what the impact of new people would be on the productivity of the team, which he felt was already stretched. Mark continues to consider the entire development chain and how code changes were implemented to ACSESim’s (the company’s primary product) graphical user interfaces. Having recently been acquired by an American company, he was also under pressure to start to adopt some of the parent company’s systems, which would constitute a fairly disruptive, but necessary, change, particularly for future collaborations with other developers in the parent company. With two new developers, experience taught Mark that development could slow down owing to training efforts. To minimise disruption, he was wondering about how to get the new developers up-to-speed quickly and streamline their operations within a changing corporate environment. The case highlights the different mechanisms that were in place at ACSESim, including the use of issue trackers; Kanban boards; version control software; automated systems; stand-up meetings, etc. Each of these mechanisms is discussed briefly and shows the value they added to the development practices that were in place. This also allows students to understand Agile practices and what Lean thinking might mean in a knowledge work environment and then to consider what the proposed changes might mean and how they could be deployed. Expected learning outcomes To gain an understanding of how Lean and Agile principles can be applied in a software development environment and Lean knowledge work in general To consider the best way to manage new hires so that they can become productive in a Lean or Agile software development environment, whilst dealing with pressures to migrate to new systems. Supplementary materials Teaching notes are available for educators only. Please contact your library to gain login details or email [email protected] to request teaching notes. Subject code CSS: 9: Operations and Logistics.

Sign in / Sign up

Export Citation Format

Share Document