Gotowe bibliografie tematyczne / Team software

Gotowa bibliografia na temat „Team software”

Autor: Grafiati
Data publikacji: 4 czerwca 2021
Data aktualizacji: 20 lutego 2023

Utwórz poprawne odniesienie w stylach APA, MLA, Chicago, Harvard i wielu innych

Wybierz rodzaj źródła:

Spis treści

Zobacz listy aktualnych artykułów, książek, rozpraw, streszczeń i innych źródeł naukowych na temat „Team software”.

Przycisk „Dodaj do bibliografii” jest dostępny obok każdej pracy w bibliografii. Użyj go – a my automatycznie utworzymy odniesienie bibliograficzne do wybranej pracy w stylu cytowania, którego potrzebujesz: APA, MLA, Harvard, Chicago, Vancouver itp.

Możesz również pobrać pełny tekst publikacji naukowej w formacie „.pdf” i przeczytać adnotację do pracy online, jeśli odpowiednie parametry są dostępne w metadanych.

Artykuły w czasopismach na temat "Team software"

1

Hernández-López, Adrián, Ricardo Colomo-Palacios, Ángel García-Crespo i Pedro Soto-Acosta. "Team Software Process in GSD Teams". International Journal of Human Capital and Information Technology Professionals 1, nr 3 (lipiec 2010): 32–53. http://dx.doi.org/10.4018/jhcitp.2010070103.

Pełny tekst źródła
Streszczenie:
Distributed software development is becoming the norm for the software industry today as an organizational response to globalization and outsourcing tendencies. In this new environment, centralized models for software development team building models have to be reanalyzed. Team Software Process (TSP) guides engineering teams in developing software-intensive products and is intended to improve the levels of quality and productivity of a team’s software development project. In this paper, the authors assess the difficulty of using TSP in distributed software development environments. The objective of this assessment is twofold; firstly, know the general difficulty for using TSP in these environments, and secondly, know the caveats to be addressed in future software development team building models designed specifically for distributed environments.
Style APA, Harvard, Vancouver, ISO itp.
2

Dey, Chitra, i Ganesh Mangadu Paramasivam. "Team Boundary Activity in Software Development Teams". Academy of Management Proceedings 2016, nr 1 (styczeń 2016): 12484. http://dx.doi.org/10.5465/ambpp.2016.12484abstract.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Gómez, Marta N., Silvia T. Acuña, Marcela Genero i José A. Cruz-Lemus. "How Does the Extraversion of Software Development Teams Influence Team Satisfaction and Software Quality?" International Journal of Human Capital and Information Technology Professionals 3, nr 4 (październik 2012): 11–24. http://dx.doi.org/10.4018/jhcitp.2012100102.

Pełny tekst źródła
Streszczenie:
Team member knowledge and expertise are the aspects typically considered important for software team development formation. However, the authors believe that the formation of teams, as is found in literature, could be based on factors related to the personalities of the members of the development team, and that these factors might affect both the quality of the software product developed and the satisfaction perceived by the development team. In this work they present a controlled experiment, which was carried out during an academic course on Data Bases. The intention of this experiment was to evaluate whether the work team’s level of extraversion influenced, on the one hand, the final quality of the software products obtained and, on the other, the satisfaction perceived while this work was being carried out. The results obtained indicate that when forming work teams, project managers and lecturers should carry out a personality test beforehand in order to balance the amount of extraverted team members with those who are not extraverted. This would permit the team members to feel satisfied with the work carried out by the team without reducing the quality of the software products developed.
Style APA, Harvard, Vancouver, ISO itp.
4

Chiang, I. Robert, i Vijay S. Mookerjee. "Improving software team productivity". Communications of the ACM 47, nr 5 (1.05.2004): 89–93. http://dx.doi.org/10.1145/986213.986217.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Schlimmer, J. C., J. B. Fletcher i L. A. Hermens. "Team-oriented software practicum". IEEE Transactions on Education 37, nr 2 (maj 1994): 212–20. http://dx.doi.org/10.1109/13.284997.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

DeFranco, Joanna F., i Phillip Laplante. "A software engineering team research mapping study". Team Performance Management: An International Journal 24, nr 3/4 (11.06.2018): 203–48. http://dx.doi.org/10.1108/tpm-08-2017-0040.

