class-repository

Check-Ins

You will be required to create a check-in issue for each module. These check-ins are how you will share your individual progress with your classmates. Coaches, peers and your academic team will read your check-in to know how we can help you. Coaches will also use your Thursday Check-Ins to prepare for review calls and Sunday Class.

Module Check-in Issue Checklist

Your issue should have a title such as Elias: Agile Development, 4 weeks and make sure you go through these steps:

[ ] add yourself as assignee to it, [ ] add the labels check-in & week-x  
[ ] add it to the Project Board: Deliverables [ ] add the appropriate milestone
(eg. 2. Agile Development) [ ] add your comment using the template on every
Thursday

Issue Description

In the main issue description you will copy-paste the module’s learning objective checklist, and possibly a personal study plan. This will help you track your progress through the module and prioritize your study time.

Weekly Check-In

Every Thursday you will add a comment to your check-in issue summarizing your progress over the last week. You will need to write these sections in your comment using the given template:

• I Need Help with: What are you having trouble understanding? What parts of the homework are you struggling to complete?
• What went well?: What has been successful so far? have you learned and/or completed so far this week?
• What went less well?: What mistakes did you and/or your group make? What was difficult?
• Lessons Learned: What did you learn this week that you will take with you into next week? I can be technical, a mindset, a study habit, anything!
• Sunday Prep Work: Begin organizing your prep work for the following Sunday.

When you have posted your Thursday Check-in comment please add the week-x label to your issue, so we know it’s ready for review.

After reading your check-in, a coach or your academic team member will label it checked-x.

If you are blocked on something then a coach or classmate will get in touch to help you

Module Retrospective

At the end of each module you will post a retrospective comment in your issue where you will look back over the module to summarize what went well and what can be better:

• Me
  • What was not clear, where did you get stuck?
  • What was clear, what did you master?
  • Where can you still use some help?
  • Where can you help others moving forwards?
• The Course
  • What can there be more of?
  • What can there be less of?
  • What material were most helpful (from DeNepo or elsewhere)?
  • What materials were least helpful?
  • Any suggestions for future classes?

After you’ve posted this comment you will add the retro label to your issue so your coaches know to read it. After reading it they will add the checked-retro label to your issue.

This site is open source. Improve this page.