Talk:IDosvid pitch

FTD-3

Course development Requirements

Discussion and suggestions

Kevin : At this point, what I can predict might come out of the dry run is staffing for the launch

Gary : Or another dry run -- yes, that would be nice.

Kevin : However, there are a few notable improvements that I have noted we may need to improve on for the next group that we will have. ... These improvements include: ... The pitch should be broken into two or three separate sessions / chapters,

Gary : Pitch? Why "pitch"? I made this pitch wikipage for you as a prototype for the first course. No, no pitch. The first course should be re-developed or, better say, developed again.

Kevin : With simple review questions at the end of each to check for understanding. Delivering too much information in one long session caused students to lose focus.

Gary : I guess that was your idea, so, yes, I agree.

Kevin : The pitch to place greater emphasis on the project page and provide specific examples of expected key outcomes from the students, like project documentation, etc. This will enable the students to understand what is expected of them and what the next step will be.

Gary : Pitch? Why "pitch"? No, you are talking about the third course to be re-developed or, better say, developed again.

Kevin : A hands-on demonstration project to showcase the process students need to practice with, from:

1. 1. Choosing a project
   2. Getting project approved
   3. Using our communication channels
   4. Organizing office hours
   5. Utilizing event scheduling tools
   6. Conducting office hour sessions
   7. Documenting outcomes in wiki.

Gary : Correct. And we should have the tech prototypes in place before the next sprint.

Kevin : Since most of the students initially found communicating to be difficult or had fear,

Gary : "Had fear" is a wrong audience problem. The kids wouldn't have that problem. However, I agree on the first "communicating" part.