Common use of Meetings and Presentations with Students Clause in Contracts

Meetings and Presentations with Students. Scientists will need to participate in the app design process by meeting with the team and watching team presentations. I have found that the best mode of communication is face to face, followed by conference calling or video conferencing using phone, skype or google hang out, and that email correspondence is the least effective. Nevertheless, all modes of communication will need to be used, except in the case of off-­‐campus scientists, where face-­‐to-­‐face communication is unlikely. Following are scheduled meeting dates and the expected focus of each meeting. 1/19/2017 or 1/20/2017 – First meeting between teams and scientists. The teams will learn about the app idea from the scientist; including what tasks are to be performed with the app, users of the app, where the app is to be used, etc. The meeting should last between 30 – 60 minutes. 1/24/2017 or 1/25/2017 – Second follow-­‐up meeting with teams and scientists. This second meeting allows teams to ask follow up questions after they have thought about the app idea over the weekend. The meeting should last between 30 – 60 minutes. 2/2/2017 – 2/7/2017 – Paper prototype design presentation. In this presentation, teams present their designs working through the apps' tasks using a design of the app expressed as drawings on paper. Each team has 30 minutes to present their design, answer questions and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation for their app. It is best if the scientists attend the presentation live, but scientists can view the videos later if the cannot be present. Links to the video will be posted on the course website the evening of the presentation or the following day. 2/3/2017 – 2/11/2017 – Feedback from scientist on the paper prototype. During this meeting, scientists can provide detailed feedback of the design presented in the paper prototype presentation. The meeting should last between 30 – 60 minutes. 3/28/2017 – 3/30/2017– Final design presentation. In this presentation, teams present their design by working through apps' tasks using a partially implemented app. Each team has 30 minutes to present their design, answer question and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation of their app. It is best if the scientists can attend the presentation live, but scientists can view the videos later. Links to the video will be posted on the course website the evening of the presentation or the following day.

Meetings and Presentations with Students. Scientists will need to participate in the app design process by meeting with the team and watching team presentations. I have found that the best mode of communication is face to face, followed by conference calling or video conferencing using phone, skype or google hang out, and that email correspondence is the least effective. Nevertheless, all modes of communication will need to be used, except in the case of off-­‐campus off-campus scientists, where face-­‐to-­‐face face-to-face communication is unlikely. Following are scheduled meeting dates and the expected focus of each meeting. 1/19/2017 1/25/2018 or 1/20/2017 1/26/2018 – First meeting between teams and scientists. The teams will learn about the app idea from the scientist; including what tasks are to be performed with the app, users of the app, where the app is to be used, etc. The meeting should last between 30 – 60 minutes. 1/24/2017 1/30/2018 or 1/25/2017 1/31/2018 – Second follow-­‐up follow-up meeting with teams and scientists. This second meeting allows teams to ask follow up questions after they have thought about the app idea over the weekend. The meeting should last between 30 – 60 minutes. 2/2/2017 2/13/2018 – 2/7/2017 2/15/2018 – Paper prototype design presentation. In this presentation, teams present their designs working through the apps' tasks using a design of the app expressed as drawings on paper. Each team has 30 minutes to present their design, answer questions and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation for their app. It is best if the scientists attend the presentation live, but scientists can view the videos later if the cannot be present. Links to the video will be posted on the course website the evening of the presentation or the following day. 2/3/2017 2/14/2018 – 2/11/2017 2/21/2018 – Feedback from scientist on the paper prototype. During this meeting, scientists can provide detailed feedback of the design presented in the paper prototype presentation. The meeting should last between 30 – 60 minutes. 3/28/2017 4/3/2018 – 3/30/20174/5/2018 – Final design presentation. In this presentation, teams present their design by working through apps' tasks using a partially implemented app. Each team has 30 minutes to present their design, answer question and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation of their app. It is best if the scientists can attend the presentation live, but scientists can view the videos later. Links to the video will be posted on the course website the evening of the presentation or the following day.

