You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: org-cyf-itp/content/guides/teaching/timeline/index.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,15 +8,15 @@ emoji= "π "
8
8
9
9
## Timeline of ITP, staying on track:
10
10
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.
12
12
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.
14
14
15
15
So that's your rule of thumb for staying on track. What does this look like in practice, week by week?
16
16
17
17
## π«Άπ½ Day 1 Week 1
18
18
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.
20
20
21
21
## π€ Module 1: [Weeks 2, 3, 4](/onboarding)
22
22
@@ -42,12 +42,12 @@ Week 1: you have logged in to the dashboard to see your list of learners and wel
42
42
43
43
## π₯ Final Module: [Weeks 11, 12, 13](/data-flows)
44
44
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.
48
48
49
49
## π Wrapping up: Weeks 14, 15, 16
50
50
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.
53
53
π Week 16 : This course has completed. 100% of learners have completed or withdrawn. Have a party.
0 commit comments