Closed kfklein15 closed 5 months ago
@wainwmr cw in this sprint is super long. Before I shorten the prep in S2 could you see if you can shorten the cw :)
@wainwmr , you can also break the coursework down into 3 or 4 - so that some bit of it becomes stretch target.
@LaraHuzjan , @kfklein15 , I think this coursework should be easy to make smaller (from 6 hours KEY/MANDATORY to 2 hours KEY + 1 hour MANDATORY + 2 hours STRETCH) as follows. What say you? Shall I make it so?
STAR coursework (rename to Answering interview questions using STAR)
Instead of 4 hours (MANDATORY) on preparing 14 interview questions on "Tell us about a time when...", split this into:
It seems impossible to me that junior developers would build a Definition of Done on their own. They would always create one with their team who will be more experienced than they are. So they need to understand the concepts and know how to follow one, but not build it.
So Instead of 2 hours (KEY), I would shrink this to a time-boxed 1 hour and make it MANDATORY.
IMHO, there's FAR too much content in the prep for SQL/Sprint 1. The current plan is 80 minutes, but there's too much content and I think it would take far longer than 80 minutes to do it all justice. I suggest two things:
Thanks, @wainwmr . I will let @LaraHuzjan look at this in detail, but happy to move the "too much content" to coursework as stretch (either the week before or after), if you think there is value in it
@wainwmr thanks for this! Just to make sure I understand the changes: PREP We only keep
CW
Time wise the cuts would just about work
Having agreed with @LaraHuzjan , I've now made the following changes to the coursework:
@kfklein15 , please note the above for your PD milestone board.
Thanks, I have done the changes on the PD Milestone board.
@wainwmr I can't see it updated on the curriculum, have you changed it on cms?
@LaraHuzjan , yes I updated the prep on CMS last night here. It's now 60 minutes instead of 80 and I'm confident this is achievable for the trainees. I saved it, but I haven't published it because I thought someone might want to review or double check.
Great, I published it, thanks! Let me know when you finalise the day plan as well so it can go live asap :)
Hi @LaraHuzjan , I've tweaked the day plan a little. It didn't need much changing because the timings are totally fine I think. I've save it but not published it.
Perfect, all published.
What type of request is it
**Is the change on:
Why do you want to suggest this update? Feedback from NW6 is that the PD content has time estimations that they cannot fulfil. They also mentioned that most of our coursework is set as mandatory, which it shouldn't.
Timing process suggestion
Coursework Per sprint we should have
Document necessary changes as a comment