7,836 research outputs found
Role clarity deficiencies can wreck agile teams
Background
One of the twelve agile principles is to build projects around motivated individuals and trust them to get the job done. Such agile teams must self-organize, but this involves conflict, making self-organization difficult. One area of difficulty is agreeing on everybody’s role.
Background
What dynamics arise in a self-organizing team from the negotiation of everybody’s role?
Method
We conceptualize observations from five agile teams (work observations, interviews) by Charmazian Grounded Theory Methodology.
Results
We define role as something transient and implicit, not fixed and named. The roles are characterized by the responsibilities and expectations of each team member. Every team member must understand and accept their own roles (Local role clarity) and everbody else’s roles (Team-wide role clarity). Role clarity allows a team to work smoothly and effectively and to develop its members’ skills fast. Lack of role clarity creates friction that not only hampers the day-to-day work, but also appears to lead to high employee turnover. Agile coaches are critical to create and maintain role clarity.
Conclusions
Agile teams should pay close attention to the levels of Local role clarity of each member and Team-wide role clarity overall, because role clarity deficits are highly detrimental
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
Information flows at inter-team boundaries in agile information systems development
Agile software development methods are being used on larger projects thus the study of inter-team communication are becoming an important topic of interest for researchers. This research addresses inter-team communication by exploring the tools and three different boundaries, inter-team, team and customers, and geographically separated teams. In this research, we gathered data from semi-structured face-to-face interviews which were analyzed following the grounded theory approach. Our study reveals consensus from different teams on the importance of virtual Kanban boards. Also, some teams members tend to adapt to other teams’ preferred communication tool. We observed challenges around interdependent user stories among the different teams and highlighted the problems that rise at the different boundaries.
Keywords: agile information system development • inter-team communication • agile team boundary • communication • agile methods • cooperating agile team
Challenges In Transitioning From Waterfall To Scrum
In today\u27s fast-paced, fiercely competitive world; speed and flexibility are essential. Companies are increasingly realizing that the sequential approach to developing new product simply will not get the job done.
The goal of this thesis is to investigate critical issues and challenges that occur during the transition from a traditional software development methodology such as Waterfall to Scrum. During the last decade, Scrum has gained a vast success in software development due to its lightweight character and efficient way of handling the challenges of increased market speed, change and product complexity.
This thesis is based on a sequential exploratory mixed methods research model, which uses both qualitative as well as quantitative research methods to investigate the problem. The rationale for this is that neither method is sufficient by itself to capture the trends and details of situations. When used in combination, both quantitative and qualitative methods complement each other and provide a more complete picture of the research problem.
There are six main results from this thesis. First the main challenges are identified. Second, they are ranked based on their frequency of occurrence and thirdly, based on their importance. Fourth, the correlation between the frequency of occurrence of challenge and their importance is measured. This thesis also examines the varied perspectives of Scrum Coaches and Scrum Practitioners regarding the frequency of challenges as the fifth result and regarding the importance of challenges as the sixth result
Agile software development practices in Egypt SMEs : a grounded theory investigation
Agile information system development methods have been adopted
by most software development organizations due to their proven benefits in terms
of flexibility, reliability, and responsiveness. However, companies face significant
challenges in adopting these approaches. Specifically, this research investigates
challenges faced by software development companies in Egypt while transitioning
to Agile. As little previous research is available targeting their concerns,
we have conducted a grounded theory investigation. Key problem areas were
found including lack of cadence in sprints planning, inadequate use of effort estimation
and product quality issues.
The developed grounded theory reflects on the key problem areas found with
SMEs adopting agile practices and can be used by software development practitioners
adopting agile methods in Egypt or similar developing countries as an
outline for the common problem areas they are expected to find
Coexisting Plan-driven and Agile Methods: How Tensions Emerge and Are Resolved
Fast changing products, processes, and services caused by digital technologies require organizations to adopt agile methods after having used plan-driven approaches for decades. Adopting agile methods only to software development, can lead to a challenging coexistence of methods. To date, little empirical understanding exists with regard to the difficulties that emerge when organizations introduce agile teams in plan-driven environments. Consequently, we investigate the coexistence of agile and plan-driven methods and study its impacts. We conducted an exploratory multiple case study of four organizations and draw from adaptive structuration theory to study how agile methods are adopted on team level to an environment of deeply entrenched plan-driven methods. We find that this coexistence causes several tensions between agile and plan-driven teams (i.e., budgeting, knowledge, planning, process, responsibility, and cultural tension). Further, we reveal how organizations and teams overcome these tensions with balanced and blended resolutions
“NO ONE CAN DO IT ALL”: THE (CHANGING) ROLE OF EXTERNAL MANAGERS FOR TEAM EMPOWERMENT IN AGILE TEAMS
Agile software development teams require a high degree of team empowerment, but the necessity of these teams to make autonomous decisions and self-organize is at odds with traditional command-and-control management. As more and more organizations adopt agile methods at a large scale, managers can be either a burden or a facilitator in the endeavor to achieve agility. Prior research has extensively studied internal processes of agile teams, but our understanding of the role of team-external managers is limited. In this research, we conducted a case study in five teams in a large organization currently undergoing an agile transformation. We developed a theoretical model of team-external management and its effects on team empowerment. We provide both recommendations for practitioners and a set of hypotheses for empirical testing in future research
On Understanding Preference for Agile Methods Among Software Developers
Agile methods are gaining widespread use in industry. Although management is keen on adopting agile, not all developers exhibit preference for agile methods. The literature is sparse in regard to why developers may show preference for agile. Understanding the factors informing the preference for agile can lead to more effective formation of teams, better training approaches, and optimizing software development efforts by focusing on key desirable components of agile. This study, using a grounded theory methodology, finds a variety of categories of factors that influence software developer preference for agile methods including self-efficacy, affective response, interpersonal response, external contingencies, and personality contingencies. Each of these categories contains multiple dimensions. Preference rationalization for agile methods is the core category that emerges from the data. It informs that while the very essence of agile methods overwhelmingly and positively resonates with software developers, the preference is contingent on external and personality factors as well
- …