CYF Docs
  • Welcome to CodeYourFuture Docs
  • CodeYourFuture Curriculum
  • šŸØOrganisation
    • Our History
    • Agreements & Policies
      • Naming Accounts Consistently
      • Code of Conduct
      • House Rules
      • Trainee Forms
        • Personal Circumstances Forms
        • Course Withdrawal Request
        • Leave of Absence Request
        • Learner Agreement
      • Trainee Expenses
      • Trainee Pregnancy Policy
      • Volunteer Agreement
      • Volunteer Expenses
      • Complaints Procedure
    • Partnerships
  • šŸ‘Øā€šŸŽ“Trainees and Alumni
    • Overview
    • Course Eligibility
    • Basic Online Skills Course
      • WhatsApp Community Guidelines
    • CYF Products
      • Our Products
    • Trainee Support
      • Signpost
      • Request a Laptop
      • How to get a bank account
      • Minimum Laptop Specs
      • Trainee Expenses
  • šŸ‘©ā€šŸ«Volunteers
    • Overview
    • Teams
      • Tech Education
        • Roles
          • Lead Trainer
          • Technical Assistant
          • Tech Buddy
          • Syllabus Team
      • Professional Development
        • Roles
          • PD Trainer
          • PD Coach
          • PD Coursework Reviewer
          • PD Mock Interviewer
          • PD Syllabus Team
        • PD Coach Guide
      • Community Coordination
        • Outreach Roles
        • Social Media Guide
          • Plan and schedule Social Media
        • Applicant Outreach
          • Calling NGOs and other referral organisations
            • NGO Dashboard - Step by step guide for volunteers
          • Calling Applicants
          • More outreach strategy
        • Volunteer Outreach
        • Approaching Potential Partners
        • Energisers and Icebreakers
      • Employability
        • Regional Employability Role
        • Career Mentors
      • CYF Products/Launch Module
        • Roles
          • Product Owner
          • Product Manager (Launch Module)
          • Scrum Master
          • Tech Lead
          • Tech Lead (Launch Module)
          • Developer
          • Code Reviewer
          • QA
          • UI/UX Designer
          • Business Owner (Lauch Module)
          • DevOps Engineer
  • šŸš€PROGRAMME DELIVERY
    • Running the Course
    • šŸŒLaunching the community in a new region
      • Fundraising & budgeting
      • Finding a Space
  • Archive
    • šŸ—„ļøArchived Pages
      • Intro to Digital (ITD)
        • Re-application Requirements for Application rejection
      • After Graduation
      • Running the course
      • Getting a Job
      • Useful Links
      • Hackathons
      • Asking Questions
      • Hosting on Netlify
      • Applicant Interviews
        • Interview - Technical
        • Interview - English
        • Interview - Rubric
      • Selection Day
      • Google Classroom for Trainees
      • Google Classroom
        • Google Classroom For Volunteers
      • Re-admission to Course
      • Laptop Request
      • Requesting a Laptop or Support
      • Graduation Module
      • Join CYF Tech Products
      • Overview
      • PD Coursework Reviewer
      • PD Coach
      • Onboarding PD Volunteers
      • CYF Website
      • Mission, Values & Working Principles
      • Our Trainees Backgrounds
      • Onboarding Process
      • Dashboard
      • Joining
      • Overview
      • Tools
        • Slack
          • Slack for Volunteers
          • Slack for Trainees
      • Leaving or Stepping Back
      • After the Course
        • From Trainee to Volunteer
      • General Information
      • Overview of our Process
        • Outreach Process
        • Application Process
        • Student Selection Process
        • Volunteering Structure
        • Class Structure
        • Communication from each CYF branch with CYF Global
        • Tech Projects
        • Tech Suite
        • Marketing
        • People into Employment
        • Finances and Insurance
      • The Founders team challenge
        • Challenge 1 - Find the Founding team
        • Challenge 2 - Strategy Challenge
          • The strategy challenge Template
        • Challenge 3: Find the Ambassador team
      • The Ambassadors Challenge
      • Volunteers Requirements
      • Welcome Event
      • The first Ambassador Team
      • Intro to Digital Course
        • Course Materials
        • Intro To Digital Slack Community Guidelines
      • Fundamentals Course
        • Course Materials
      • Software Development Course
        • Course Materials
      • Guides
        • Node Version Manager
        • Common Responses
          • Create an example
          • Don't ask to ask
          • Read the error message
          • Reply in thread
      • Coursework Feedback
      • Training Tips
      • Starting a Course
      • Getting Setup
      • Hackathons
      • Codility
      • Study Groups
      • Before the Course
        • Course Eligibility
      • Request a Laptop or Other Support
      • Success Criteria
      • Joining the Course
        • Laptops
          • Installing Ubuntu
      • Assessment
        • Milestones
      • Codewars
        • Codewars Advice from CYFers
        • Codewars Advice from Mentors
