<li>Why should my marks suffer if I end up with underperforming team mates?</li>
</ul>
</section>
<sectionid="slide-3-2">
<h3id="3-2"><spanclass="section-number-3">3.2.</span> Main reason: Cloud native == team development</h3>
<ul>
<li>You have to know how to get along with people
<ulclass="fragment grow">
<li>Biggest lesson of this module is growing the “soft skill” of team work.</li>
</ul></li>
</ul>
</section>
<sectionid="slide-3-3">
<h3id="3-3"><spanclass="section-number-3">3.3.</span> You get to pick your languages</h3>
<ul>
<li>Each person can code a microservice</li>
<li>Different microservices talk over the wire, so you can use your own language!</li>
</ul>
</section>
<sectionid="slide-3-4">
<h3id="3-4"><spanclass="section-number-3">3.4.</span> You EVEN get to pick your own problem to work on!</h3>
<ul>
<li>We don’t specify what WebApp you should create.</li>
<li>Find a problem you have been itching to work on</li>
<li>Process (teamwork; splitting into microservices; dockerization) is more important than the actual WebApp or the language you use</li>
</ul>
</section>
<sectionid="slide-3-5">
<h3id="3-5"><spanclass="section-number-3">3.5.</span> BUT: How should we split our work?</h3>
<divclass="outline-text-3"id="text-3-5">
</div>
</section>
<sectionid="slide-3-5-1">
<h4id="3-5-1"><spanclass="section-number-4">3.5.1.</span> Each team member does one Microservice. Each microservice has its own UI and data backend</h4>
</section>
<sectionid="slide-3-5-2">
<h4id="3-5-2"><spanclass="section-number-4">3.5.2.</span> One team member does UI; one does back end. Business logic split into microservices.</h4>
</section>
<sectionid="slide-3-6">
<h3id="3-6"><spanclass="section-number-3">3.6.</span> BUT: What if one team member does not do the work they agreed to do?</h3>
<divclass="outline-text-3"id="text-3-6">
</div>
</section>
<sectionid="slide-3-6-1">
<h4id="3-6-1"><spanclass="section-number-4">3.6.1.</span> Your (collective) job to get the team together</h4>
</section>
<sectionid="slide-3-6-2">
<h4id="3-6-2"><spanclass="section-number-4">3.6.2.</span> You will have a team mentor (TA/Demonstrator)</h4>
</section>
<sectionid="slide-3-6-3">
<h4id="3-6-3"><spanclass="section-number-4">3.6.3.</span> We ask you to sign team contracts <ahref="https://www.cmu.edu/teaching/designteach/teach/instructionalstrategies/groupprojects/tools/TeamContracts/TeamContract.docx">Team Contract 1</a>; <ahref="https://www.cmu.edu/teaching/designteach/teach/instructionalstrategies/groupprojects/tools/TeamContracts/teamcontracttemplate.docx">Team Contract 2</a> in Week 5</h4>
</section>
<sectionid="slide-3-6-4">
<h4id="3-6-4"><spanclass="section-number-4">3.6.4.</span> We ask you to evaluate honestly in Week 8. <ahref="https://www.cmu.edu/teaching/designteach/teach/instructionalstrategies/groupprojects/tools/GroupEvaluations/GroupProcess-EvaluationForm.docx">Evaluation 1</a>; <ahref="https://www.cmu.edu/teaching/designteach/teach/instructionalstrategies/groupprojects/tools/SelfEvaluations/SelfEval-Form.docx">Evaluation 2</a></h4>
</section>
<sectionid="slide-3-6-5">
<h4id="3-6-5"><spanclass="section-number-4">3.6.5.</span> (<spanclass="underline"><spanclass="underline">With the agreement of all team members</span></span>), you can do group scaling:</h4>
<ul>
<li>This is a zero sum game: If Team member A scales up by X%; some others (e.g., members B and C) should scale down so that their scale down is collectively -X%.</li>
<li>This is a <i>recommendation</i>: We (markers) reserve the right to override.</li>
</ul>
</section>
<sectionid="slide-3-6-6">
<h4id="3-6-6"><spanclass="section-number-4">3.6.6.</span> Scaling cannot happen at the last minute before submission</h4>
<ul>
<li>Any scaling should be agreed upon by all team members and signed off with your team mentor/TA <spanclass="underline"><spanclass="underline">by Week 8</span></span>.</li>
<li>Good incentive to get most work done by Week 8.</li>
<li>If team member has not contributed by week 8, you can assume they are not contributing and make case for scaling.</li>
</ul>
</section>
<sectionid="slide-3-7">
<h3id="3-7"><spanclass="section-number-3">3.7.</span> Changes to teams this year</h3>
<ul>
<li>Each team will have 5-6 members</li>
<li><i>New this year</i>: You will be allowed to choose your own team members</li>
<li><i>New this year</i>: MSc students will have a separate team; UG students will have separate teams
<ul>
<li>Each cohort (MSc and UG) will be evaluated separately; though the marks scheme is the same</li>
<li>Coming to lecture, where we will have discussion about the lecture (1 hour)</li>
<li>Discussing with your coursework team about these questions and your coursework (1 hour; no classroom timetabled; meet on campus where convenient)</li>
<li>MS Teams site created for this class. Questions will be posed about the lecture on the #general channel</li>
</ul>
</section>
<sectionid="slide-4-1">
<h3id="4-1"><spanclass="section-number-3">4.1.</span> Meet by yourselves as a team (your coursework team)</h3>
<ul>
<li>No classroom timetabled but important to make progress (remember Week 5 and Week 8 deadlines)</li>
<li>Purpose: To Make progress on your coursework and discuss recorded lecture + questions</li>
<li>Need to meet as a team, not a</li>
<li>For next week, coursework/self-learning: <ahref="https://missing.csail.mit.edu/2020/version-control/">https://missing.csail.mit.edu/2020/version-control/</a></li>
</ul>
</section>
</section>
<section>
<sectionid="slide-5">
<h2id="5"><spanclass="section-number-2">5.</span> Overall plan: Module divided into three parts</h2>
<divclass="outline-text-2"id="text-5">
</div>
</section>
<sectionid="slide-5-1">
<h3id="5-1"><spanclass="section-number-3">5.1.</span> Intro: indispensable ’’-ilities’’ of scalable cloud native software</h3>
<ul>
<li>Reliability and failure</li>
<li>Scalability</li>
<li><b><b>Lab</b></b>:
<ul>
<li>Git and collaborative software development.</li>
<li>Intro to Docker</li>
</ul></li>
<li><b><b>Coursework</b></b>: Teams formed by <spanclass="underline"><spanclass="underline">end of Week 2</span></span></li>