Academic literature on the topic 'Team software'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Team software.'
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.
Journal articles on the topic "Team software"
Hernández-López, Adrián, Ricardo Colomo-Palacios, Ángel García-Crespo, and Pedro Soto-Acosta. "Team Software Process in GSD Teams." International Journal of Human Capital and Information Technology Professionals 1, no. 3 (July 2010): 32–53. http://dx.doi.org/10.4018/jhcitp.2010070103.
Full textDey, Chitra, and Ganesh Mangadu Paramasivam. "Team Boundary Activity in Software Development Teams." Academy of Management Proceedings 2016, no. 1 (January 2016): 12484. http://dx.doi.org/10.5465/ambpp.2016.12484abstract.
Full textGómez, Marta N., Silvia T. Acuña, Marcela Genero, and 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, no. 4 (October 2012): 11–24. http://dx.doi.org/10.4018/jhcitp.2012100102.
Full textChiang, I. Robert, and Vijay S. Mookerjee. "Improving software team productivity." Communications of the ACM 47, no. 5 (May 1, 2004): 89–93. http://dx.doi.org/10.1145/986213.986217.
Full textSchlimmer, J. C., J. B. Fletcher, and L. A. Hermens. "Team-oriented software practicum." IEEE Transactions on Education 37, no. 2 (May 1994): 212–20. http://dx.doi.org/10.1109/13.284997.
Full textDeFranco, Joanna F., and Phillip Laplante. "A software engineering team research mapping study." Team Performance Management: An International Journal 24, no. 3/4 (June 11, 2018): 203–48. http://dx.doi.org/10.1108/tpm-08-2017-0040.
Full textMtsweni, Emmanuel S., Tertia Hörne, and John Andrew van der Poll. "Soft Skills for Software Project Team Members." International Journal of Computer Theory and Engineering 8, no. 2 (2016): 150–55. http://dx.doi.org/10.7763/ijcte.2016.v8.1035.
Full textHe, Jun, Brian S. Butler, and William R. King. "Team Cognition: Development and Evolution in Software Project Teams." Journal of Management Information Systems 24, no. 2 (October 2007): 261–92. http://dx.doi.org/10.2753/mis0742-1222240210.
Full textChakraborty, Suranjan, Saonee Sarker, Sudhanshu Rai, Suprateek Sarker, and Ranganadhan Nadadhur. "Offshore Vendors’ Software Development Team Configurations." Journal of Global Information Management 19, no. 3 (July 2011): 1–29. http://dx.doi.org/10.4018/jgim.2011070101.
Full textO’Connor, Rory, and Shuib Basri. "The Effect of Team Dynamics on Software Development Process Improvement." International Journal of Human Capital and Information Technology Professionals 3, no. 3 (July 2012): 13–26. http://dx.doi.org/10.4018/jhcitp.2012070102.
Full textDissertations / Theses on the topic "Team software"
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 textCrunk, 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 textThe 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.
Yang, Bob 1976. "Managing a distributed software engineering team." Thesis, Massachusetts Institute of Technology, 1998. http://hdl.handle.net/1721.1/50394.
Full textIncludes bibliographical references (leaves 97-98).
by Bob Yang.
B.S.
M.Eng.
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 textCavalcante, 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 textGifford, 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 textMaster of Science
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 textMaster of Science
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 textSudhakar, 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 textAhlstrand, 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 textI 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.
Books on the topic "Team software"
Pasch, Jürgen. Software-Entwicklung im Team. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9.
Full textJames, Newkirk, ed. Visual studio team system: Better software development for agile teams. Upper Saddle River, NJ: Addison-Wesley, 2007.
Find full textBabich, Wayne A. Software configuration management: Coordination for team productivity. Reading, Mass: Addison-Wesley, 1986.
Find full textHumphrey, Watts S. Introduction to the team software process(sm). Reading, Mass: Addison-Wesley, 2000.
Find full textAaron, Bjork, and De la Maza Michael, eds. Professional Scrum with Team Foundation Server 2010. Indianapolis, IN: Wiley Pub., 2011.
Find full textHandbook of team design: A practitioner's guide to team systems development. New York: McGraw-Hill, 1998.
Find full textLevinson, Jeff. Pro visual studio team system: With team edition for database professionals. 2nd ed. Berkeley, CA: Apress, 2007.
Find full textMeier, J. D. Team development with Microsoft Visual studio team foundation server: Patterns & practices. [United States?]: Microsoft, 2008.
Find full textHumphrey, Watts S. TSP--leading a development team. Upper Saddle River, NJ: Addison-Wesley, 2006.
Find full text1971-, David Jean-Luc, ed. Professional Visual studio team system. Indianapolis, IN: Wiley Technology Pub., 2006.
Find full textBook chapters on the topic "Team software"
Demant, Christian. "Das Team." In Software Due Diligence, 87–123. Berlin, Heidelberg: Springer Berlin Heidelberg, 2017. http://dx.doi.org/10.1007/978-3-662-53062-7_4.
Full textBeneken, Gerd, Felix Hummel, and Martin Kucich. "Euer Team." In Grundkurs agiles Software-Engineering, 75–117. Wiesbaden: Springer Fachmedien Wiesbaden, 2022. http://dx.doi.org/10.1007/978-3-658-37371-9_3.
Full textRosen, Clive. "Team Management." In Guide to Software Systems Development, 57–77. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-39730-2_4.
Full textPasch, Jürgen. "Ein Problem: Die Software-Bürokratie." In Software-Entwicklung im Team, 19–27. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_3.
Full textPasch, Jürgen. "Die Theorie: Dialogischer Software-Entwurf." In Software-Entwicklung im Team, 79–108. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_6.
Full textPasch, Jürgen. "Die Praxis: Dialogischer Software-Entwurf." In Software-Entwicklung im Team, 109–65. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_7.
Full textPasch, Jürgen. "Der Prolog: Perspektivität bei der Software-Entwicklung Ein Fallbeispiel." In Software-Entwicklung im Team, 1–5. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_1.
Full textPasch, Jürgen. "Die Einführung." In Software-Entwicklung im Team, 7–17. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_2.
Full textPasch, Jürgen. "Die Tradition: Projekte aus der Sicht der Software- Technik." In Software-Entwicklung im Team, 29–53. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_4.
Full textPasch, Jürgen. "Die Alternative: Die prozeßorientierte Sichtweise der Software-Entwicklung." In Software-Entwicklung im Team, 55–78. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-78513-9_5.
Full textConference papers on the topic "Team software"
Marsicano, George, Diana Valenca Pereira, Fabio Q. B. da Silva, and Cesar Franca. "Team Maturity in Software Engineering Teams." In 2017 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM). IEEE, 2017. http://dx.doi.org/10.1109/esem.2017.36.
Full textMiller, Phillip. "Team software process." In 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.
Full textKemppainen, Amber, Amy Hamlin, Matthew Barron, and Mary Raber. "Comparing Team Evaluation Software (Team+ and CATME)." In 2022 IEEE Frontiers in Education Conference (FIE). IEEE, 2022. http://dx.doi.org/10.1109/fie56618.2022.9962624.
Full textChen, Cong, and Kang Zhang. "TEAM RADAR." In 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.
Full textMcGuire, Mary. "Team software development techniques." In the twenty-second annual computer personnel research conference. New York, New York, USA: ACM Press, 1986. http://dx.doi.org/10.1145/317210.317234.
Full text"Team." In 2012 IEEE International Conference on Software Maintenance (ICSM). IEEE, 2012. http://dx.doi.org/10.1109/icsm.2012.6404981.
Full textChen, Pei-Chi, Ching-Chin Chern, and Chung-Yang Chen. "Software Project Team Characteristics and Team Performance: Team Motivation as a Moderator." In 2012 19th Asia-Pacific Software Engineering Conference (APSEC). IEEE, 2012. http://dx.doi.org/10.1109/apsec.2012.152.
Full textRobillard, Pierre N., and Mathieu Lavallee. "Software team processes: A taxonomy." In 2012 International Conference on Software and System Process (ICSSP). IEEE, 2012. http://dx.doi.org/10.1109/icssp.2012.6225952.
Full textZhang, Suling, Marilyn Tremaine, Jerry Fjermestad, Allen Milewski, and Patrick O'Sullivan. "Delegation in Virtual Team: the Moderating Effects of Team Maturity and Team Distance." In 2006 IEEE International Conference on Global Software Engineering (ICGSE'06). IEEE, 2006. http://dx.doi.org/10.1109/icgse.2006.261217.
Full textAlsaedi, Olaa, Zachary Toups, and Jonathan Cook. "Can a team coordination game help student software project teams?" In ICSE '16: 38th International Conference on Software Engineering. New York, NY, USA: ACM, 2016. http://dx.doi.org/10.1145/2897586.2897594.
Full textReports on the topic "Team software"
Humphrey, Watts S. The Team Software Process (TSP). Fort Belvoir, VA: Defense Technical Information Center, November 2000. http://dx.doi.org/10.21236/ada386941.
Full textChick, Timothy A., Robert Cannon, James McHale, William Nichols, Marsha Pomeroy-Huff, Jefferson Welch, and Alan Willet. Team Software Process (TSP) Coach Mentoring Program Guidebook. Fort Belvoir, VA: Defense Technical Information Center, August 2009. http://dx.doi.org/10.21236/ada512361.
Full textHumphrey, Watts S., Timothy A. Chick, William Nichols, and Marsha Pomeroy-Huff. Team Software Process (TSP) Body of Knowledge (BOK). Fort Belvoir, VA: Defense Technical Information Center, July 2010. http://dx.doi.org/10.21236/ada634307.
Full textNord, Robert L., James McHale, and Felix Bachmann. Combining Architecture-Centric Engineering with the Team Software Process. Fort Belvoir, VA: Defense Technical Information Center, December 2010. http://dx.doi.org/10.21236/ada536714.
Full textCallison, Rachel, and Marlene MacDonald. A Bibliography of the Personal Software Process (PSP) and the Team Software Process (TSP). Fort Belvoir, VA: Defense Technical Information Center, October 2009. http://dx.doi.org/10.21236/ada512317.
Full textChick, Timothy A., Robert Cannon, James McHale, William Nichols, Marsha Pomeroy-Huff, Jefferson Welch, and Alan Willett. Team Software Process (TSP) Coach Mentoring Program Guidebook Version 1.1. Fort Belvoir, VA: Defense Technical Information Center, June 2010. http://dx.doi.org/10.21236/ada528656.
Full textDavis, Noopur, and 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, June 2002. http://dx.doi.org/10.21236/ada404970.
Full textSims, 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), November 2019. http://dx.doi.org/10.2172/1575765.
Full textMcAndrews, Donald R. The Team Software Process (TSP): An Overview and Preliminary Results of Using Disciplined Practices. Fort Belvoir, VA: Defense Technical Information Center, November 2000. http://dx.doi.org/10.21236/ada387061.
Full textMcAndrews, Donald R. The Team Software ProcessSM (TSPSM): An Overview and Preliminary Results of Using Disciplined Practices. Fort Belvoir, VA: Defense Technical Information Center, November 2000. http://dx.doi.org/10.21236/ada388712.
Full text