Search results

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: Improving the IPRO Processes (semester?), IPRO 338: Improving the IPRO Process IPRO 338 Abstract S05
Creator: Orrison, Natalie, Krzyzek, Piotr, Berenfeld, Christopher, Aquilla, Joseph, Attaya, Nabil, Garascia, Dominic, Pamulapalthy, Abhinav, Olmstead, Van, Wasserman, Rachel
Date: 2005-05, 2005-05
Description: Most IPRO teams experience a significant delay in start up, spending about four weeks trying to figure out exactly what has previously been...
Show moreMost IPRO teams experience a significant delay in start up, spending about four weeks trying to figure out exactly what has previously been done, what problem they are trying to solve, and what the team must accomplish to solve the problem. This delay can be attributed to several reasons including high student turnover—85% of students in an IPRO are new each semester and there is a lack of delivering process knowledge between semesters.
Deliverables for IPRO 338: Improving the IPRO Process for the Summer 2005 semester
Show less

Title: Improving the IPRO Processes (semester?), IPRO 338: Improving the IPRO Process IPRO 338 IPRO Day Presentation S05
Creator: Orrison, Natalie, Krzyzek, Piotr, Berenfeld, Christopher, Aquilla, Joseph, Attaya, Nabil, Garascia, Dominic, Pamulapalthy, Abhinav, Olmstead, Van, Wasserman, Rachel
Date: 2005-05, 2005-05
Description: Most IPRO teams experience a significant delay in start up, spending about four weeks trying to figure out exactly what has previously been...
Show moreMost IPRO teams experience a significant delay in start up, spending about four weeks trying to figure out exactly what has previously been done, what problem they are trying to solve, and what the team must accomplish to solve the problem. This delay can be attributed to several reasons including high student turnover—85% of students in an IPRO are new each semester and there is a lack of delivering process knowledge between semesters.
Deliverables for IPRO 338: Improving the IPRO Process for the Summer 2005 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

Title: Improving the IPRO Processes (semester?), IPRO 338
Creator: Orrison, Natalie, Krzyzek, Piotr, Berenfeld, Christopher, Aquilla, Joseph, Attaya, Nabil, Garascia, Dominic, Pamulapalthy, Abhinav, Olmstead, Van, Wasserman, Rachel
Date: 2005-05, 2005-05
Description: Most IPRO teams experience a significant delay in start up, spending about four weeks trying to figure out exactly what has previously been...
Show moreMost IPRO teams experience a significant delay in start up, spending about four weeks trying to figure out exactly what has previously been done, what problem they are trying to solve, and what the team must accomplish to solve the problem. This delay can be attributed to several reasons including high student turnover—85% of students in an IPRO are new each semester and there is a lack of delivering process knowledge between semesters.
Deliverables for IPRO 338: Improving the IPRO Process for the Summer 2005 semester
Show less

repository.iit

Search the repository

Enabled Filters

Refine Results

Type

Date

Department

Subject

Creator

Rights