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.

Kevin : to overcome this fear, we may assign one or two students to lead the hands-on practical project with assistance from us. This will help them in: a) communication; b) Event organization c) Documentation.

Gary : We can try at least. Plus, "how-to-get-it-done" videos would be helpful.

Kevin : The first course should be re-developed or, better say, developed again. > I totally agree. And one of the things I would recommend is that the first course needs to initiate the idea that the students will pick a project, have it approved, and organize office hours with the stakeholders to collect requirements.

Gary : I am drafting solutions to address that challenge for now, mostly using the pitch wiki page.

Kevin : This is one of the major challenges I have seen with the dry run team.

Gary : This has been one of the primary challenges all the time since I recruited startup staffers for the investment group.

Kevin : To enable the students to start envisioning themselves doing so from the beginning. And in the third course, the students do it practically.

Gary : And then you would discover an even bigger challenge, which would be the fear of doing something "wrong". While recruiting, I had hard times because many startups weren't well structured and a few roles were ambiguous. We initially "met" when I tried to develop a "gold mine", while taking tons of "sand" in order to find gold "nuggets". I targeted one "nugget" out of one hundred pieces of "sand". When my primary client retired, that project lost its sense.

One of the causes is that few schools nurture leaders and entrepreneurs. Traditional schools mostly feature "don't do anything we haven't told you" approaches. The problem was identified centuries ago. You probably heard Picasso's, "Every child is an artist. The problem is how to remain an artist once he grows up," or even stronger Lennon's "Every child is an artist until he’s told he’s not an artist". That was why children tended to be more successful in the programs I led.

Kevin : And we should have the tech prototypes in place before the next sprint. > It is my idea that this would be our agenda for our meeting tomorrow, specifically: a). HumHub's event scheduling tool and HumHub wiki, b) recording, and any other tech we need to develop.

Gary : Yes, we will need it for sure. I believe that HumHub is a better place to start from than MediaWiki let's say.

Kevin : We can try at least. Plus, "how-to-get-it-done" videos would be helpful. > That would be great. I had developed a video on how to register on Opplet. Can we have a discussion on this as well in the meeting?

Gary : Yes, absolutely. I also think about a demonstration project in which a volunteer leads a group of students.

Course proposal.

==1st Course==;