Author: Admin

Strategic agility enables an organisation to sense and seize opportunities, manage uncertainty and adapt to changes. This paper presents one case study of a traditional charitable organisation taking a strategy-focused approach to agile transformation. Interview data was collected over a 13-month period through interviews at different stages and with different members of the transformation team and Heads of Department. This case study illustrates the challenges faced in such a transformation, and shows that strategic agility requires different time horizons to co-exist: a future vision, a medium term set of objectives and a short term performance monitoring perspective.

https://oro.open.ac.uk/74989/1/74989.pdf

Austerity and financial constraints have been threatening the public sector in the UK for a number of years. Foreseeing the threat of continued budget cuts, and addressing the situation many local councils face, requires
internal transformations for financial stability without losing the key focus on public service. Agile transformations have been undertaken by organisations wanting to learn from the software development community and bringing agile principles into the wider organisation. This paper describes and analyses an ongoing behaviour-led transformation in a district council in the UK. It presents the results of the analysis of 19 interviews with internal stakeholders at the council, of observations of meetings among senior and middle management in a five-month period. The paper explores the successes and the challenges encountered towards the end of the transformation process and reflects on balancing acts to address the challenges, between: disruption and business as usual, empowerment and goal setting, autonomy and processes and procedures, and behaviours and skills. Based on our findings, we suggest that behaviours on their own cannot guarantee a sustained agile culture, and that this is equally important for enterprise agility and for large-scale agile software development transformations.

https://oro.open.ac.uk/59819/8/59819.pdf

Enterprise agility requires capabilities to transform, sense and seize new business opportunities more quickly than competitors. However, acquiring those capabilities, such as continuous delivery and scaling agility to product programmes, portfolios and business models, is challenging in many organisations. This paper introduces definitions of enterprise agility involving business management and cultural lenses for analysing large-scale agile transformation. The case organisation, in the higher education domain, leverages collaborative discovery sprints and an experimental programme to enable a bottom-up approach to transformation. Meanwhile the prevalence of bureaucracy and organisational silos are often contradictory to agile principles and values. The case study results identify transformation challenges based on observations from a five-month research period. Initial findings indicate that increased focus on organisational culture and leveraging of both bottom-up innovation and supportive top-down leadership activities, could enhance the likelihood of a successful transformation.

https://oro.open.ac.uk/55138/1/10.1007%252F978-3-319-91602-6_9.pdf

Agile approaches are adopted in industry to improve outcomes from software development, and are
increasingly the subject of research studies. However, adoption is not the end of the story. Agile requires on-going change and commitment in order to become sustainable and embedded within teams and organisations. This study explores current perceptions of post-adoptive agility. We asked 50 practitioners ‘what does agile sustainability mean to you?’. Analysis of practitioner comments identified four themes: being completely agile, independent, focused on business value and need, and consistent across time. Post-adoptive agile is an under-researched area, there is inconsistent use of terminology, and there is a gap between practitioners’ and researchers’ perceptions about what
is important for sustaining agile.

https://oro.open.ac.uk/58207/1/SPPI_shortened_submitted%20copy.pdf

We present a comparison of two ways of developing and delivering MOOCs. One was developed by the Open University in collaboration with FutureLearn; the other was developed independently by a small team at Northampton University. The different approaches had very different profiles of pedagogic flexibility, cost, development processes, institutional support, and participant numbers. This comparison shows that, even several years after MOOCs came to prominence, there is a range of viable approaches for MOOCs. MOOCs on existing large platforms can reach many thousands of people, but constrain pedagogical choice. Smaller, self-made MOOCs have smaller audiences but can target them more effectively.

https://oro.open.ac.uk/49137/1/49137.pdf

Context: There continues to be concern that research is not addressing the challenges that practice faces. For the benefit of academia and industry, researchers need to be aware of practitioners’ challenges and their context so that relevant and applicable research is undertaken.

Objective: This paper investigates two research questions: what challenges do agile practitioners face? and, how do practitioner challenges manifest themselves in an organisational setting? It aims to map the practitioner challenge landscape, explore challenge characteristics, compare findings with previous literature and identify implications for research that is relevant to practice.

Method: A combination of methods was used: elicitation of practitioner challenges collected using a Challenge Wall at a series of practitioner events; organisational Case Study using interviews, document analysis and observation; and online Survey. Findings were then compared to previous publications.