Meetings and Presentations with Students. Scientists will need to participate in the app design process by meeting with the team and watching team presentations. I have found that the best mode of communication is face to face, followed by conference calling or video conferencing using phone, skype or google hang out, and that email correspondence is the least effective. Nevertheless, all modes of communication will need to be used, except in the case of off-­‐campus off-campus scientists, where face-­‐to-­‐face face-to-face communication is unlikely. Following are scheduled meeting dates and the expected focus of each meeting. 1/19/2017 or 1/20/2017 1/23/2020 - 1/24/2020 – First meeting between teams and scientists. The teams will learn about the app idea from the scientist; including what tasks are to be performed with the app, users of the app, where the app is to be used, etc. The meeting should last between 30 – 60 minutes. 1/24/2017 or 1/25/2017 1/30/2020 - 1/31/2020 – Second follow-­‐up follow-up meeting with teams and scientists. This second meeting allows teams to ask follow up questions after they have thought about the app idea over the weekend. The meeting should last between 30 – 60 minutes. 2/2/2017 – 2/7/2017 2/11/2020 and 2/13/2020 – Paper prototype design presentation. In this presentation, teams present their designs working through the apps' tasks using a design of the app expressed as drawings on paper. Each team has 30 minutes to present their design, answer questions and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation for their app. It is best if the scientists attend the presentation livelive or by conference call, but scientists can view the videos later if the you cannot be present. If attending the presentations, you will be given an opportunity to ask questions. Please ask questions that you require immediate answers for your understanding because time is short during the presentations. You will meet with your development team shortly and can ask longer questions then. Links to the video will be posted on the course website the evening of the presentation or the following day. 2/3/2017 – 2/11/2017 2/12/2020 - 2/18/2020 – Feedback from scientist on the paper prototype. During this meeting, scientists can provide detailed feedback of the design presented in the paper prototype presentation. The meeting should last between 30 – 60 minutes. 3/28/2017 – 3/30/20173/31/2020 and 4/2/2020 – Final design presentation. In this presentation, teams present their design by working through apps' tasks using a partially implemented app. Each team has 30 minutes to present their design, answer question and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation of their app. It is best if the scientists can attend the presentation live, but scientists can view the videos later. Links to the video will be posted on the course website the evening of the presentation or the following day. 4/1/2020 - 4/7/2020 – Feedback from the scientist for adjustment of the final design. During this meeting, scientists can provide detailed feedback on the presented design. Because the students should have already implemented a significant portion of the app, only minor adjustments can be made. The student teams should decide if they have time to implement the changes and will advise the scientist so. The meeting should last between 30 – 60 minutes. 4/21/2020 and 4/23/2020 – Usability test result presentations. During the prior week, teams will have tested their app, using students from other classes. In this presentation, graduate students and humanities students present preliminary results of the usability tests. Each team has 30 minutes to present their design, answer questions and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation of their app. It is best if the scientists could attend the presentation live, but scientists can view the videos later. Links to the video will be posted on the course website the evening of the presentation or the following day. 4/22/2020 - 4/30/2020 – Feedback from scientists on usability test results. During this meeting, graduate students give details of the usability test results. Scientists, teams and graduate students can discuss changes to a new version of the app as a result of the usability test results. The meeting should last between 30 – 60 minutes. The above schedule implies that there are 8 "scheduled meetings and video presentations" of about one half hour to an hour each, but additional meetings for gathering app requirements may also be needed in the first seven weeks of the semester, depending on the complexity of the app and how precisely the app concept has been defined prior to the beginning of the project. The teams will be responsible for arranging the meetings. They will try to minimize any extra meetings, but it is important for the scientists to respond in a timely manner to the teams’ requests for further meetings. In addition to meetings, team may use emails to communicate. Both scientists and teams should be responsive to answering emails. Note that the teams maintain a website for posting their design documents. Links to the teams' project website will be available on the CS4760 course website. The project website will be continuously available after the second week of the semester. Scientists will find these websites invaluable for learning about app design details and progress.