Pełny tekst źródła
Streszczenie:
Purpose The purpose of this mapping study has been performed to identify, critically analyze and synthesize research performed in the area of software engineering teams. Teams, in a general sense, have been studied extensively. But the distinctive processes that need to be executed effectively and efficiently in software engineering require a better understanding of current software engineering team research. Design/methodology/approach In this work, software engineering team publications were analyzed and the key findings of each paper that met our search inclusion criteria were synthesized. In addition, a keyword content analysis was performed to create a taxonomy to categorize each paper and evaluate the state of software engineering team research. Findings In software engineering team research, the resulting areas that are the most active are teamwork/collaboration, process/design and coordination. Clear themes of analysis have been determined to help understand how team members collaborate, factors affecting their success and interactions among all project stakeholders. In addition, themes related to tools to support team collaboration, improve the effectiveness of software engineering processes and support team coordination have been found. However, the research gaps determined from the content analysis point toward a need for more research in the area of communication and tools. Originality/value The goal of this work is to define the span of previous research in this area, create a taxonomy to categorize such research and identify open research areas to provide a clear road map for future research in the area of software engineering teams. These results, along with the key finding themes presented, will help guide future research in an area that touches all parts of the software engineering and development processes.
Style APA, Harvard, Vancouver, ISO itp.
7

Mtsweni, Emmanuel S., Tertia Hörne i John Andrew van der Poll. "Soft Skills for Software Project Team Members". International Journal of Computer Theory and Engineering 8, nr 2 (2016): 150–55. http://dx.doi.org/10.7763/ijcte.2016.v8.1035.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

He, Jun, Brian S. Butler i William R. King. "Team Cognition: Development and Evolution in Software Project Teams". Journal of Management Information Systems 24, nr 2 (październik 2007): 261–92. http://dx.doi.org/10.2753/mis0742-1222240210.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Chakraborty, Suranjan, Saonee Sarker, Sudhanshu Rai, Suprateek Sarker i Ranganadhan Nadadhur. "Offshore Vendors’ Software Development Team Configurations". Journal of Global Information Management 19, nr 3 (lipiec 2011): 1–29. http://dx.doi.org/10.4018/jgim.2011070101.

Pełny tekst źródła
Streszczenie:
This research uses configuration theory and data collected from a major IT vendor organization to examine primary configurations of distributed teams in a global off-shoring context. The study indicates that off-shoring vendor organizations typically deploy three different types of configurations, which the authors term as thin-at-client, thick-at-client, and hybrid. These configurations differ in terms of the size of the sub-teams in the different distributed locations and the nature of the ISD-related tasks performed by the distributed team members. In addition, the different configurations were compared on their inherent process-related and resource-related flexibilities. The thick-at-client configuration emerged as the one that offers superior flexibility (in all dimensions).However, additional analysis also revealed contingencies apart from flexibility that may influence the appropriateness of the distributed ISD team configuration, including the volatility of the client organization’s environment and the extent to which the ISD tasks can be effortlessly moved to the vendor’s home location.
Style APA, Harvard, Vancouver, ISO itp.
10

O’Connor, Rory, i Shuib Basri. "The Effect of Team Dynamics on Software Development Process Improvement". International Journal of Human Capital and Information Technology Professionals 3, nr 3 (lipiec 2012): 13–26. http://dx.doi.org/10.4018/jhcitp.2012070102.

Pełny tekst źródła
Streszczenie:
This article identifies the effect of team dynamics in the context of software development teams and its impact on software process improvement (SPI) activities in very small companies, in order to understand the relationship between these two variables. Most software development work is done by teams of software engineers working together in a collaborative manner to execute a software development process. Although there is much literature examining software process and how to improve it, less attention has been paid to the issues of team-working and specifically the impact of team dynamics on the software development process. Team dynamics is the term used to define how people work and interact together in teams. Teamwork is more effective with the existence of positive team dynamic, as it encourages a better working environment with satisfied, fulfilled employees who will in turn be more productive. This paper presents the results of a research study of team dynamics in very small software development companies and its impact on the software development process and software process improvement activities.
Style APA, Harvard, Vancouver, ISO itp.
Więcej źródeł

Rozprawy doktorskie na temat "Team software"

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.

Pełny tekst źródła
Streszczenie:
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.
Style APA, Harvard, Vancouver, ISO itp.
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.

Pełny tekst źródła
Streszczenie:

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.

Style APA, Harvard, Vancouver, ISO itp.
3

Yang, Bob 1976. "Managing a distributed software engineering team". Thesis, Massachusetts Institute of Technology, 1998. http://hdl.handle.net/1721.1/50394.

Pełny tekst źródła
Streszczenie:
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.
Includes bibliographical references (leaves 97-98).
by Bob Yang.
B.S.
M.Eng.
Style APA, Harvard, Vancouver, ISO itp.
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.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
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.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
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.

Pełny tekst źródła
Streszczenie:
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.
Master of Science
Style APA, Harvard, Vancouver, ISO itp.
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.