Powered by GitBook
On this page
  • Milestone Dates
  • Factors
  • Case Study

Was this helpful?

  1. Archive
  2. Archived Pages
  3. Assessment

Milestones

How is progress defined?

PreviousAssessmentNextCodewars

Last updated 1 year ago

Was this helpful?

On our software development course, we set milestones along the way so everybody knows what is expected and how to meet those expectations. Volunteers and trainees should use milestones as an opportunity to check in and self-assess progress at key points in the course.

We set these milestones by looking closely at successful and unsuccessful graduates and making guesses about measurable factors in that success. (See the to understand what we mean by success.) They are informed guesses and we test and revise them a lot based on new information, which we share as much as possible.

What is a milestone? A milestone is a point on the course. At that point, we check a series of milestone factors.

Milestone Dates

We set ten milestone dates on our course.

  1. Start

  2. HTML-CSS Week 1

  3. JS1 Week 1

  4. JS2 Week 1

  5. JS3 Week 3 <= specialisation

  6. React Week 2

  7. Node Week 2

  8. Databases Week 3

  9. Final Projects Week 2

  10. Post Graduation

Factors

We currently check these five factors:

  • Attendance - as shown

  • Codewars - Rank as shown

  • Codility - 1 for a test being issued, 2 for taking the test, 3 for scoring

  • Pull Reqs - rounded to 1 per week

On each milestone date, we check a trainee’s numbers against each milestone factor. Each check returns a value:

1 - behind milestone

2 - at milestone

3 - beyond milestone

We sum (add up) those returned values and check it against the milestone sum.

If the value is lower, the trainee is behind the milestone. If the value is the same, the trainee is at the milestone. If the value is greater, the trainee is beyond the milestone.

That’s how we measure.

As for why we measure, it’s so we can help everyone in the right way for them. We work with each trainee as an individual on their own journey towards a good job in tech. Milestones are to help everyone understand our progress. All trainees agree to meet their milestones as part of their Trainee Agreement, so it's important we all know how that is going.

If you’d like to read some more about this, I’ve included a story below, and defined some terms.

Case Study

ā€˜Greg’ is on Week 3 of Javascript Module 3 in 2021

He has just reached 6kyu on Codewars, with 110 points. He completed around 28 kata, mostly level 7 and one or two level 6 to get to this rank. He has been set two Codility tests. He took the first one and felt he got most things wrong, so he didn’t take the second one. He has attended every class. He has submitted a pull req every week except this week - he hasn’t done that yet!

Let’s score Greg’s engagement against the milestone at this point in the course.

header

Codewars

Codility

Attendance

Pull Reqs

Milestone

6

4

95%

11

Greg

6

3

100%

11

Codewars = 2

Codility = 1

Attendance = 3

Pull Reqs = 2

Greg scores 8, which is the milestone score, so he’s met his milestone. Well done Greg!

This model is not about being perfect, and it’s not about doing everything right every time. It’s not about competing against colleagues. It’s about Greg, and how he’s doing. It’s about showing up and taking part. Greg should have taken his second Codility test, particularly because all we ask at this point is that he takes the test, not even that he passes it. But he’s showing up to class, he’s submitting his coursework, and he’s managed his time well on Codewars so he’s in a good position to make his next milestone. So he’s looking like he’s coping on the course, and that’s what we’re measuring here in this automated way.

For more individual/personal progress in things like code quality or personal development, trainees work with mentors on their own development plans, of which this is just one factor.

Over time, we might be able to develop more factors that tell us more things to help everyone succeed. Watch this space!

Sub-term definitions: How is success defined?

Here’s an example of the milestones that were set for London Class 8. Subject to revision!

šŸ—„ļø
term definitions
Success Criteria
What is evaluation for?Module Template
sample of milestones set for a live class
Logo