Spelling suggestions: "subject:"8oftware teams"" "subject:"5oftware teams""
1 |
Team-RUP an agent-based simulation study of team behavior in software development organizations /Phillips, Jared R. January 2006 (has links) (PDF)
Thesis (M.S.)--Auburn University, 2006. / Abstract. Vita. Includes bibliographic references (ℓ.89-84 )
|
2 |
Supporting group awareness in synchronous distributed groupware framework, tools and evaluations /Tran, Minh Hong. January 2006 (has links)
Thesis (Ph.D) - Swinburne University of Technology, Faculty of Information & Communication Technologies, 2006. / A thesis submitted to Faculty of Information and Communication Technologies, Swinburne University of Technology for the degree of Doctor of Philosophy, 2006. Typescript. Bibliography p. 227-252.
|
3 |
Notification services in a distributed conferencing systemShukla, Swati Patanjali. January 2000 (has links) (PDF)
Thesis (M.S.)--University of Florida, 2000. / Title from first page of PDF file. Document formatted into pages; contains xi, 97 p.; also contains graphics. Vita. Includes bibliographical references (p. 95-96).
|
4 |
Ensuring document security, user coordination, and multimedia synchronization in a prototype groupware suiteDollar, Timothy Wayne, January 1997 (has links)
Thesis (Ph. D.)--Auburn University, 1997. / eContent provider-neutral record in process. Description based on print version record. Includes bibliographical references.
|
5 |
Efficient group membership algorithm for ad hoc networksPradhan, Pushkar P. January 2002 (has links)
Thesis (M.S.)--University of Florida, 2002. / Title from title page of source document. Includes vita. Includes bibliographical references.
|
6 |
Collaboration via aligned autonomy for commercial software teamsKalliamvakou, Eirini 06 November 2017 (has links)
Modern software organizations produce increasingly complex and sophisticated products that build on the effort of multiple individuals and teams. This reality highlights the critical importance of collaboration and the support of its various facets, which are still central concerns for software engineering research and practice. Software organizations also aim to motivate their developers and teams and help them be productive. Knowledge work research highlights the importance of autonomy in work design for satisfaction and happiness. The now pervasive adoption of agile methods and advocacy of self-organization have made autonomy and its challenging practical application a mainstream focus for software engineering research and practice.
Employee autonomy and effective collaboration are thus essential for software companies to motivate developers and help them deliver successful software products. Yet, essential as it might be for organizations to combine them, autonomy and collaboration seem conceptually and practically at odds with one another; is it possible for people or teams that are working together on something be autonomous? One can imagine teams finding it challenging to organize the development work of autonomous developers. Furthermore, on the organizational level it can be difficult to align autonomous agents towards a desirable company strategy. Finally, management may need to be revisited as a function when individuals or teams have autonomy in their work.
Given the complex landscape that software teams are part of in today’s mod- ern organizations, we need to understand how they collaborate in the context of their environment. This dissertation builds on three substantial, diverse case studies based in industry, capturing various ways that several software organizations organize collaborative development work. In the first study I examined how 24 commercial software teams in di↵erent companies organize their development work through their use of GitHub. In the second study I probed how Atlassian scales the practices of its rapidly growing development teams and enacts a culture that keeps them aligned to the strategic goals. In the third study I explored the role of engineering managers at Microsoft and how they support software developers and teams to organize their own work and generate quality outcomes that meet organizational goals. The studies are primarily qualitative and I have used a variety of data collection methods including interviews, observations, documentation review, and surveys.
Tension between autonomy and collaboration surfaced in the studies and it be- came the central challenge I investigate in this dissertation. By understanding the meaning of autonomy for the studied organizations, the definition and characteristics of autonomy evolved and, upon synthesis of the findings, I argue that autonomy is not incompatible with collaboration but rather that the two concepts build on each other.
I articulate and propose a conceptual framework of collaboration via aligned autonomy for software companies in this dissertation. This represents a holistic view of organizations and includes four areas to consider when making autonomy the foundation of collaboration: team collaboration practices, scaling strategies, cultural values, and manager roles. The framework has implications for the study of collaborative software development by proposing to look beyond the combination of independence and coordination as the basis of collaboration. At the same time, the framework can guide commercial software teams and organizations on how to empower development teams, yet not compromise strategic vision. / Graduate
|
7 |
Risk as a Mechanism in Self-Organizing Agile Software Development TeamsThota, Venkata Rama Chaitra January 2017 (has links)
No description available.
|
8 |
Exploring Behavioral Driven DevelopmentHild, Florian-Pascal January 2019 (has links)
Behavior Driven Development (BDD) is a modern agile software development approach that originates from Test Driven Development (TDD) and Acceptance Test Driven Development (ATDD). Other than TDD and ATDD, BDD introduces new methods and strategies that intend to discover the behavior of software in greater detail which is achieved through enhanced communication and cooperation between everyone involved in software projects. In this paper it is examined how BDD can be taken even further and be connected to the products of UX-strategy in order to explore the possibilities to improve internal communication within software project teams. The report guides the reader through the theoretical frameworks of BDD, UX-strategy and Communication and presents suggestions of how BDD and the products UX-strategy can be connected to improve communication and understanding.
|
9 |
The Effects of Uncertainties in Partially Distributed Agile Software Development Teams / Effekterna av Osäkerheter i Delvis Distribuerade Agila MjukvaruutvecklingsteamKlinc, Rebecca January 2018 (has links)
Purpose: The purpose of this study is to identify how uncertainties affect a partially distributed team. To do this, the thesis goes into the details of the different types of uncertainties and how they are handled. Design/Methodology/Approach: This research uses a multiple case study with interviews and observations as data gathering methods. The two cases study are first analyzed separately and then a cross case analysis is conducted. Findings: This study showed that uncertainties are mostly correlated to threats and therefor focus lies on mitigating them. Using agile practices allows for a greater flexibility and makes uncertainties more manageable. Practical implications: This study shows the value of following agile principles. It also shows that when choosing to have a partially distributed team one needs to weigh the negative aspects with the positive ones. Originality/Value: This study combines research conducted on partially distributed teams and uncertainties. / Syfte: Syftet med denna studie är att identifiera hur osäkerheter påverkar ett delvis distribuerat team. För att göra detta går uppsatsen in i detalj om olika typer av osäkerheter och hur de kan hanteras. Design/Metodologi/Ansats: Denna studie använder sig av fallstudier med intervjuer och observationer som datainsamlingsmetoder. Två fallstudier analyseras först separat och därefter genomförs en korsfallsanalys. Resultat: Denna studie visade att osäkerheter mestadels är korrelerade med hot och därför ligger fokus på att förhindra dem. Genom att använda agila metoder möjliggörs större flexibilitet och gör osäkerheter mer hanterbara. Praktisk betydelse: Denna studie visar värdet av att följa agila principer. Det visar också att när man väljer att ha ett delvis distribuerat team måste man väga de negativa aspekterna med de positiva. Orginalitet/Värde: Denna studie kombinerar forskning som utförs på delvis distribuerade team och osäkerheter.
|
Page generated in 0.0583 seconds