To see the other types of publications on this topic, follow the link: Software Team.
Dissertations / Theses on the topic 'Software Team'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Software Team.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Gidlund, Maja. "Measuring feature team characteristics of software development teams." Thesis, KTH, Skolan för datavetenskap och kommunikation (CSC), 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-192371.
Full textAbstract:
This report evaluates the team-structure of three software maintenance teams in order to decide their level of featureness (a term that defines to what extent a team has the quality (the set of characteristics) of being a feature team). Simulations of changes that are expressed as beneficial in an agile environment and that could increase the teams‘ level of featureness within the team structure are performed. The results show that each team‘s level of featureness is affected differently by each change. Partly, this underlines the importance of understanding the current team-structure before implementing changes that aim to increase the level of featureness. And secondly, within the scope of the study, the change where a user expert is declared a team member is concluded as the change that increases the teams‘ level of featureness the most. Based on the results the report also concludes that it is essential to implement changes that affect different, which in combination can increase the level of featureness.
2
Crunk, John. "Examining Tuckman's Team Theory in Non-collocated Software Development Teams Utilizing Collocated Software Development Methodologies." Thesis, Capella University, 2018. http://pqdtopen.proquest.com/#viewpdf?dispub=10929105.
Full textAbstract:
<p> The purpose of this qualitative, multi-case study was to explain Tuckman’s attributes within software development when using a collocated software designed methodology in a non-collocated setting. Agile is a software development methodology that is intended for use in a collocated setting; however, organizations are using it in a non-collocated setting, which is increasing the software errors in the final software product. The New Agile Process for Distributed Projects (NAPDiP) was developed to fix these software errors that arise when using Agile in a non-collocated setting but have not been effective. This research utilized Tuckman's team theory to explore the disparity related to why these errors still occur. The research question asked is how software development programmers explain Tuckman's attributes (i.e., forming, storming, norming, performing) on software development projects. The study adopted a qualitative model using nomothetic major and minor themes in the exploration of shared expressions of sentiments from participants. The study’s population came from seven participants located in the United States and India who met the requirement of using the Agile development methodology and work for organizations on teams with a size of at least thirty individuals from various organizations. A total of seven participants reached saturation in this multi-case study supporting the research question explored. The findings of the research demonstrated that development teams do not meet all stages and attributes of Tuckman’s team development. Future research should explore additional ways that software development teams satisfy a more significant number of Tuckman’s team development stages.</p><p>
3
Yang, Bob 1976. "Managing a distributed software engineering team." Thesis, Massachusetts Institute of Technology, 1998. http://hdl.handle.net/1721.1/50394.
Full textAbstract:
Thesis (M. Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science; and, Thesis (B.S.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 1998.<br>Includes bibliographical references (leaves 97-98).<br>by Bob Yang.<br>B.S.<br>M.Eng.
4
Basava, Shibani. "Supporting team performance---An empirical study of software teams, processes and tools to enhance software development." Connect to online resource, 2008. http://gateway.proquest.com/openurl?url_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:dissertation&res_dat=xri:pqdiss&rft_dat=xri:pqdiss:1453486.
Full text
5
Cavalcante, Marcia Beatriz. "The impact of team software organizations on software quality and productivity." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1998. http://www.collectionscanada.ca/obj/s4/f2/dsk1/tape10/PQDD_0006/MQ44140.pdf.
Full text
6
Gifford, Solomon Stephen. "A Roadmap for a Successful Software Development Team Assembly Model Using Roles." Thesis, Virginia Tech, 2003. http://hdl.handle.net/10919/43109.
Full textAbstract:
Software development requires teams due to size, scope, and location of the project. A few software development team structures have been proposed based on tasks and job descriptions, but no team structure or model has been proposed to assemble software development teams based on individual characteristic and trait differences. This thesis presents two studies that support the argument that a new model needs to be developed for assembling software development teams. A roadmap for developing such a model is presented as the response to the inapplicability of applying current models to software development team assembly.<br>Master of Science
7
Schoenhoff, Peter Klaus. "Belbin's Company Worker, The Self-Perception Inventory, and Their Application to Software Engineering Teams." Thesis, Virginia Tech, 2001. http://hdl.handle.net/10919/36117.
Full textAbstract:
Software engineering often requires a team arrangement because of the size and scope of modern projects. Several team structures have been defined and used, but these structures generally define only the tasks and jobs required for the team. Various process and product metrics seek to improve quality, even though it is generally agreed that the greatest potential benefit lies in people issues. This study uses a team-based personality profiling tool, the Belbin Self-Perception Inventory, to explore the characteristics offered by the Company Worker, one of the team roles defined by Belbin.<br>Master of Science
8
Sudhakar, G. P. [Verfasser]. "The Relationship between Team Climate and Performance in Software Development Teams / G.P. Sudhakar." München : GRIN Verlag, 2020. http://d-nb.info/120337318X/34.
Full text
9
Sudhakar, G. P. [Verfasser]. "The Relationship between Team Climate and Performance in Software Development Teams / G.P. Sudhakar." München : GRIN Verlag, 2019. http://d-nb.info/1203373163/34.
Full text
10
Ahlstrand, Rebecca, and Annie Xu. "Guidelines to improve teamwork in software projects." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-177553.
Full textAbstract:
In consulting firms one of the goals is to have the consultants on an assignment with an external client to bring in capital. In some consulting firms, when the consultants are not on an assignment with a client, they work on internal projects until a new assignment arrives. Since most of the team members do not work for more than a few days or weeks on the projects, it leads to a high team member turnover. In projects with such a turnover, problems such as hasty handovers, unclear roles and responsibilities and low-quality documentation may occur. The purpose of this thesis was to create guidelines to improve teamwork in teams with a high team member turnover. This thesis was based on a case study of a company specializing in information technology and management consulting. To begin to tackle this problem, a literature review was conducted and the data was collected by conducting interviews. The interviews were performed with team members that had been on a project for the longest and shortest period of time in order to identify problems from different perspectives. Based on the interviews and the literature study, guidelines were created to counteract the problems experienced in this type of volatile teams. The guidelines are categorized in four areas: processes, resources, people and long-term perspective. The areas cover the problems experienced and can be ultimately implemented in all teams with high team member turnover to improve teamwork in software projects.<br>I konsultföretag är ett av målen att konsulterna ska vara på uppdrag hos en extern kund för att dra in pengar. I vissa konsultföretag, när konsulterna inte är hos en extern kund, arbetar de på interna projekt tills dess att ett nytt uppdrag kommer. Eftersom de flesta teammedlemmar inte jobbar i mer än några dagar på dessa interna projekt leder det till en hög omsättning av projektmedlemmar. I projekt med den typen av höga omsättning kan problem uppstå som förhastade överlämningar, otydliga roller och skyldigheter samt lågkvalitativ dokumentation. Målet med denna uppsats var att skapa riktlinjer för att förbättra lagarbete i teams med hög omsättning av projektmedlemmar. Denna uppsats var baserad på ett fallstudie på ett företag som är specialiserat på informationsteknik och management consulting. För att börja tackla detta problem utfördes en litteraturstudie och data samlades in genom intervjuer. Intervjuerna utfördes med de teammedlemmar som har deltagit i projektet längst respektive kortast tid, för att identifiera problemen utifrån olika perspektiv. Baserat på intervjuerna och litteraturstudien, skapades riktlinjer för att motverka dessa problem som uppstår i sådana typer av rörliga team. Riktlinjerna kan kategoriseras i fyra områden: processer, resurser, människor och långtids perspektiv. Dessa områden täcker de upplevda problemen och kan implementeras av teams som har hög omsättning av medlemmar för att förbättra arbetet inom teamet i mjukvaruprojekt.
11
Alhabashneh, Mohammad Abad Alhameed. "Protect team handler (PTH)." Thesis, University West, Department of Technology, Mathematics and Computer Science, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-567.
Full textAbstract:
<p>There is always a need for easy-to-follow processes that enable accurate and non-time consuming solutions. Nowadays we see a lot of different approaches to development processes in software engineering. This project is concerned with how to manage a software development process in a reliable, secure and efficient way. Software is available which provides some help for project managers / administrators to work more productively, with effective communication. Using such systems, it is possible to keep track of all the phases of development, including task distribution, making maximum use of previous hands-on experience and increasing productivity, to deliver a finished product in minimum time. No existing solution, however, fulfills all the desirable criteria. This paper describes the motivation, design and implementation of an improved development management system using Active Server Pages and Microsoft Internet Information Services with a backend Microsoft Access Database developed using a waterfall software development process. The resulting system is described and evaluated. This system will be beneficial for software houses, because they can communicate on the web, allowing efficiency gains by avoiding the need to call meetings for distribution of tasks among employees, with the additional advantage of location-transparent team management through the Internet.</p>
12
Kuziwa, Ally, and Kazibwe Flavia Ndagire. "Application of Agile Methods in Distributed Software Development." Thesis, Umeå universitet, Institutionen för informatik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-122495.
Full textAbstract:
Agile software development methods are characterized by developer’s empowerment through self-organization, incremental requirements and constant knowledge sharing. Despite some effort to elaborate how successfully agile methods can be applied in co-located development teams, little is known on how the same is done when the development teams are distributed. Our research focus is to uncover factors that influence the successful application of agile methods in distributed development teams using a software development company as our case study. With three distributed teams applying different agile methods, we conducted focused ethnography alongside interviews to comprehend what and how various factors under distributed development teams influence successful agile methods application. It seems, all that matters is team structure, team spirit, effective communication, product requirements, and knowledge sharing. The team structure has more influence than other factors and therefore our suggestions for successful application of agile methods in distributed software development is to focus on the development team, above all factors. The analysis shows that the development methods themselves have little to do with the successful application of agile methods in distributed software development teams.
13
Mehta, Nikhil Byrd Terry Anthony. "Knowledge integration in software teams an analysis of team, project, and IT-related issues /." Auburn, Ala., 2006. http://repo.lib.auburn.edu/Send%2012-15-07/MEHTA_NIKHIL_1.pdf.
Full text
14
Alhabashneh, Mohammad Abad Alhameed. "Project and team handler (PTH)." Thesis, Högskolan Väst, Institutionen för teknik, matematik och datavetenskap, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-567.
Full textAbstract:
There is always a need for easy-to-follow processes that enable accurate and non-time consuming solutions. Nowadays we see a lot of different approaches to development processes in software engineering. This project is concerned with how to manage a software development process in a reliable, secure and efficient way. Software is available which provides some help for project managers / administrators to work more productively, with effective communication. Using such systems, it is possible to keep track of all the phases of development, including task distribution, making maximum use of previous hands-on experience and increasing productivity, to deliver a finished product in minimum time. No existing solution, however, fulfills all the desirable criteria. This paper describes the motivation, design and implementation of an improved development management system using Active Server Pages and Microsoft Internet Information Services with a backend Microsoft Access Database developed using a waterfall software development process. The resulting system is described and evaluated. This system will be beneficial for software houses, because they can communicate on the web, allowing efficiency gains by avoiding the need to call meetings for distribution of tasks among employees, with the additional advantage of location-transparent team management through the Internet.
15
Haraldsen, Lars Martin Riiser. "An Investigation of Team Effectiveness in Agile Software Development." Thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2012. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-18902.
Full textAbstract:
Abstract Agile teamwork has been widely used and accepted in today's industry of software development. The methods in agile teamwork claim to improve performance and predictability, and has during the past years become the target for an emerging area of research. The majority of the existing studies concerning agile teamwork mainly focus around eXtreme Programming (XP). Abstract This report is one of few that discuss teamwork in software development having the agile methodology “Scrum” in the main focus. The report focus on teamwork and team effectiveness. It discuss existing literature concerning Scrum and teamwork as well as showing the results from an observed ethnographically informed study of an agile project. All findings, challenges and opportunities, are analyzed and compared to theories around teamwork. The primary literature used are case studies about Scrum conducted in the past five years. Some descriptive literature is also used to support my findings. Abstract My main results are that solid leadership and members willing to adapt are of great importance. I also found that working in a closed room together facilitates teamwork and can increase team effectivenes. My teamwork model and framework for this project might not be completely optimal for this specific observed project. Overall, I have found that Scrum can be hard to adapt to. However, the agile practices facilitates team effectiveness. In addition, my results show that Scrum guidelines support communication and adaptability.Abstract Ultimately, it is interesting to see what can be improved in agile methods and to what extent team effectiveness changes.Abstract Keywords: Agile development, Scrum, Teamwork, Team effectiveness, Team performance
16
Nazir, Qamar, and Khurram Shahzad. "Training Communication and Self Organization in a Team Training Environment." Thesis, Linköping University, Department of Computer and Information Science, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-52439.
Full textAbstract:
<p>C3Fire is a micro-world that provides the simulation system, which is use to improve team management skills in fully controlled enviroment. C3Fire system can be used in research process where researcher can select some characteristics of the real world and create the well controlled simulation system. Training is used for developing skills to tackle with emergency situation. The purpose of our thesis is to develop and test, Communiacation and Self Organization cofigurations in a team training environment. Success of dealing with emergency management situation mostly depends on these training factors. In the first step we had studied different theories and research work relevant to Communication and Self Organization. In second step we studied the structure of the C3Fire then we developed different configurations based on communication and self-organization. In third step we test these training session with the real world participants. Finally we analyze the behavior of the participants while playing the game.</p>
17
Bapir, Sivan, and Kajany Varatharajah. "Leading Learning: A managerial perspective on promoting team learning in a software development company." Thesis, KTH, Industriell Management, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-148829.
Full textAbstract:
Fast pace of change in the business of technology is the reality of many organizations today. The software development industry is one example where this nature is prominent. Companies need to adapt in ways that eases the persistence against change from external forces. Companies need to turn into Learning Organizations as these help people and organizations embrace change. Two key components of the Learning Organization are the teams, as they are considered to be the fundamental units of organizations, and managers, as they have the biggest impact on facilitating learning in the organization. Therefore, this study has investigated how managers could act to create conditions for encouraging team learning of a software development company to become a Learning Organization. This has been done by conducting a case study at the company Ericsson in Kista, Sweden, who is market leaders within the software development industry. The case design consisted of a two phase method that included both a quantitative and qualitative data collection method. The results indicate that Ericsson could be classified as a Learning Organization and in addition display promising characteristics when it comes to having team learning capabilities. Furthermore, the findings suggest that in order for managers to encourage team learning they should take on a coaching and supporting role to understand the need of the teams; challenge the status quo; empower teams through giving them mandate; allocate time for learning as an integral part of the daily work; and reward learning in teams. The findings of this study have implications both in a theoretical aspect and a sustainability aspect. From the theoretical aspect, the findings provide with further empirical data in a field that is currently dominated by theoretical literature. Furthermore, the findings display a practical example of how managers of a market leading company with promising characteristics of team learning capabilities have acted to create such conditions. From a sustainability aspect, the results of this study give firms a sustainable competitive advantage through increased business performance, healthy labor conditions that are a result of healthy team dynamics and possible encouragement to future attention towards emphasis on environmental aspects.
18
Brooks, Ian Robert. "SEM Predicting Success of Student Global Software Development Teams." Thesis, University of North Texas, 2015. https://digital.library.unt.edu/ark:/67531/metadc799549/.
Full textAbstract:
The extensive use of global teams to develop software has prompted researchers to investigate various factors that can enhance a team’s performance. While a significant body of research exists on global software teams, previous research has not fully explored the interrelationships and collective impact of various factors on team performance. This study explored a model that added the characteristics of a team’s culture, ability, communication frequencies, response rates, and linguistic categories to a central framework of team performance. Data was collected from two student software development projects that occurred between teams located in the United States, Panama, and Turkey. The data was obtained through online surveys and recorded postings of team activities that occurred throughout the global software development projects. Partial least squares path modeling (PLS-PM) was chosen as the analytic technique to test the model and identify the most influential factors. Individual factors associated with response rates and linguistic characteristics proved to significantly affect a team’s activity related to grade on the project, group cohesion, and the number of messages received and sent. Moreover, an examination of possible latent homogeneous segments in the model supported the existence of differences among groups based on leadership style. Teams with assigned leaders tended to have stronger relationships between linguistic characteristics and team performance factors, while teams with emergent leaders had stronger. Relationships between response rates and team performance factors. The contributions in this dissertation are three fold. 1) Novel analysis techniques using PLS-PM and clustering, 2) Use of new, quantifiable variables in analyzing team activity, 3) Identification of plausible causal indicators for team performance and analysis of the same.
19
Wang, Tingting. "Multi-agent team competitions and the implementation of a team-strategy." HKBU Institutional Repository, 2006. http://repository.hkbu.edu.hk/etd_ra/772.
Full text
20
Stevens, K. Todd Jr. "The Effects of Roles and Personality Characteristics on Software Development Team Effectiveness." Diss., Virginia Tech, 1998. http://hdl.handle.net/10919/30389.
Full textAbstract:
The objective of this research is to show the utility of roles and personality characteristics to the evaluation and formation of software development teams. The goals of this research include demonstrating empirically that Belbin's team roles can be used to form and evaluate software teams, providing a partial validation of the analyses by using the Belbin roles to analyze teams from the software industry, and comparing the personality data collected for this research to data from two previous studies and to the general population.
In the highly competitive software industry, improving the software development process can be critical to a company's success. More specifically, improving a team's productivity can save employers significant time and money. This investigation addresses the productivity of software development teams in a series of studies. First, controlled studies empirically show that Belbin's roles can be used in team formation to improve team performance. Second, additional studies, both qualitative and quantitative, demonstrate that Belbin's roles can be used as criteria in team evaluation and formation. Finally, teams from the software development industry are evaluated, providing a partial validation of the usefulness of Belbin's roles to software teams.
The cumulative effect of the results of the studies in this investigation demonstrate that Belbin's roles can be used effectively in team formation and evaluation. Specifically, Belbin's roles for leadership and innovation are shown in empirical studies to be important in the formation of software teams, and all of the Belbin roles are used in the evaluation of teams in academia as well as in industry. The results of this investigation should be used in team formation and evaluation, in an academic setting as well as in the software development industry. For team evaluation, deficiencies uncovered in the Belbin roles should be remedied, and positive aspects should be encouraged. In team formation, teams should contain the complement of Belbin roles and should specifically contain the leadership and innovation roles focused on as part of this investigation. It is clear from this investigation that Belbin's roles can be used effectively to improve software development teams.<br>Ph. D.
21
Tornberg, Peder. "Self-organizing Distributed Team : Working agile and effective." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-16182.
Full textAbstract:
In order for a software development team to be successful, cost effective and perform effectively the team needs to coordinate and communicate sufficiently in order to compensate for the obstacles that a distributed team face. The focus of this report is to observe a distributed team as they try to overcome the obstacles that a distributed team face when it comes to coordination and collaboration. The team is being observed as they try to overcome those obstacles while working on a project for a client in another country. Methods, processes and tools are introduced in order for the team to become a self-organizing distributed team that works agile and effective. With the team being observed throughout the course of the project and the literature review on the subject, this report will analyze the team and the methods used in order to come to a conclusion on what enables a distributed team to become a self-organizing team that works agile and effective in a international market. There are obstacles that a distributed self-organizing team face. With efficient communication methods and tools for coordination the team can become a strong self-organizing team that works agile and productive.
22
Wani, John Rubena. "Project Managers’ Communication Strategies for Team Collaboration in Software Development." ScholarWorks, 2019. https://scholarworks.waldenu.edu/dissertations/7769.
Full textAbstract:
Effective communication among team members in software development projects is increasingly significant for the success of the project. Successful software projects are the catalyst for achieving profitability objectives and creating shareholder value in organizations. The purpose of this single case study was to investigate communication strategies information technology (IT) project managers used for successful team collaboration in software development. The population for this study comprised senior IT project managers. The project managers had supervision responsibilities from a midsized IT company in Alberta, Canada. The sociotechnical theory guided this study as the conceptual framework. Data were collected from semistructured interviews with 13 senior IT project managers on their experiences using effective communication strategies for team collaboration. A review of 11 company documents was conducted. Using methodological triangulation and member checking of original interview transcripts served to establish the trustworthiness of final interpretations. Through thematic analysis, 4 significant themes emerged from the study: effective communication, attributes of communication, the importance of social and emotional intelligence, and the impact of postwork activities for team collaboration. The findings of this study might bring about positive change by supporting senior project managers use of communication strategies for team collaborations in midsize IT companies to increase job satisfaction and project completion.
23
Seppänen, P. (Pertti). "Balanced initial teams in early-stage software startups:building a team fitting to the problems and challenges." Doctoral thesis, Oulun yliopisto, 2018. http://urn.fi/urn:isbn:9789526219493.
Full textAbstract:
Abstract The rapid development of digital technology and software in recent years has created great variety of totally new business opportunities. Software startups are commonly considered to be the fastest in exploiting the new opportunities and the most innovative in creating new products and services. At the same time, software startups are often small, immature enterprises with limited resources and inexperienced teams. The initial team plays a key role in the early stages of a software startup. This research focuses on the initial team from the perspective of human capital – the knowledge, experiences, skills, and other cognitive abilities. It studies the initial team empirically, utilizing the multi-case study and triangulation methods applying the human capital, resource-based view, capability, and the opportunity discovery and creation theories. The empirical data were gathered from thirteen software startups in Italy, Norway and Finland, and from a student experiment. From the analysis of this data, a generic structure of a software startup’s initial team was identified, consisting of three different roles, with each having a specific human capital profile. This team structure sought a balance between the team’s human capital and problems and challenges to be solved. The level of the initial human capital of the team and the means to strengthen it varied, and affected the progress of the work in the studied startups. Though the components of the team’s human capital were not rare and inimitable in terms of the resource-based view, building a balanced startup team created a unique and task-specific setup, which is a key capability of a software startup. The balanced startup team structure is proposed to be the generic human capital model of a software startup’s initial team<br>Tiivistelmä Digitaalitekniikan ja ohjelmistojen nopea kehitys viime vuosina on synnyttänyt suuren joukon kokonaan uusia liiketoimintamahdollisuuksia. Ohjelmistostartup-yrityksiä pidetään yleisesti nopeimpina hyödyntämään uusia mahdollisuuksia ja erityisen innovatiivisina luomaan uusia tuotteita ja palveluita. Kuitenkin samalla, ohjelmistostartup-yritykset ovat usein pieniä, kehityksensä alussa olevia yrityksiä, joilla on pienet resurssit ja kokematon henkilökunta. Varhaisen vaiheen ohjelmistostartup-yrityksissä alkutiimin merkitys on keskeinen. Tässä tutkimuksessa tarkastellaan alkutiimiä inhimillisen pääoman, osaamisen, kokemuksen ja taitojen, näkökulmasta. Tutkimuksessa tarkastellaan alkutiimiä kokeellisesti, käyttäen monitapaustutkimuksen ja triangulaation menetelmiä ja soveltaen inhimillisen pääoman, resurssipohjaisen näkemyksen, kyvykkyyden ja liiketoimintamahdollisuuksien hyödyntämisen teorioita. Kokeellinen tutkimusaineisto on kerätty kolmestatoista yrityksestä Italiasta, Norjasta ja Suomesta ja yhdestä opiskelijoilla tehdystä kokeellisesta tutkimuksesta. Tutkimuksessa löydettiin alkutiimin yleinen malli. Mallissa on kolme roolia, kullakin oma inhimillisen pääoman profiili. Mallissa on tiimin inhimillisen pääoman ja ratkaistavien ongelmien tasapaino. Tiimien inhimillisen pääoman määrä ja sen kehitystavat vaihtelivat, ja vaikuttivat tutkittavien yritysten edistymiseen. Vaikka alkutiimien inhimillisen pääoman komponentit eivät olleet ainutkertaisia resurssipohjaisen näkemyksen kannalta, tasapainossa olevan alkutiimin rakentaminen synnytti ainutkertaisen, tehtävänmukaisen tiimirakenteen, jota voidaan pitää yrityksen keskeisenä kyvykkyytenä. Havaittu tiimirakenne esitetään yrityksen alkutiimin inhimillisen pääoman yleiseksi malliksi
24
Jiarou, Huang, and Ye Sigewei. "The management differences between self-organizing team and traditional team: Focus on communication and coordination." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-18867.
Full text
25
Ögren, Mikael, and Ludwig Wikblad. "En testprocess för webbutvecklingsprojekt med små team." Thesis, Linköpings universitet, Programvara och system, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-138125.
Full textAbstract:
Att hitta ett lämpligt tillvägagångssätt för att utföra testning i små utvecklingsteam är en utmaning. Många små företag upplever traditionella testprocesser och testförbättringsprocesser som alltför resurskrävande. Minimal Test Practice Framework (MTPF) är ett ramverk för testning vars syfte är att tillhandahålla ett minimalistiskt tillvägagångssätt för testförbättring. Målet med denna studie var att undersöka hur MTPF kan implementeras och anpassas till ett litet utvecklingsteam utan att den medför en för stor tidsinvestering. Studien utfördes på avdelningen Webb \& Mobilt i företaget Exsitec där team om 2-6 personer utvecklar webbapplikationer till företagskunder. I nära samarbete med utvecklarna på avdelningen togs en testprocess fram med målet att den skulle anpassas till verksamheten i så stor utsträckning som möjligt. Studien genomfördes som aktionsforskning i tre faser utefter Cooperative Method Development i ett projekt med två utvecklare. Under studiens första fas intervjuades alla utvecklare på avdelningen för att skapa en grundförståelse för verksamheten. Under den andra fasen togs ett antal förbättringsförslag fram tillsammans med utvecklarna. Under den tredje fasen infördes och utvärderades dessa förbättringar. Genom att fokusera på enhetstestning av central affärslogik i applikationen uppnåddes en testprocess som gav utvecklarna ett ökat förtroende för kodens kvalitet utan att upplevas som för resursintensiv.<br>Finding a suitable approach for testing in small development teams is a challenge. Many small companies view traditional test processes and test process improvement models as too resource intensive for their needs. Minimal Test Practice Framework (MTPF) is a framework for testing which purpose is to provide a minimalistic approach to test improvement. The goal of this study was to examine how MTPF can be adapted to a small development team without incurring a time cost that the team would experience as too high. The study was performed in the department Web \& Mobile of the company Exsitec. At the department teams of 2-6 people develop web applications to business customers. During the study a testprocess was developed in close cooperation with the developers of the department with the aim of adapting it as well as possible to the needs of the department. The study was performed as action research in three phases, according to the method Cooperative Method Development, in a project with two developers. During the first phase all developers in the department were interviewed to establish an understanding of the environment for the study. During the second phase a set of possible improvements was developed together with the developers. During the third phase some of these improvements were implemented and evaluated. By focusing on unit testing central business logic in the application the developed test process improved the developers confidence in the code quality without being perceived as too resource intensive.
26
Sabatino, Alessandro. "Un software collaborativo per la gestione delle attività di un team." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2019. http://amslaurea.unibo.it/19081/.
Full textAbstract:
La tesi in questione descrive lo sviluppo di un software collaborativo che faciliti l’interazione fra i collaboratori e lo svolgimento delle mansioni loro assegnate, caratterizzanti delle responsabilità in termini funzionali. Un “groupware” che racchiuda la gestione della conoscenza, la condivisione delle informazioni utili nel contesto cooperativo di un sito web ed il flusso di attività (da analizzare sotto differenti punti di vista) e documenti vagliati dall’amministratore nonché costituenti un workflow system.
L’elaborato prevede la descrizione delle caratteristiche del dominio applicativo (gestione collaborativa di un sito web) con conseguente specifica dei requisiti ed analisi del problema (modellato attraverso il linguaggio UML), per poi approcciarsi alla progettazione (basata sul paradigma ad oggetti e con annessa definizione di workflow collaborativi e mockup formati in seguito alla discussione con un focus group). Completano il documento l’implementazione (di un’applicazione mobile per piattaforma Android) e le tecnologie utilizzate (da quelle caratterizzanti il corso di studi passando per un background personale implicante la conoscenza di WordPress, diagramma GANTT ed il linguaggio YAWL). Infine le conclusioni (sezione dedicata anche a possibili migliorie ed aggiornamenti futuri).
27
Rogers, Neal L. Umphress David A. "Discrete event role playing simulation of small team software engineering projects." Auburn, Ala., 2006. http://repo.lib.auburn.edu/2006%20Summer/Dissertations/ROGERS_NEAL_18.pdf.
Full text
28
Birtle, Malcolm. "Developing learner autonomy and process improvement in software engineering team projects." Thesis, Lancaster University, 1996. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.337459.
Full text
29
Freudenberg, Sallyann. "The 'tag team' : tools, tasks and roles in collaborative software development." Thesis, University of Sussex, 2006. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.436393.
Full text
30
Matinolli, I. (Ilari). "Designing, implementing and evaluating a database for a software testing team." Master's thesis, University of Oulu, 2016. http://urn.fi/URN:NBN:fi:oulu-201612033204.
Full textAbstract:
Databases have existed since 1960s. Relational databases came out in 1970s and they have been the most popular database technology ever since. However, non-relational databases came out in 2000s and have gathered popularity since then. This thesis studied different open-source database management systems including relational and non-relational systems. Prompt looks into data analytics and distributed databases were also taken.
The main purpose of this study was to design, implement and evaluate a new database for the needs of a software testing team. In order to do that it was needed to find out a database management system that met the requirements best given by the case company. It was also needed to find out which database design principles and techniques should be followed to achieve a well-performing and easily maintainable database.
After studying different database management system, MySQL was chosen for the database management system and a new database was designed, implemented and evaluated. It turned out that MySQL is still a relevant and successful database management system to meet the needs of a modern software testing team when optimization techniques such as indexing and normalization are applied.
In the future it would be beneficial to study how a non-relational database management system could be combined with a relational database management system to meet the needs of different software testing teams.
31
Saxton, Dominic Martinelli. "Relationship Between Software Development Team Structure, Ambiguity, Volatility, and Project Failure." ScholarWorks, 2018. https://scholarworks.waldenu.edu/dissertations/6277.
Full textAbstract:
Complex environments like the United States Air Force's advanced weapon systems are highly reliant on externally developed software, which is often delivered late, over budget, and with fewer benefits than expected. Grounded in Galbraith's organizational information processing theory, the purpose of this correlational study was to examine the relationship between software development team structure, ambiguity, volatility and software project failure. Participants included 23 members of the Armed Forces Communications and Electronics Association in the southeastern United States who completed 4 project management surveys. Results of multiple regression analysis indicated the model as a whole was able to predict software project failure, F(3,19) = 10.838, p < .001, R2 = 0.631. Software development team structure was the only statistically significant predictor, t = 2.762, p = .012. Implications for positive social change include the potential for software development company owners and military leaders to understand the factors that influence software project success and to develop strategies to enhance software development team structure.
32
Long, Rick, and Peter Crump. "SOFTWARE QUALITY AND PRODUCTIVITY: ARE THEY COMPATIBLE?" International Foundation for Telemetering, 1999. http://hdl.handle.net/10150/608443.
Full textAbstract:
International Telemetering Conference Proceedings / October 25-28, 1999 / Riviera Hotel and Convention Center, Las Vegas, Nevada<br>Many view quality and productivity as competing concepts. After all, doesn’t high software quality come at a high cost? Doesn’t it mean that a large amount of "extra stuff" needs to be done during the software development cycle? And, doesn’t that mean that software productivity takes a back seat to (and a major hit from) quality efforts? This paper will explore these issues. This paper provides some preliminary data that supports how a disciplined software engineering process can (and has) resulted in high quality software while actually increasing productivity. Data has been gathered on organizations that have a disciplined, quality-oriented software engineering process in place. That data shows that quality and productivity can (and do) coexist. The data will be discussed along with an explanation of how these results can be achieved.
33
Juhlin, Annica. "Scrum master in a global distributed development team." Thesis, Blekinge Tekniska Högskola, Avdelningen för för interaktion och systemdesign, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4927.
Full textAbstract:
Companies around the world work more globally than ever and it reflects in the system development projects that run. The companies work span continents and the employees work together over the borders. This way of working, the global distributed, brings a number of opportunities for the company but also presents a lot of problems. The distributed way of working means that the teams and/or individuals are divided. I wanted to connect this way of working with the agile framework Scrum, partly due to my own interest on the subject and partly as it is a contradiction to me, distributed work and Scrum, therefore a challenge to combine. To be able to investigate this way of working I got in touch with two companies that work globally and distributed, using the Scrum technique, I read literature and papers on the subject to be able to reach my conclusions. My conclusions are based on the success factors I found in both the literature and the dialogs performed. The study shows three important qualities in a leader, a scrum master, in a globally distributed development team: Coaching leadership, clear leadership and smaller distributed teams not individuals.
34
Alkandari, Mohammad A. "A Model of Multicultural Software Project Team Management applied in Requirements Engineering." Diss., Virginia Tech, 2012. http://hdl.handle.net/10919/26808.
Full textAbstract:
In today's world of global software teams, managing members from multiple countries and cultures adds to an already complex mix of software productivity issues. While software team compositions have been researched based on tasks, personality, and role descriptions, few models exist to help software project managers reason about software teams with respect to culture. As more culturally diverse teams develop software products, software project managers need to manage teams based on cultural factors that will inevitably arise. This research examines the effect of culture on software project team management, and its impacts on software productivity, especially as it pertains to requirements engineering tasks. The main objective is to investigate how individuals from different cultures work together in software development projects, and to use that understanding to formulate a model for reasoning about key cultural factors. Communication is a critical part of software project team effectiveness. Hence, this research examines how cultural factors (e.g., language, attitudes, roles, social organization, and time) affect the communication process in software development projects. Based on an initial survey of multicultural teams, this research examines some of the issues that arise from diverse teams working together. The survey results led to language and attitudes as dominant aspects of communication that impact software productivity. Time, roles, and social organization also had considerable influence from the preliminary results. From these results, the research approach was refined and more specific survey instruments were designed to aid in identifying the critical factors that impact software productivity. The results of the second set of the surveys showed that various cultures have different attitudes and behaviors, which in turn have distinct impacts on productivity in terms of more rework and delay. Furthermore, multicultural teams have miscommunication issues with respect to differences in languages, attitudes, roles, time, and social organization. The effect of some cultural factors on communication and productivity vary from culture to culture. Based on the results of the surveys, a model for Multicultural Software Project Team Management is described. This model was substantiated with further surveys using software professionals with experience working on multicultural teams.<br>Ph. D.
35
Alkandari, Mohammad A. "Investigation into Cultural Aspects, Personality, and Roles of Software Project Team Configuration." Thesis, Virginia Tech, 2006. http://hdl.handle.net/10919/35837.
Full textAbstract:
Managing software engineering teams in a systematic, controlled, and efficient manner often results in higher quality software. Today, with around the clock software development, software teams consist of members from geographically different locations and a variety of cultures. A few software development team compositions have been presented based on tasks, personality, and role descriptions. While these have been shown effective for understanding software teams and to some extent predicting favorable team configurations, there are no team structures or models to configure software development teams based on cultural aspects. Therefore, this thesis proposes a model for assembling software teams based on roles, personality, and cultural profiles. In particular, this research investigates how the Belbin and Myers-Briggs model, and Keirsey theories could be applied effectively to software development teams based on previous studies and analysis conducted in this study. Moreover, the study not only explores the relationship between Belbin roles and Myers-Briggs personality types, but examines how cultural differences with respect to their values and other project influences could be mapped successfully into the team profiles.<br>Master of Science
36
Zlatkovic, Samireh Jalali and Branislav. "Success Factors in Building and Maintaining Trust Among Globally Distributed Team Members." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2084.
Full textAbstract:
Globalization trends have affected many software organizations in the past years. They are turning towards global software development (GSD) market in search for quality with a lower price and shorter development times. It turns out that certain management methods used for in-house development are not applicable in GSD, often resulting in a failed project. It is believed that trust is one of the key factors for success or failure of such projects. In the first part, this thesis studies the causes of lacking or losing trust in globally distributed teams though a literature review and systematic review of current research. The second part of this thesis studies the practices which have been applied in industry to prevent or minimize the impact of trust related issues. Finally these practices are mapped to the identified issues, resulting in a set of recommendations for managers involved in GSD.
37
Heinstedt, Elin, and Niklas Johansson. "Requesting Utility in Usability -Perspectives from a large team software engineering project." Thesis, Blekinge Tekniska Högskola, Institutionen för arbetsvetenskap och medieteknik, 2001. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4960.
Full textAbstract:
Many companies invest large amount of money in developing new technology, without knowing how it will be used. To succeed in making these technologies useful it is necessary to understand the context that gives meaning to the artifact. In the case of generic products, especially in new domains, the context is not obvious. This bachelor thesis analyses what Usability Engineering, Participatory Design and Ethnography can contribute to the problem of learning about the context of usage for generic artifacts. Understanding and identifying details of context is considered to be important to achieve usability in software development. The experience is that most recommendations on usability methods concern situations of specific users in a specific context. In order to find important aspects of the real-world use of generic products, we suggest that ethnographic studies can be conducted in contexts where behaviors relevant to the design are thought to be found. The problem of not knowing the context was experienced in usability work practiced in a large software engineering project. The project task was to develop a web browser for Symbian's ?Quartz? reference design for handheld devices. Methods used were taken from participatory design and usability engineering.
38
Xie, Xusong 1975. "An empirical study of the coordination in a distributed software development team." Thesis, Massachusetts Institute of Technology, 2004. http://hdl.handle.net/1721.1/28633.
Full textAbstract:
Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Civil and Environmental Engineering, 2004.<br>Includes bibliographical references (p. 89-92).<br>As today's software systems become more and more complicated, coordinating the development of such systems has been an important factor to their successful implementation. The need for good coordination is especially important when the development team is geographically distributed and has to rely on information and communication technologies to support its activities. With limited available coordination mechanisms, distributed software teams need to carry out a set of coordination functions effectively throughout the software development process. In addition, in response to the changes in context and task, distributed software teams needed to be adaptive in their coordination. In this study, I try to understand how different coordination methods and tools could serve the changing coordination needs in software development through an empirical study of a distributed software team's practice.<br>by Xusong Xie.<br>S.M.
39
Sedano, Todd. "Sustainable Software Development: Evolving Extreme Programming." Research Showcase @ CMU, 2017. http://repository.cmu.edu/dissertations/837.
Full textAbstract:
Context: Software development is a complex socio-technical endeavor that involves coordinating different disciplines and skill sets. Practitioners experiment with and adopt processes and practices with a goal of making their work more effective. Objective: To observe, describe, and analyze software development processes and practices in an industrial setting. Our goal is to generate a descriptive theory of software engineering development, which is rooted in empirical data. Method: Following Constructivist Grounded Theory, we conducted a 2.5 year participant-observation of eight software projects at Pivotal, a software development company. We interviewed 33 software engineers, interaction designers, and product managers, and analyzed one year of retrospection topics. We iterated between data collection, data analysis and theoretical sampling until achieving theoretical saturation and generating a descriptive theory. Results: 1) This research introduces a descriptive theory of Sustainable Software Development. The theory encompasses principles, policies, and practices aiming at removing knowledge silos and improving code quality, hence leading to development sustainability. 2) At the heart of Sustainable Software Development is team code ownership. This research widens our understanding of team code ownership. Developers achieve higher team code ownership when they understand the system context, have contributed to the code in question, perceive code quality as high, believe the product will satisfy the user needs, and perceive high team cohesion. 3) This research introduces the first evidence-based waste taxonomy, identifying eight wastes along with causes and tensions, and compares it with Lean Software Development’s waste taxonomy. Conclusion: The Sustainable Software Development theory refines and extends our understanding of Extreme Programming by adding principles, policies, and practices (including Overlapping Pair Rotation) and aligning them with the business goal of sustainability. One key aspect of the theory is team code ownership, which is rooted in numerous cognitive, emotional, contextual and technical factors and cannot be achieved simply by policy. Another key dimension is waste identification and elimination, which has led to a new taxonomy of waste. Overall, this research contributes to the field of software engineering by providing new insights, rooted in empirical data, into how a software organization leverages and extends Extreme Programming to achieve software sustainability.
40
Ali, Asif, and Faheem Ramzan. "Analysis and Monitoring of Team Collaboration in Emergency Response Training supported by a Web Based Information Management System." Thesis, Linköping University, Department of Computer and Information Science, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-52078.
Full textAbstract:
<p>Our objective in this thesis work is to analyze and manage the log files which are generated after a number of experiments series on different groups using C3Fire simulation environment. It includes analyzing and extracting information from log files, and then maintaining this information in a database. This should be presented with a web interface through ICEfaces Ajax framework for Java. Log Files are generated after a number of experiments series on the different groups. All sequences and information related to task performed by team in group is organized in session log files. The work is divided into different steps; first step is to analyze and extract data from log files, and properly arrange it in several different tables in a database, for this MySQL database is used to store the information. The web interface of log file management system is implemented using ICEfaces Ajax framework, and is based on the statistics of log files generated from the C3Fire environment. User would be able to add/remove the log files, also can view or edit the details of each session log file in database through web interface. Different events can be generated, and logged for the session information.</p><p>C3Fire is an environment that supports training and research in team collaboration. The environment is mainly used in command, control and communication research, and in training of team decision making. Many humanitarian relief operations are doing their work without having any practice. When some disaster events occur, they cannot perform their jobs effectively. Effective and efficient relief operation is the need of humanity; even that’s not enough to move teams to the disaster place at right time; communication and co-ordination among the team members is the big factor to make effective and well-organized work. C3Fire is a simulation system which provides the training for team members to handle such type of disaster events, and makes the work more proficient at that time by doing effective coordination.</p>
41
Zelazny, Lucian M. "Toward a Theory of Information System Development Success: Perceptions of Software Development Team Members." Diss., Virginia Tech, 2011. http://hdl.handle.net/10919/28014.
Full textAbstract:
This dissertation increases our understanding of information system project success by investigating how software development team members define the success of an information system development effort. The theoretical model of ISD success is developed and tested. ISD success is measured through the eyes of the software development team membersâ since they are the most influential stakeholders during the development of the system.
This dissertation was conducted in two phases: 1) theory building and 2) theory testing. The theory building phase began with a thorough literature review. Semi-structured interviews were conducted and the data analyzed to add emergent concepts to the model. The result of the theory building phase is the theoretical model of ISD success.
The theory testing stage began with the development and validation of a survey instrument to measure the constructs and subconstructs found within the theoretical model of ISD success. Data was collected and the model tested using partial least squares regression. The findings indicate that software development team members view ISD success as being composed of process quality, functional product quality, non-functional product quality, team member benefits, and team member satisfaction. Team member satisfaction is highly influenced by team member benefits, moderately influenced by functional product quality and slightly influence by non-functional product quality and process quality.
Software development team members view process quality as being composed of within budget and process maturity; non-functional product as being composed of reliability, usability, testability, and efficiency; team member benefits as being composed of learning and teamwork; and team member satisfaction as being composed of product satisfaction, process satisfaction, and personal satisfaction. Software development team members do not view on time as a significant contributor to their definition of process quality; they do not view modifiability, portability, or reusability as significant contributors to their definition of non-functional product quality; and they do not view recognition as a significant contributor to team member benefits.<br>Ph. D.
42
Myhill, Carl. "Facilitating the comprehension of human-computer interaction design intent within a software team." Thesis, Cranfield University, 1998. http://hdl.handle.net/1826/825.
Full textAbstract:
A large proportion of today’s software development is unsuccessful. One reason for
this is thought to be lack of attention to the user. Maintaining a user-centred focus
during software production is regarded as a major problem. Introducing an HCI
designer role into the software team (they usually function as external advisors) is
thought to be a means of addressing this problem.
Issues surrounding the introduction of an HCI designer role into software teams were
explored by a qualitative investigation. Participant-observation studies were carried out
on two year-long software projects, with the researcher performing the role of HCI
designer within the software teams. Aspects of comprehension within the team were
found to be fundamental to successful collaboration. Prototypes were found to be an
effective means of facilitating team members' comprehension of HCI design intent, and
of maintaining conceptual integrity. However, this use of prototypes was flawed
because they introduced the potential for ambiguity and they were inaccessible.
Focusing on the collaboration of the HCI designer and programmers, requirements for a
prototype-centred explanation tool were specified to exploit the potential of prototyping
to facilitate comprehension, by addressing the flaws discovered. Such a tool, called
‘ProtoTour’, was designed and implemented, based on the requirements specified.
An experiment was conducted with 22 commercial programmers to ascertain whether a
ProtoTour representation of an existing, commercially developed prototype, facilitated
comprehension more effectively and was more accessible than a conventional
prototype. Results of the experiment found that programmers using ProtoTour gained a
significantly better understanding of HCI design intent, than programmers using a
conventional prototype. Those using ProtoTour also asked the HCI designer
significantly fewer questions about the HCI design intent. Results suggest that
prototype-centred explanation tools have the potential to improve programmers’
comprehension of HCI design intent.
Introducing an HCI designer into a software team was found to be an effective way of
improving the user-centred focus of software during production. A prototype-centred
explanation tool appears to have potential as a means of helping programmers
comprehend HCI design intent.
43
Ye, En. "TeamWATCH: Visualizing Development Activities Using a 3-D City Metaphor to Improve Conflict Detection and Team Awareness." Ohio University / OhioLINK, 2017. http://rave.ohiolink.edu/etdc/view?acc_num=ohiou1481215153498219.
Full text
44
Nordenskjöld, Gustav, and Harm Andries Kingma. "Software Process Improvement Using Groupware : Supporting Distributed Cooperation in Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3915.
Full textAbstract:
This master thesis describes our work with Team Sweden and how we have attempted to perform a Software Process Improvement using groupware. Team Sweden is a distributed academic software development organization doing research on artificial intelligence and robotics. Such an organization has a lot to gain from the introduction of a more structured process model. We have investigated the possibility of supporting the development processes of a small software development organization by introducing groupware. Only introducing a groupware tool or technique is not enough to improve the processes of an organization. Process improvement requires an infrastructure and groupware could be a useful tool for establishing it. Improved communication and knowledge sharing through groupware can be beneficial for establishing a process infrastructure. Groupware should be used in conjunction with other process improvement measures in order to be effective and improve the capability of the targeted organization.<br>This master thesis describes our work with Team Sweden and how we have attempted to perform a Software Process Improvement using groupware.<br>gustav@nordenskjold.com hakingma@hotmail.com
45
Shen, Haifeng, and n/a. "Internet-Based Collaborative Programming Techniques and Environments." Griffith University. School of Computing and Information Technology, 2003. http://www4.gu.edu.au:8080/adt-root/public/adt-QGU20031015.143156.
Full textAbstract:
Software systems are getting larger and more complex, while the requirements are becoming vaguer and more rapidly changing. These trends make current software development more and more likely a team work. To integrate multiple developers into a coherent structured management process and make team software development a positive-sum game for both higher productivity and better quality, many team soft ware development methodologies have been proposed and practised. An emerging methodology is collaborative programming, which allows a group of programmers to work together on the same source code for design, implementation of individual components, and integration of individual components. Compared with other team software methodologies that only address needs in some phases or situations, collaborative programming is more adaptive to the variety of different phases or situations in a team software development process. A core technical component in collaborative programming is collaborative editing, which allows a group of programmers to view and edit the same source code. To support different phases or situations in an Internet-based collaborative programming process, collaborative editing must meet the requirements of supporting unconstrained, responsive, real-time collaborative editing; unconstrained, syncretic, non-real-time collaborative editing; and smooth, flexible switching between real-time and non-real-time collaborative editing. This thesis research contributes several novel techniques to address these requirements, and an Internet-based collaborative programming environment to integrate those techniques. These research contributions have advanced state-of-the-art technologies on col laborative editing for supporting Internet-based collaborative programming. First, we contribute a collaborative highlighting gestural communication technique for unconstrained, responsive, real-time collaborative editing. This technique is particularly effective in improving the quality of real-time interaction on text-based source code documents. The contribution to the operational transformation technology is the extension of the technology to support group awareness. It includes a package of operational transformation functions and transformation control algorithms for consistency maintenance in collaborative highlighting, and a flexible undo solution that has the capability of undoing any highlighting operation at any time. Second, we contribute a flexible operation-based merging technique for unconstrained, syncretic, non-real-time collaborative editing, which is efficient and has the capability of textually integrating all changes, and automatically detecting and resolving syntactic conflicts according to application-dependent user-specified policies. The contribution to the operational transformation technology is the extension of the technology to support unconstrained, syncretic, non-real-time collaborative editing. Its includes a log compression algorithm, a textual merging algorithm, and a syntactic merging algorithm. Moreover, we contribute a flexible notification technique to support flexible collaborative editing: unconstrained, responsive, real-time collaborative editing; uncon strained, syncretic, non-real-time collaborative editing; and smooth, flexible switching between them. The contribution to the operational transformation technology is the extension of the technology to support flexible collaborative editing. It includes a new transformation control algorithm that has a linear time complexity, two notification algorithms that support propagation and acceptance of any notifications at any time, and a notification propagation protocol that is efficient for both real-time and non-real-time collaborative editing.
46
Shen, Haifeng. "Internet-Based Collaborative Programming Techniques and Environments." Thesis, Griffith University, 2003. http://hdl.handle.net/10072/367439.
Full textAbstract:
Software systems are getting larger and more complex, while the requirements are becoming vaguer and more rapidly changing. These trends make current software development more and more likely a team work. To integrate multiple developers into a coherent structured management process and make team software development a positive-sum game for both higher productivity and better quality, many team soft ware development methodologies have been proposed and practised. An emerging methodology is collaborative programming, which allows a group of programmers to work together on the same source code for design, implementation of individual components, and integration of individual components. Compared with other team software methodologies that only address needs in some phases or situations, collaborative programming is more adaptive to the variety of different phases or situations in a team software development process. A core technical component in collaborative programming is collaborative editing, which allows a group of programmers to view and edit the same source code. To support different phases or situations in an Internet-based collaborative programming process, collaborative editing must meet the requirements of supporting unconstrained, responsive, real-time collaborative editing; unconstrained, syncretic, non-real-time collaborative editing; and smooth, flexible switching between real-time and non-real-time collaborative editing. This thesis research contributes several novel techniques to address these requirements, and an Internet-based collaborative programming environment to integrate those techniques. These research contributions have advanced state-of-the-art technologies on col laborative editing for supporting Internet-based collaborative programming. First, we contribute a collaborative highlighting gestural communication technique for unconstrained, responsive, real-time collaborative editing. This technique is particularly effective in improving the quality of real-time interaction on text-based source code documents. The contribution to the operational transformation technology is the extension of the technology to support group awareness. It includes a package of operational transformation functions and transformation control algorithms for consistency maintenance in collaborative highlighting, and a flexible undo solution that has the capability of undoing any highlighting operation at any time. Second, we contribute a flexible operation-based merging technique for unconstrained, syncretic, non-real-time collaborative editing, which is efficient and has the capability of textually integrating all changes, and automatically detecting and resolving syntactic conflicts according to application-dependent user-specified policies. The contribution to the operational transformation technology is the extension of the technology to support unconstrained, syncretic, non-real-time collaborative editing. Its includes a log compression algorithm, a textual merging algorithm, and a syntactic merging algorithm. Moreover, we contribute a flexible notification technique to support flexible collaborative editing: unconstrained, responsive, real-time collaborative editing; uncon strained, syncretic, non-real-time collaborative editing; and smooth, flexible switching between them. The contribution to the operational transformation technology is the extension of the technology to support flexible collaborative editing. It includes a new transformation control algorithm that has a linear time complexity, two notification algorithms that support propagation and acceptance of any notifications at any time, and a notification propagation protocol that is efficient for both real-time and non-real-time collaborative editing.<br>Thesis (PhD Doctorate)<br>Doctor of Philosophy (PhD)<br>School of Computing and Information Technology<br>Full Text
47
Gaddefors, Ella, and Shahira Hashem. "An Intraorganizational Perspective of Sales Teams : A case study of the design and processes of a sales team in the cloud software industry." Thesis, Uppsala universitet, Företagsekonomiska institutionen, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-388427.
Full textAbstract:
The shift towards relationship marketing entails an increased attention directed to buildingcollaborative relationships in the business-to-business market. This has further contributed tothe current interest in the intraorganizational setting in the area of sales and key accountmanagement, and more specifically the notion of sales teams. In light of the above, the purposeof this study is to develop a conceptual framework emphasizing the intraorganizationalperspective of such teams. Within this context, the team’s design and processes have beenhighlighted in relation to its performance and ability to form relationships with customers. Toprovide insights to the purpose of this study a single-case study was conducted in a companyoperating within the cloud software industry. The analysis demonstrates how the design of theteam, depicted by the formalization of procedures and the heterogeneity of team members’expertise, constitutes the frame in which the processes are carried out. Further, the interplay ofcommunication, proactiveness and alignment of goals showed to constitute key processesenabling the team to build relationships with its customers. Thus, by providing a conceptualframework emphasizing the intraorganizational perspective of sales teams, this studycontributes to the theoretical discussion as well as to practitioners in the field.
48
Heß, Philipp [Verfasser], and Klaus [Akademischer Betreuer] Fiedler. "Scrum and Self-Control : How a team-based software development methodology can support team members' self-control / Philipp Heß ; Betreuer: Klaus Fiedler." Heidelberg : Universitätsbibliothek Heidelberg, 2016. http://d-nb.info/118060945X/34.
Full text
49
Liljedahl, Emma, and Alexandra Gabriel. "Self-selection in Software Development Teams : A Case Study Regarding Challenges and Possibilities with Reorganization through Self-selection." Thesis, Linköpings universitet, Informatik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-158417.
Full textAbstract:
The software development business today is a land of constant change. The change requires the organizations who operate within this business to be flexible and quick to respond. This has led to multiple agile organization methods being developed, one of them is DevOps. A cornerstone in DevOps is self-selection - a method for assembling teams. This method gives hope of less administration, autonomy in teams and increased performance. In this essay we investigate the promises - the challenges and the possibilities - of self-selection. The case in this essay is IFS - a big software development company, implementing self-selection department by department also facing the challenges of combining traditional project values with the short iterations of an agile method. Our qualitative study investigates which the main challenges and possibilities are. We also investigate how these findings should be managed. How could the diversity, team size and autonomy be enhanced or diminished? We found that some parts of the case, and practice, were like our prior literature - but some were not. For example, the feeling of being in homogeneous teams were not always negative, and the majority of those taking part of the self-selection at IFS said they chose team by assignment - not social network as the prior literature said. Our conclusion reveals that there are several different factors to consider when having selfselection implemented in a traditional project environment. The main areas where we have found possible improvements are Team Choice, Team Diversity, Overlapping Assignments, Experienced Ownership, Management Influence and Performance.
50
Lundberg, Niklas. "How is information and knowledge communicated? : A case study on communication within and across software-provisioning team boundaries." Thesis, Umeå universitet, Institutionen för informatik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-105089.
Full textAbstract:
Today it has become standard for organizations to rely on self-serving teams to make decisions since they are believed to provide access to bigger pools of information and knowledge than individual managers. However, while a lot of research has been focusing on how to improve information and knowledge sharing in teams to better promote the making of deliverables, not much has been said about how self-serving teams actually communicate information and knowledge. In this thesis a qualitative study was conducted with seven members of a software-provisioning team to, with particular focus on using IT when communicating, investigate how information and knowledge is communicated within and across team boundaries. Findings in this thesis suggest that there is a tension between information and knowledge sharing in teams. While the formalization of technological channels might facilitate effective information sharing in teams, it could have negative effects on knowledge sharing.