Meetings and Presentations with Students. Scientists will need to participate in the app design process by meeting with the team and watching team presentations. I have found that the best mode of communication is face to face, followed by conference calling or video conferencing using phone, skype Zoom or google hang out, and that email meet. Email correspondence is the least effective. Nevertheless, all modes of communication will need to be used, except in the case of off-­‐campus off-campus scientists, where face-­‐to-­‐face face-to-face communication is unlikely. Following are scheduled meeting dates and the expected focus of each meeting. 1/19/2017 or 1/20/2017 1/19/2021 - 1/20/2021– First meeting between teams and scientists. The teams will learn about the app idea from the scientist; including what tasks are to be performed with the app, users of the app, where the app is to be used, etc. The meeting should last between 30 – 60 minutes. 1/24/2017 or 1/25/2017 1/19/2021 - 1/20/2021– Second follow-­‐up follow-up meeting with teams and scientists. This second meeting allows teams to ask follow up questions after they have thought about the app idea over the weekend. The meeting should last between 30 – 60 minutes. 2/2/2017 – 2/7/2017 2/9/2021 and 2/11/2021 – Paper prototype design presentation. In this presentation, teams present their designs designs, working through the apps' tasks using a design of the app expressed as drawings on paperpaper prototype. Each team has 30 minutes to present their design, answer questions and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation for their app. It is best if the scientists attend the presentation livelive or by conference call, but scientists can view the videos later if the they cannot be present. If attending the presentations, you will be given an opportunity to ask questions. Please ask questions that you require immediate answers for your understanding because time is short during the presentations. You will meet with your development team after the presentation and can ask longer questions then. Links to the video will be posted on the course website the evening of the presentation or the following day. 2/3/2017 – 2/11/2017 2/10/2021 - 2/18/2021 – Feedback from scientist on the paper prototype. During this meeting, scientists can provide detailed feedback of the design presented in the paper prototype presentation. The meeting should last between 30 – 60 minutes. 3/28/2017 – 3/30/20173/30/2021 and 4/1/2021 – Final design presentation. In this presentation, teams present their design by working through apps' tasks using a partially implemented app. Each team has 30 minutes to present their design, answer question and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation of their app. It is best if the scientists can attend the presentation live, but scientists can view the videos later. Links to the video will be posted on the course website the evening of the presentation or the following day. 3/31/2021 - 4/8/2021 – Feedback from the scientist for adjustment of the final design. During this meeting, scientists can provide detailed feedback on the presented design. Because the students should have already implemented a significant portion of the app, only minor adjustments can be made. The student teams should decide if they have time to implement the changes and will advise the scientist so. The meeting should last between 30 – 60 minutes. 4/20/2021 and 4/22/2021 – Usability test result presentations. During the prior week, teams will have tested their app using students from other classes. In this presentation, graduate students present preliminary results of the usability tests. Each team has 30 minutes to present their design, answer questions and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation of their app. It is best if the scientists could attend the presentation live, but scientists can view the videos later. Links to the video will be posted on the course website the evening of the presentation or the following day. 4/21/2021 - 4/28/2021 – Feedback from scientists on usability test results. During this meeting, graduate students give details of the usability test results. Scientists, teams and graduate students can discuss changes to a new version of the app as a result of the usability test results. The meeting should last between 30 – 60 minutes. The above schedule implies that there are 8 "scheduled meetings and video presentations" of about one half hour to an hour each, but additional meetings for gathering app requirements may also be needed in the first seven weeks of the semester, depending on the complexity of the app and how precisely the app concept has been defined prior to the beginning of the project. The teams will be responsible for arranging the meetings. They will try to minimize any extra meetings, but it is important for the scientists to respond in a timely manner to the teams’ requests for further meetings. In addition to meetings, team may use emails to communicate. Both scientists and teams should be responsive to answering emails. Note that the teams maintain a website for posting their design documents. Links to the teams' project website will be available on the CS4760 course website. The project website will be continuously available after the second week of the semester. Scientists will find these websites invaluable for learning about app design details and progress.

