Search results

Title: COMMUNICATION, LEADERSHIP, AND VIRTUAL TEAMS
Creator: Robinson, Joy D.
Date: 2014, 2014-05
Description: A self-managing virtual (SMV) team is a configuration that permits team leaders to manage and administer their team with limited supervisory...
Show moreA self-managing virtual (SMV) team is a configuration that permits team leaders to manage and administer their team with limited supervisory oversight. These teams are widespread in software and engineering environments where resources may be scattered globally (Yukl, 2009). Research into SMV team leadership is, however, in its early stages. Scholars have yet to confirm that traditional leadership theories operate in this theater. Additionally, the slate of leader roles that describe leadership and how these leaders affect success is not well understood. Research into emergent leadership provides limited insight into virtual teams, but current research fails to examine how emergent leaders manifest in the presence of an appointed leader. This study examines the relationship between emergent leadership and team success using the Behavioral Complexity Leadership theory or Leaderplex. In the experiment, two virtual teams attempted a series of interdependent, complex tasks across a series of weeks. This analysis confirmed that leader roles could adequately describe leadership in virtual teams. SMV leaders focused specifically on the Monitor role with the remaining roles left distributed among the membership. The appointed leader condition did not suppress leader roles, however, in this study the appointed leader negatively affected team performance. Lastly, two perspectives (Perception and Practice) showed little correlation between leader roles. The study, conducted using the synthetic milieu of a popular MMO --World of Warcraft, served to push the envelope of permissible social science research environments.
PH.D in Technical Communication, May 2014
Show less

Title: Maintaining and Implementing a Knowledge Management System (semester?), IPRO 338: iKNOW Management IPRO 338 IPRO Day Presentation Sp06
Creator: Collard, Aaron, Crulcich, Jake, Debiak, Carol, Edwardson, John, Hasija, Abhinav, Krzyzek, Piotr, Lam, Christopher, Meyer, Douglas, Ramakrishna, Sushanth, Roberson, Dennis, Robinson, Joy, Schramm, Dan, Tillmans, Mike, Wojtowicz, Norbert
Date: 2006-05, 2006-05
Description: IPRO 338 project started in 2003 was designed to address the issue of knowledge transfer in the IPRO teams. Due to an 80% student turnover...
Show moreIPRO 338 project started in 2003 was designed to address the issue of knowledge transfer in the IPRO teams. Due to an 80% student turnover rate and few teams continuing across semesters a large amount of valuable project knowledge was being lost. To address this issue, the IPRO knowledge management tool – iKNOW, was developed to assist with capturing and cataloging the knowledge generated from IPRO projects during each semester. This semester, IPRO 338 was charged with the full implementation of IKNOW across the 36 teams in the IPRO Spring semester. However, since this report was completed prior to the iKNOW upload deadline, a full accounting of the number of compliant teams was unavailable.
Sponsorship: Tom Jacobius
Deliverables for IPRO 338: Maintaining and Implementing a Knowledge Management System for the Spring 2006 semester
Show less

Title: Maintaining and Implementing a Knowledge Management System (semester?), IPRO 338: iKNOW Management IPRO 338 Final Report Sp06
Creator: Collard, Aaron, Crulcich, Jake, Debiak, Carol, Edwardson, John, Hasija, Abhinav, Krzyzek, Piotr, Lam, Christopher, Meyer, Douglas, Ramakrishna, Sushanth, Roberson, Dennis, Robinson, Joy, Schramm, Dan, Tillmans, Mike, Wojtowicz, Norbert
Date: 2006-05, 2006-05
Description: IPRO 338 project started in 2003 was designed to address the issue of knowledge transfer in the IPRO teams. Due to an 80% student turnover...
Show moreIPRO 338 project started in 2003 was designed to address the issue of knowledge transfer in the IPRO teams. Due to an 80% student turnover rate and few teams continuing across semesters a large amount of valuable project knowledge was being lost. To address this issue, the IPRO knowledge management tool – iKNOW, was developed to assist with capturing and cataloging the knowledge generated from IPRO projects during each semester. This semester, IPRO 338 was charged with the full implementation of IKNOW across the 36 teams in the IPRO Spring semester. However, since this report was completed prior to the iKNOW upload deadline, a full accounting of the number of compliant teams was unavailable.
Sponsorship: Tom Jacobius
Deliverables for IPRO 338: Maintaining and Implementing a Knowledge Management System for the Spring 2006 semester
Show less

