Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

🧑🏾‍⚖️ Check module success criteria #181

Open
4 tasks
SallyMcGrath opened this issue Nov 1, 2023 · 1 comment
Open
4 tasks

🧑🏾‍⚖️ Check module success criteria #181

SallyMcGrath opened this issue Nov 1, 2023 · 1 comment
Labels
📅 HTML-CSS Tickets for HTML-CSS 🏕 Priority Mandatory This work is expected 🦔 Size Tiny Less than 30 minutes 🎯 Topic Code Review Reading, understanding, and analysing code 🎯 Topic Communication Reading, writing, speaking, and listening in English; expressing our ideas 🎯 Topic Delivery Shipping our work, deploying our code, delivering our product 🎯 Topic Requirements Interpreting requirements with precision and accuracy 🎯 Topic Teamwork Working productively with other people 🎯 Topic Testing It's important that software works and that people can use it 🎯 Topic Time Management Managing competing needs and meeting deadlines 📅 Week 1 Assigned during Week 1 of this module 📅 Week 4 Assigned during Week 4 of this module

Comments

@SallyMcGrath
Copy link
Member

SallyMcGrath commented Nov 1, 2023 •
edited by sairaheta1
Loading

Link to the coursework

https://curriculum.codeyourfuture.io/html-css/success/

Why are we doing this?

🔑 The most important thing is that you are secure in your understanding.

At the end of the course, we will expect you to build novel applications using your understanding. If you cannot build things, we cannot put you forward for jobs. It is in your personal interest to make sure you have properly understood this module.

To progress to the next module you need to meet the success criteria for this module. How will you as a cohort meet the module success criteria? Discuss it in your class channel and make a plan together.

🧑🏿‍🎤 good strategies

  • asking volunteers to review your code
  • helping each other with coursework blockers
  • arranging midweek study sessions
  • using Saturday time to review code and cohort tracker

🙅🏿 bad strategies

  • opening empty PRs
  • copying and pasting
  • breaking the Trainee Agreement
  • mistaking the measure for the target

Maximum time in hours

.5

How to get help

Discuss with your cohort. Support each other.

How to submit

In week 4 of your module you will need a representative to report to the organisation. Here's your template, fill in your details and delete as appropriate:

📈 Cohort Progress Report from @cohort-name to @programme-team

  • criterion
  • criterion
  • criterion
  • criterion

✅ We are progressing to the next module.
⛔ We are taking a consolidation week to meet our targets.
@SallyMcGrath SallyMcGrath added 🏕 Priority Mandatory This work is expected 🐂 Size Medium 1-4 hours labels Nov 1, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Module-HTML-CSS Nov 1, 2023
@SallyMcGrath SallyMcGrath added 🎯 Topic Code Review Reading, understanding, and analysing code 🎯 Topic Communication Reading, writing, speaking, and listening in English; expressing our ideas 🎯 Topic Delivery Shipping our work, deploying our code, delivering our product 🎯 Topic Requirements Interpreting requirements with precision and accuracy 🎯 Topic Teamwork Working productively with other people 🎯 Topic Testing It's important that software works and that people can use it 🎯 Topic Time Management Managing competing needs and meeting deadlines 🦔 Size Tiny Less than 30 minutes 📅 Week 1 Assigned during Week 1 of this module 📅 Week 4 Assigned during Week 4 of this module and removed 🐂 Size Medium 1-4 hours labels Nov 1, 2023
@SallyMcGrath SallyMcGrath mentioned this issue Nov 1, 2023
Open
4 tasks
@SallyMcGrath SallyMcGrath moved this to 📋 Backlog in Curriculum Planning Dec 15, 2023
@SallyMcGrath SallyMcGrath changed the title [TECH ED] Check module success criteria 🧑🏾‍⚖️ Check module success criteria Mar 19, 2024
@kfklein15 kfklein15 added the 📅 HTML-CSS Tickets for HTML-CSS label May 3, 2024
@FrenchFry36 FrenchFry36 mentioned this issue Sep 10, 2024
Open
@FrenchFry36
Copy link

Kamino cloned this issue to FrenchFry36/Coursework-Planner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
📅 HTML-CSS Tickets for HTML-CSS 🏕 Priority Mandatory This work is expected 🦔 Size Tiny Less than 30 minutes 🎯 Topic Code Review Reading, understanding, and analysing code 🎯 Topic Communication Reading, writing, speaking, and listening in English; expressing our ideas 🎯 Topic Delivery Shipping our work, deploying our code, delivering our product 🎯 Topic Requirements Interpreting requirements with precision and accuracy 🎯 Topic Teamwork Working productively with other people 🎯 Topic Testing It's important that software works and that people can use it 🎯 Topic Time Management Managing competing needs and meeting deadlines 📅 Week 1 Assigned during Week 1 of this module 📅 Week 4 Assigned during Week 4 of this module
Projects
Coursework Overview Board for Everyone to Look At
Status: No status
Module-HTML-CSS
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
3 participants
@SallyMcGrath @kfklein15 @FrenchFry36