Meetings and Presentations with Students. Scientists will need to participate in the app design process by meeting with the team and watching team presentations. I have found that the best mode of communication is face to face, followed by conference calling or video conferencing using phone, skype Zoom or google hang out, and that email meet. Email correspondence is the least effective. Nevertheless, all modes of communication will need to be used, except in the case of off-­‐campus off-campus scientists, where face-­‐to-­‐face face-to-face communication is unlikely. Following are scheduled meeting dates and the expected focus of each meeting. 1/19/2017 or 1/20/2017 1/18/2022 - 1/19/2022 – First meeting between teams and scientists. The teams will learn about the app idea from the scientist; including what tasks are to be performed with the app, users of the app, where the app is to be used, etc. The meeting should last between 30 – 60 minutes. 1/24/2017 or 1/25/2017 1/25/2022 - 1/26/2022 – Second follow-­‐up follow-up meeting with teams and scientists. This second meeting allows teams to ask follow up questions after they have thought about the app idea over the weekend. The meeting should last between 30 – 60 minutes. 2/2/2017 – 2/7/2017 2/3/2022 and 2/11/2022 – Paper prototype design presentation. In this presentation, teams present their designs designs, working through the apps' tasks using a design of the app expressed as drawings on paperpaper prototype. Each team has 30 minutes to present their design, answer questions and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation for their app. It is best if the scientists attend the presentation livelive or by conference call, but scientists can view the videos later if the they cannot be present. If attending the presentations, you will be given an opportunity to ask questions. Please ask questions that you require immediate answers for your understanding because time is short during the presentations. You will meet with your development team after the presentation and can ask longer questions then. Links to the video will be posted on the course website the evening of the presentation or the following day. 2/3/2017 – 2/11/2017 2/3/2022 - 2/14/2022 – Feedback from scientist on the paper prototype. During this meeting, scientists can provide detailed feedback of the design presented in the paper prototype presentation. The meeting should last between 30 – 60 minutes. 3/28/2017 – 3/30/20173/29/2022 and 3/31/2022 – Final design presentation. In this presentation, teams present their design by working through apps' tasks using a partially implemented app. Each team has 30 minutes to present their design, answer question and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation of their app. It is best if the scientists can attend the presentation live, but scientists can view the videos later. Links to the video will be posted on the course website the evening of the presentation or the following day. 3/29/2022 - 4/7/2022 – Feedback from the scientist for adjustment of the final design. During this meeting, scientists can provide detailed feedback on the presented design. Because the students should have already implemented a significant portion of the app, only minor adjustments can be made. The student teams should decide if they have time to implement the changes and will advise the scientist so. The meeting should last between 30 – 60 minutes. 4/19/2022 and 4/21/2022 – Usability test result presentations. During the prior week, teams will have tested their app using students from other classes. In this presentation, graduate students present preliminary results of the usability tests. Each team has 30 minutes to present their design, answer questions and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation of their app. It is best if the scientists could attend the presentation live, but scientists can view the videos later. Links to the video will be posted on the course website the evening of the presentation or the following day. 4/19/2022 - 4/27/2022 – Feedback from scientists on usability test results. During this meeting, graduate students give details of the usability test results. Scientists, teams and graduate students can discuss changes to a new version of the app as a result of the usability test results. The meeting should last between 30 – 60 minutes. The above schedule implies that there are 8 "scheduled meetings and video presentations" of about one half hour to an hour each, but additional meetings for gathering app requirements may also be needed in the first seven weeks of the semester, depending on the complexity of the app and how precisely the app concept has been defined prior to the beginning of the project. The teams will be responsible for arranging the meetings. They will try to minimize any extra meetings, but it is important for the scientists to respond in a timely manner to the teams’ requests for further meetings. In addition to meetings, team may use emails to communicate. Both scientists and teams should be responsive to answering emails. Note that the teams maintain a website for posting their design documents. Links to the teams' project website will be available on the CS4760 course website. The project website will be continuously available after the second week of the semester. Scientists will find these websites invaluable for learning about app design details and progress.

Meetings and Presentations with Students. Scientists will need to participate in the app design process by meeting with the team and watching team presentations. I have found that the best mode of communication is face to face, followed by conference calling or video conferencing using phone, skype or google hang out, and that email correspondence is the least effective. Nevertheless, all modes of communication will need to be used, except in the case of off-­‐campus scientists, where face-­‐to-­‐face communication is unlikely. Following are scheduled meeting dates and the expected focus of each meeting. 1/19/2017 1/21/2016 or 1/20/2017 1/22/2016 – First meeting between teams and scientists. The teams will learn about the app idea from the scientist; including what tasks are to be performed with the app, users of the app, where the app is to be used, etc. The meeting should last between 30 – 60 minutes. 1/24/2017 1/26/2016 or 1/25/2017 1/27/2016 – Second follow-­‐up meeting with teams and scientists. This second meeting allows teams to ask follow up questions after they have thought about the app idea over the weekend. The meeting should last between 30 – 60 minutes. 2/2/2017 2/9/2016 – 2/7/2017 2/11/2016 – Paper prototype design presentation. In this presentation, teams present their designs working through the apps' tasks using a design of the app expressed as drawings on paper. Each team has 30 minutes to present their design, answer questions and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation for their app. It is best if the scientists attend the presentation live, but scientists can view the videos later if the cannot be present. Links to the video will be posted on the course website the evening of the presentation or the following day. 2/3/2017 2/11/2016 – 2/11/2017 2/18/2015 – Feedback from scientist on the paper prototype. During this meeting, scientists can provide detailed feedback of the design presented in the paper prototype presentation. The meeting should last between 30 – 60 minutes. 3/28/2017 3/29/2016 – 3/30/20173/31/2016 – Final design presentation. In this presentation, teams present their design by working through apps' tasks using a partially implemented app. Each team has 30 minutes to present their design, answer question and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation of their app. It is best if the scientists can attend the presentation live, but scientists can view the videos later. Links to the video will be posted on the course website the evening of the presentation or the following day.