Title: Maintaining and Implementing a Knowledge Management System (semester?), IPRO 338: iKNOW Management IPRO 338 Poster Sp06
Creator: Collard, Aaron, Crulcich, Jake, Debiak, Carol, Edwardson, John, Hasija, Abhinav, Krzyzek, Piotr, Lam, Christopher, Meyer, Douglas, Ramakrishna, Sushanth, Roberson, Dennis, Robinson, Joy, Schramm, Dan, Tillmans, Mike, Wojtowicz, Norbert
Date: 2006-05, 2006-05
Description: IPRO 338 project started in 2003 was designed to address the issue of knowledge transfer in the IPRO teams. Due to an 80% student turnover...
Show moreIPRO 338 project started in 2003 was designed to address the issue of knowledge transfer in the IPRO teams. Due to an 80% student turnover rate and few teams continuing across semesters a large amount of valuable project knowledge was being lost. To address this issue, the IPRO knowledge management tool – iKNOW, was developed to assist with capturing and cataloging the knowledge generated from IPRO projects during each semester. This semester, IPRO 338 was charged with the full implementation of IKNOW across the 36 teams in the IPRO Spring semester. However, since this report was completed prior to the iKNOW upload deadline, a full accounting of the number of compliant teams was unavailable.
Sponsorship: Tom Jacobius
Deliverables for IPRO 338: Maintaining and Implementing a Knowledge Management System for the Spring 2006 semester
Show less

Title: Maintaining and Implementing a Knowledge Management System (semester?), IPRO 338: iKNOW Management IPRO 338 Abstract Sp06
Creator: Collard, Aaron, Crulcich, Jake, Debiak, Carol, Edwardson, John, Hasija, Abhinav, Krzyzek, Piotr, Lam, Christopher, Meyer, Douglas, Ramakrishna, Sushanth, Roberson, Dennis, Robinson, Joy, Schramm, Dan, Tillmans, Mike, Wojtowicz, Norbert
Date: 2006-05, 2006-05
Description: IPRO 338 project started in 2003 was designed to address the issue of knowledge transfer in the IPRO teams. Due to an 80% student turnover...
Show moreIPRO 338 project started in 2003 was designed to address the issue of knowledge transfer in the IPRO teams. Due to an 80% student turnover rate and few teams continuing across semesters a large amount of valuable project knowledge was being lost. To address this issue, the IPRO knowledge management tool – iKNOW, was developed to assist with capturing and cataloging the knowledge generated from IPRO projects during each semester. This semester, IPRO 338 was charged with the full implementation of IKNOW across the 36 teams in the IPRO Spring semester. However, since this report was completed prior to the iKNOW upload deadline, a full accounting of the number of compliant teams was unavailable.
Sponsorship: Tom Jacobius
Deliverables for IPRO 338: Maintaining and Implementing a Knowledge Management System for the Spring 2006 semester
Show less

Title: Maintaining and Implementing a Knowledge Management System (semester?), IPRO 338
Creator: Collard, Aaron, Crulcich, Jake, Debiak, Carol, Edwardson, John, Hasija, Abhinav, Krzyzek, Piotr, Lam, Christopher, Meyer, Douglas, Ramakrishna, Sushanth, Roberson, Dennis, Robinson, Joy, Schramm, Dan, Tillmans, Mike, Wojtowicz, Norbert
Date: 2006-05, 2006-05
Description: IPRO 338 project started in 2003 was designed to address the issue of knowledge transfer in the IPRO teams. Due to an 80% student turnover...
Show moreIPRO 338 project started in 2003 was designed to address the issue of knowledge transfer in the IPRO teams. Due to an 80% student turnover rate and few teams continuing across semesters a large amount of valuable project knowledge was being lost. To address this issue, the IPRO knowledge management tool – iKNOW, was developed to assist with capturing and cataloging the knowledge generated from IPRO projects during each semester. This semester, IPRO 338 was charged with the full implementation of IKNOW across the 36 teams in the IPRO Spring semester. However, since this report was completed prior to the iKNOW upload deadline, a full accounting of the number of compliant teams was unavailable.
Sponsorship: Tom Jacobius
Deliverables for IPRO 338: Maintaining and Implementing a Knowledge Management System for the Spring 2006 semester
Show less

repository.iit

Search the repository

Query

Refine Results

Type

Date

Department

Subject

Creator

Rights