Skip to content

Commit f648adb

Browse files
authored
edits to ITP timeline based on feedback (#1256)
* edits based on feedback data flows was misaligned, and what about christmas * Update org-cyf-itp/content/guides/teaching/timeline/index.md
1 parent 5ee354b commit f648adb

File tree

1 file changed

+8
-8
lines changed
  • org-cyf-itp/content/guides/teaching/timeline

1 file changed

+8
-8
lines changed

β€Žorg-cyf-itp/content/guides/teaching/timeline/index.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,15 @@ emoji= "πŸ“…"
88

99
## Timeline of ITP, staying on track:
1010

11-
The course starts on the 1st of the month but there may be 7 days until the first Saturday, so we have written this to cover that variance.
11+
The course starts on the 1st of the month but there may be 7 days until the first Saturday, so we have written this to follow that timeline.
1212

13-
There are 12 learning weeks in the curriculum, which you will schedule over a maximum of 16 weeks. Most people should complete this course in 12 weeks of classes. Some will go faster (and this is encouraged). A few people will have adverse life events and need a couple of weeks to catch up. Once a learner is a full module behind, it's not realistic for them to catch up.
13+
There are 12 learning weeks in the curriculum, which you will schedule over a maximum of 16 weeks. This padding will help you account for things like Christmas, or Eid and other movable feasts. The course allows for variance in ability and previous experience. Most people should complete this course in 12 weeks of classes. Some will go faster (and this is encouraged). A few people will have adverse life events and need a couple of weeks to catch up. Once a learner is a full module behind, it's not realistic for them to catch up.
1414

1515
So that's your rule of thumb for staying on track. What does this look like in practice, week by week?
1616

1717
## 🫢🏽 Day 1 Week 1
1818

19-
Week 1: you have logged in to the dashboard to see your list of learners and welcomed them by name in Slack.
19+
Week 1: you have logged in to the dashboard to see your list of learners and welcomed them by name in Slack. You have scheduled your learning weeks in your [classplanner](https://classplanner.codeyourfuture.io/) and your volunteer team has signed up on the schedule so everybody knows the rota.
2020

2121
## 🀝 Module 1: [Weeks 2, 3, 4](/onboarding)
2222

@@ -42,12 +42,12 @@ Week 1: you have logged in to the dashboard to see your list of learners and wel
4242

4343
## πŸ₯ Final Module: [Weeks 11, 12, 13](/data-flows)
4444

45-
πŸ₯ Week 11: Everybody has begun [Data Flows](/data-flows). Most trainees are completing their TV Show Projects - encourage demos!
46-
πŸ₯ Week 12: Most trainees are submitting their final step
47-
πŸ₯ Week 13: You are reviewing and approving final step submissions
45+
πŸ₯ Week 11: Everybody has begun [Data Flows](/data-flows).
46+
πŸ₯ Week 12: Most trainees are completing their TV Show Projects - encourage demos!
47+
πŸ₯ Week 13: Most trainees are submitting their final step.
4848

4949
## 🎁 Wrapping up: Weeks 14, 15, 16
5050

51-
🐟 Week 14: Trainees who have fallen behind by less than 1 module have caught up and completed. Trainees going for [the Piscine](https://piscine.codeyourfuture.io) have applied.
52-
πŸ‘£ Week 15: You are wrapping up and supporting trainees to take their next steps.
51+
🐟 Week 14: You are reviewing and approving final step submissions. Trainees going for [the Piscine](https://piscine.codeyourfuture.io) have applied.
52+
πŸ‘£ Week 15: Trainees who have fallen behind by less than 1 module have caught up and completed. You are wrapping up and supporting trainees to take their next steps.
5353
πŸŽ‰ Week 16 : This course has completed. 100% of learners have completed or withdrawn. Have a party.

0 commit comments

Comments
Β (0)