Results: Challenges collected from the Challenge Wall were grouped under 27 subthemes and seven themes: Claims and Limitations, Organisation, Sustainability, Culture, Teams, Scale, and Value. Investigating one challenge in the Case Study uncovered a set of new challenges, which were interrelated. Over 50% of survey respondents experienced challenges highlighted in the Case Study.

Conclusion: The landscape of agile practitioner challenges is complex and intertwined. Some challenges, such as doing agile in a non-agile environment, are multi-dimensional, affect many aspects of practice, and may be experienced simultaneously as business, organisational, social and adaptation problems. Some challenges, such as understanding cultural change or measuring agile value, persist and are hard to address, while others, such as adoption, change focus over time. Some challenges, such as governance and contracts, are under-researched, while others, such as business and IT transformation, have been researched but findings have not had the expected impact. Researchers wishing to address practitioner challenges need to treat them in context rather than in isolation and improve knowledge transfer.

https://oro.open.ac.uk/45729/2/The%20Challenges%20That%20Challenge%20-%20final.pdf

Most companies practicing Agile are not fully Agile but instead they combine both Agile and traditional practices in their operations. It is not clear how these practices can be successfully used together in an organisation. Aims: We
investigate practitioners’ mitigation strategies related to the challenge of doing Agile in a non-Agile environment.

Method: Strategies were collected during two studies, an online survey and an interactive workshop run at an Agile meetup and analysed thematically.

Results: Strategies related to the wider organisation and not just software development. Two perspectives emerged
from the data: an organisational and a change perspective. Five organisational themes were identified with Management and decision-making and Culture the two biggest themes. Nine change themes were identified, with Being open, Using specific approaches and Educating the biggest themes.

Conclusions: Better understanding is needed of how Agile practitioners can accomplish bottom-up change in their organisation.

https://oro.open.ac.uk/46962/1/ESEM16_short_final.pdf

Agile software development relies heavily on tight and continuous collaboration, which becomes a challenge when team members work at a distance. Despite significant focus on distributed Agile working, remote working, when only one or two individuals are not co-located with the rest of the team, remains largely unexplored. We focus on one organisation with several such teams and investigate one in detail using distributed cognition – a theoretical framework for studying collaborative work. We present the results of a group retrospective, and a comparative analysis of collaboration in the team, taking the contrasting perspectives of the remote worker and his co-located teammates. The analysis shows substantial differences in three aspects: virtual artefacts; information flow;
and the primacy of structure and facilities provided by collaborative platforms. Platforms that support meaningful collaboration and engagement for the remote worker, and create parity between all members of the team are crucial to integrating capability.

https://oro.open.ac.uk/47461/1/submitted%20%20version.pdf

As agile is maturing and becoming more widely adopted, it is important that researchers are aware of the challenges faced by practitioners and organisations. We undertook a thematic analysis of 193 agile challenges collected at a series of agile conferences and events during 2013 and 2014. Participants were mainly practitioners and business representatives along with some academics. The challenges were thematically analysed by separate authors, synthesised, and a list of seven themes and 27 sub-themes was agreed. Themes were Organisation, Sustainability, Culture, Teams, Scale, Value and Claims and Limitations. We compare our findings against previous attempts to identify and categorise agile challenges. While most themes have persisted we found a shift of focus towards sustainability, business engagement and transformation, as well as claims and limitations. We identify areas for further research and a need for innovative methods of conveying academic research to industry and industrial problems to academia.

https://oro.open.ac.uk/42061/1/Gregory%20et%20al%20Agile%20Challenges%20XP2015.pdf

There is wide acceptance in the software engineering field that industry and research can gain significantly from each other and there have been several initiatives to encourage collaboration between the two. However there are some often-quoted challenges in this kind of collaboration. For example, that the timescales of research and practice are incompatible, that research is not seen as relevant for practice, and that research demands a different kind of rigour than practice supports. These are complex challenges that are not always easy to overcome. Since the beginning of 2013 we have been using an approach designed to address some of these challenges and to bridge the gap between research and practice, specifically in the agile software development arena. So far we have collaborated successfully with three partners and have investigated three practitioner-driven challenges with agile. The model of collaboration that we adopted has evolved with the lessons learned in the first two collaborations and been modified for the third. In this paper we introduce the collaboration model, discuss how it addresses the collaboration challenges between research and practice and how it has evolved, and describe the lessons learned from our experience.

https://oro.open.ac.uk/42500/2/IJSAEM%20Formatted.pdf