Meetings and Presentations with Students. Scientists will need to participate in the app design process by meeting with the team and watching team presentations. I have found that the best mode of communication is face to face, followed by conference calling or video conferencing using phone, skype or google hang out, and that email correspondence is the least effective. Nevertheless, all modes of communication will need to be used, except in the case of off-­‐campus off-campus scientists, where face-­‐to-­‐face face-to-face communication is unlikely. Following are scheduled meeting dates and the expected focus of each meeting. 1/19/2017 1/22/2015 or 1/20/2017 1/23/2015 – First meeting between teams and scientists. The teams will learn about the app idea from the scientist; including what tasks are to be performed with the app, users of the app, where the app is to be used, etc. The meeting should last between 30 – 60 minutes. 1/24/2017 1/26/2015 or 1/25/2017 1/27/2015 – Second follow-­‐up follow-up meeting with teams and scientists. This second meeting allows teams to ask follow up questions after they have thought about the app idea over the weekend. The meeting should last between 30 – 60 minutes. 2/2/2017 2/10/2015 – 2/7/2017 2/12/2015 – Paper prototype design presentation. In this presentation, teams present their designs working through the apps' tasks using a design of the app expressed as drawings on paper. Each team has 30 minutes to present their design, answer questions and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation for their app. It is best if the scientists attend the presentation live, but scientists can view the videos later if the cannot be present. Links to the video will be posted on the course website the evening of the presentation or the following day. 2/3/2017 2/11/2015 – 2/11/2017 2/18/2015 – Feedback from scientist on the paper prototype. During this meeting, scientists can provide detailed feedback of the design presented in the paper prototype presentation. The meeting should last between 30 – 60 minutes. 3/28/2017 3/31/2013 – 3/30/20174/2/2013 – Final design presentation. In this presentation, teams present their design by working through apps' tasks using a partially implemented app. Each team has 30 minutes to present their design, answer question and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation of their app. It is best if the scientists can attend the presentation live, but scientists can view the videos later. Links to the video will be posted on the course website the evening of the presentation or the following day. 4/1/2015 – 4/8/2015 – Feedback from the scientist for adjustment of the final design. During this meeting, scientists can provide detailed feedback on the presented design. Because the students should have already implemented a significant portion of the app, only minor adjustments can be made. The student teams should decide if they have time to implement the changes and will advise the scientist so. The meeting should last between 30 – 60 minutes. 4/21/2015 – 4/23/2015 – Usability test result presentations. During the prior week, teams will have tested their app, using students from other classes. In this presentation, graduate students and humanities students present preliminary results of the usability tests. Each team has 30 minutes to present their design, answer questions and received suggestions from the rest of the teams and scientists. The presentation will be scheduled and videotaped. Scientists only need to attend the presentation of their app. It is best if the scientists could attend the presentation live, but scientists can view the videos later. Links to the video will be posted on the course website the evening of the presentation or the following day. 4/22/2013 – 4/29/2013 – Feedback from scientists on usability test results. During this meeting, graduate students give details of the usability test results. Scientists, teams and graduate students can discuss changes to a new version of the app as a result of the usability test results. The meeting should last between 30 – 60 minutes. The above schedule implies that there are 9 "scheduled meetings" of about one half hour each, but additional meetings for gathering app requirements may also be needed in the first seven weeks of the semester, depending on the complexity of the app and how precisely the app concept has been defined prior to the beginning of the project. The teams will be responsible for arranging the meetings. They will try to minimize any extra meetings, but it is important for the scientists to respond in a timely manner to the teams’ requests for further meetings. In addition to meetings, team may use emails to communicate. Both scientists and teams should be responsive to answering emails. Note that the teams maintain a website for posting their design documents. Links to the teams' project website will be available on the CS4760 course website. The project website will be continuously available after the second week of the semester. Scientists will find these websites invaluable for learning about app design details and progress.