21,268 research outputs found
Digital transformation in the arts : a case study
This paper considers the interaction between digital technology and cultural organisations and the
challenges and opportunities this presents for practice and for policy. The paper is based on one of
eight 'digital R&D' projects supported by NESTA, Arts Council England and the AHRC, designed to
analyse the effects of digital innovation in UK arts organisations.
The paper focuses on a series of residencies in three UK arts organisations. The research aims to
identify the cultural conditions which support or prevent short-term digital innovation becoming
'embedded' in the ongoing practice of a cultural organisation. The paper considers differing practices,
attitudes and expectations between creative technologists and arts organisations. These differing
'cultures of innovation' may help us to understand why digital innovations often fail to move beyond
temporary and pragmatic problem-solving towards more challenging, transformational effects on
organisational strategy and culture
Historical roots of Agile methods: where did âAgile thinkingâ come from?
The appearance of Agile methods has been the most noticeable change to software process thinking in the last fifteen years [16], but in fact many of the âAgile ideasâ have been around since 70âs or even before. Many studies and reviews have been conducted about Agile methods which ascribe their emergence as a reaction against traditional methods. In this paper, we argue that although Agile methods are new as a whole, they have strong roots in the history of software engineering. In addition to the iterative and incremental approaches that have been in use since 1957 [21], people who criticised the traditional methods suggested alternative approaches which were actually Agile ideas such as the response to change, customer involvement, and working software over documentation. The authors of this paper believe that education about the history of Agile thinking will help to develop better understanding as well as promoting the use of Agile methods. We therefore present and discuss the reasons behind the development and introduction of Agile methods, as a reaction to traditional methods, as a result of people's experience, and in particular focusing on reusing ideas from histor
Recommended from our members
Requirements Engineering as Creative Problem Solving: A Research Agenda for Idea Finding
This vision paper frames requirements engineering as a creative problem solving process. Its purpose is to enable requirements researchers and practitioners to recruit relevant theories, models, techniques and tools from creative problem solving to understand and support requirements processes more effectively. It uses 4 drivers to motivate the case for requirements engineering as a creative problem solving process. It then maps established requirements activities onto one of the longest-established creative problem solving processes, and uses these mappings to locate opportunities for the application of creative problem solving in requirements engineering. The second half of the paper describes selected creativity theories, techniques, software tools and training that can be adopted to improve requirements engineering research and practice. The focus is on support for problem and idea finding - two creative problem solving processes that our investigation revealed are poorly supported in requirements engineering. The paper ends with a research agenda to incorporate creative processes, techniques, training and tools in requirements projects
Towards a situated media practice: Reflections on the implementation of project-led problem-based learning
In the field of media practice education, project-based learning is utilized as a major pedagogic paradigm with the aim of mirroring professional practice within the curriculum. However, if the use of project-based learning is to be considered as more than just a way of administrating student activity, then educators need a critical understanding of how problem encounters order practice within the life cycle of a project. The drawing together of practice-based, project-based and problem-based approaches allows us to see the overlapping nature of these approaches and also differentiate them as unique pedagogies in their own right. It is argued here that this tension between similarity and difference requires a new way of thinking about mirroring professional practice within higher education, one which offers a theory of project-based learning as a productive pedagogy which places problem encounters at its heart
Agile methods for agile universities
We explore a term, Agile, that is being used in various workplace settings, including the management of universities. The term may have several related but slightly different meanings. Agile is often used in the context of facilitating more creative problem-solving and advocating for the adoption, design, tailoring and continual updating of more innovative organizational processes. We consider a particular set of meanings of the term from the world of software development. Agile methods were created to address certain problems with the software development process. Many of those problems have interesting analogues in the context of universities, so a reflection on agile methods may be a useful heuristic for generating ideas for enabling universities to be more creative
Coordinating Knowledge Work in Multi-Team Programs: Findings from a Large-Scale Agile Development Program
Software development projects have undergone remarkable changes with the
arrival of agile development methods. While intended for small, self-managing
teams, these methods are increasingly used also for large development programs.
A major challenge in programs is to coordinate the work of many teams, due to
high uncertainty in tasks, a high degree of interdependence between tasks and
because of the large number of people involved. This revelatory case study
focuses on how knowledge work is coordinated in large-scale agile development
programs by providing a rich description of the coordination practices used and
how these practices change over time in a four year development program with 12
development teams. The main findings highlight the role of coordination modes
based on feedback, the use of a number of mechanisms far beyond what is
described in practitioner advice, and finally how coordination practices change
over time. The findings are important to improve the outcome of large
knowledge-based development programs by tailoring coordination practices to
needs and ensuring adjustment over time.Comment: To appear in Project Management Journa
Lean principles applied to software development â avoiding waste
Under the current economic conditions many organizations strive to continue the trend towards adopting better software development processes, in order to take advantage of the numerous benefits that these can offer. Those benefits include quicker return on investment, better software quality, and higher customer satisfaction. To date, however, there is little body of research that can guide organizations in adopting modern software development practices, especially when it comes to Lean thinking and principles. To address this situation, the current paper identifies and structures the main wastes (or muda in Lean terms) in software development as described by Lean principles, in an attempt to bring into researchersâ and practitionersâ attention Lean Software Development, a modern development methodology based on well-established practices such as Lean Manufacturing or Toyota Production System.Lean, software development, agile methodologies
- âŚ