Pełny tekst źródła
Streszczenie:
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.
Master of Science
Style APA, Harvard, Vancouver, ISO itp.
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.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
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.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Ahlstrand, Rebecca, i 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.

Pełny tekst źródła
Streszczenie:
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.
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.
Style APA, Harvard, Vancouver, ISO itp.
Więcej źródeł

Książki na temat "Team software"

1

Pasch, Jürgen. Software-Entwicklung im Team. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

James, Newkirk, red. Visual studio team system: Better software development for agile teams. Upper Saddle River, NJ: Addison-Wesley, 2007.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Babich, Wayne A. Software configuration management: Coordination for team productivity. Reading, Mass: Addison-Wesley, 1986.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Humphrey, Watts S. Introduction to the team software process(sm). Reading, Mass: Addison-Wesley, 2000.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Aaron, Bjork, i De la Maza Michael, red. Professional Scrum with Team Foundation Server 2010. Indianapolis, IN: Wiley Pub., 2011.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Handbook of team design: A practitioner's guide to team systems development. New York: McGraw-Hill, 1998.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Levinson, Jeff. Pro visual studio team system: With team edition for database professionals. Wyd. 2. Berkeley, CA: Apress, 2007.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Meier, J. D. Team development with Microsoft Visual studio team foundation server: Patterns & practices. [United States?]: Microsoft, 2008.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Humphrey, Watts S. TSP--leading a development team. Upper Saddle River, NJ: Addison-Wesley, 2006.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

1971-, David Jean-Luc, red. Professional Visual studio team system. Indianapolis, IN: Wiley Technology Pub., 2006.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
Więcej źródeł

Części książek na temat "Team software"

1

Demant, Christian. "Das Team". W Software Due Diligence, 87–123. Berlin, Heidelberg: Springer Berlin Heidelberg, 2017. http://dx.doi.org/10.1007/978-3-662-53062-7_4.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Beneken, Gerd, Felix Hummel i Martin Kucich. "Euer Team". W Grundkurs agiles Software-Engineering, 75–117. Wiesbaden: Springer Fachmedien Wiesbaden, 2022. http://dx.doi.org/10.1007/978-3-658-37371-9_3.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Rosen, Clive. "Team Management". W Guide to Software Systems Development, 57–77. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-39730-2_4.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Pasch, Jürgen. "Ein Problem: Die Software-Bürokratie". W Software-Entwicklung im Team, 19–27. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_3.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Pasch, Jürgen. "Die Theorie: Dialogischer Software-Entwurf". W Software-Entwicklung im Team, 79–108. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_6.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Pasch, Jürgen. "Die Praxis: Dialogischer Software-Entwurf". W Software-Entwicklung im Team, 109–65. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_7.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Pasch, Jürgen. "Der Prolog: Perspektivität bei der Software-Entwicklung Ein Fallbeispiel". W Software-Entwicklung im Team, 1–5. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_1.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Pasch, Jürgen. "Die Einführung". W Software-Entwicklung im Team, 7–17. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_2.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Pasch, Jürgen. "Die Tradition: Projekte aus der Sicht der Software- Technik". W Software-Entwicklung im Team, 29–53. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_4.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Pasch, Jürgen. "Die Alternative: Die prozeßorientierte Sichtweise der Software-Entwicklung". W Software-Entwicklung im Team, 55–78. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_5.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.

Streszczenia konferencji na temat "Team software"

1

Marsicano, George, Diana Valenca Pereira, Fabio Q. B. da Silva i Cesar Franca. "Team Maturity in Software Engineering Teams". W 2017 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM). IEEE, 2017. http://dx.doi.org/10.1109/esem.2017.36.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Miller, Phillip. "Team software process". W the 2009 Annual Research Conference of the South African Institute of Computer Scientists and Information Technologists. New York, New York, USA: ACM Press, 2009. http://dx.doi.org/10.1145/1632149.1632150.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Kemppainen, Amber, Amy Hamlin, Matthew Barron i Mary Raber. "Comparing Team Evaluation Software (Team+ and CATME)". W 2022 IEEE Frontiers in Education Conference (FIE). IEEE, 2022. http://dx.doi.org/10.1109/fie56618.2022.9962624.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Chen, Cong, i Kang Zhang. "TEAM RADAR". W 6th International Conference on Evaluation of Novel Software Approaches to Software Engineering. SCITEPRESS - Science and Technology Publications, 2011. http://dx.doi.org/10.5220/0003464201140120.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

McGuire, Mary. "Team software development techniques". W the twenty-second annual computer personnel research conference. New York, New York, USA: ACM Press, 1986. http://dx.doi.org/10.1145/317210.317234.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

"Team". W 2012 IEEE International Conference on Software Maintenance (ICSM). IEEE, 2012. http://dx.doi.org/10.1109/icsm.2012.6404981.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Chen, Pei-Chi, Ching-Chin Chern i Chung-Yang Chen. "Software Project Team Characteristics and Team Performance: Team Motivation as a Moderator". W 2012 19th Asia-Pacific Software Engineering Conference (APSEC). IEEE, 2012. http://dx.doi.org/10.1109/apsec.2012.152.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Robillard, Pierre N., i Mathieu Lavallee. "Software team processes: A taxonomy". W 2012 International Conference on Software and System Process (ICSSP). IEEE, 2012. http://dx.doi.org/10.1109/icssp.2012.6225952.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Zhang, Suling, Marilyn Tremaine, Jerry Fjermestad, Allen Milewski i Patrick O'Sullivan. "Delegation in Virtual Team: the Moderating Effects of Team Maturity and Team Distance". W 2006 IEEE International Conference on Global Software Engineering (ICGSE'06). IEEE, 2006. http://dx.doi.org/10.1109/icgse.2006.261217.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Alsaedi, Olaa, Zachary Toups i Jonathan Cook. "Can a team coordination game help student software project teams?" W ICSE '16: 38th International Conference on Software Engineering. New York, NY, USA: ACM, 2016. http://dx.doi.org/10.1145/2897586.2897594.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.

Raporty organizacyjne na temat "Team software"

1

Humphrey, Watts S. The Team Software Process (TSP). Fort Belvoir, VA: Defense Technical Information Center, listopad 2000. http://dx.doi.org/10.21236/ada386941.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Chick, Timothy A., Robert Cannon, James McHale, William Nichols, Marsha Pomeroy-Huff, Jefferson Welch i Alan Willet. Team Software Process (TSP) Coach Mentoring Program Guidebook. Fort Belvoir, VA: Defense Technical Information Center, sierpień 2009. http://dx.doi.org/10.21236/ada512361.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Humphrey, Watts S., Timothy A. Chick, William Nichols i Marsha Pomeroy-Huff. Team Software Process (TSP) Body of Knowledge (BOK). Fort Belvoir, VA: Defense Technical Information Center, lipiec 2010. http://dx.doi.org/10.21236/ada634307.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Nord, Robert L., James McHale i Felix Bachmann. Combining Architecture-Centric Engineering with the Team Software Process. Fort Belvoir, VA: Defense Technical Information Center, grudzień 2010. http://dx.doi.org/10.21236/ada536714.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Callison, Rachel, i Marlene MacDonald. A Bibliography of the Personal Software Process (PSP) and the Team Software Process (TSP). Fort Belvoir, VA: Defense Technical Information Center, październik 2009. http://dx.doi.org/10.21236/ada512317.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Chick, Timothy A., Robert Cannon, James McHale, William Nichols, Marsha Pomeroy-Huff, Jefferson Welch i Alan Willett. Team Software Process (TSP) Coach Mentoring Program Guidebook Version 1.1. Fort Belvoir, VA: Defense Technical Information Center, czerwiec 2010. http://dx.doi.org/10.21236/ada528656.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Davis, Noopur, i Jim McHale. Relating the Team Software Process(SM) (TSPSM) to the Capability Maturity Model for Software (SW-CMM). Fort Belvoir, VA: Defense Technical Information Center, czerwiec 2002. http://dx.doi.org/10.21236/ada404970.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Sims, Benjamin Hayden. Enabling coordinated, distributed development of scientific software: A research agenda for adapting a team of teams approach. Office of Scientific and Technical Information (OSTI), listopad 2019. http://dx.doi.org/10.2172/1575765.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

McAndrews, Donald R. The Team Software Process (TSP): An Overview and Preliminary Results of Using Disciplined Practices. Fort Belvoir, VA: Defense Technical Information Center, listopad 2000. http://dx.doi.org/10.21236/ada387061.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

McAndrews, Donald R. The Team Software ProcessSM (TSPSM): An Overview and Preliminary Results of Using Disciplined Practices. Fort Belvoir, VA: Defense Technical Information Center, listopad 2000. http://dx.doi.org/10.21236/ada388712.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
Możesz być także zainteresowany rozszerzonymi bibliografiami na temat „Team software” dla poszczególnych typów źródeł:
Artykuły w czasopismach Rozprawy doktorskie Książki
Oferujemy zniżki na wszystkie plany premium dla autorów, których prace zostały uwzględnione w tematycznych zestawieniach literatury. Skontaktuj się z nami, aby uzyskać unikalny kod promocyjny!

Do bibliografii