Closed LaraHuzjan closed 6 months ago
@CodeYourFuture/pd-syllabus-team let's try to attend next weeks meeting so we can agree on this :)
Hi all. I cannot make it to the meeting so wanted to share my opinion here:
how would this form be used and when Is it possible to link the form to the curriculum website?
how would we go about working on the raised issues
what would be our broad deadline
@esma-g thanks for this feedback! At yesterday's meeting, we shortened the form a bit.
How would this form be used and when The idea was to communicate this to volunteers and add it to canvas. It can also be on the curriculum, although I believe that was done before and not too successful.
How would we go about working on the raised issues We need to have a chat with Tech Ed about how the raised issues would come directly to us in a ticket form. And then how we would prioritise those tickets and make sure it's not forgotten and lost in the sea of tickets we have.
I agree with what you wrote, I think this approach works well now as well. Do you think having a new column for just feedback would make sense?
What would be our broad deadline The idea Karen and I had was to try to resolve an issue in a week-if pressing matter. I'd say max 2 weeks, of course depending on how many tickets we have and how many we can manage.
@CodeYourFuture/pd-syllabus-team feel free to leave your comments as well
I think a separate column for feedback could work.
About the timing, maybe we can say on Canvas that "We aim to resolve each feedback within 2 weeks. We prioritise urgent issues, such as broken URLs, etc."
Thanks! I'll bring it up on our weekly meeting and make a post about our work afterward.
There will be no feedback column, but we'll have a label FEEDBACK. There will be no time frame, unless there is an urgent situation.
Background We should start collecting feedback on the new PD Syllabus curriculum and @rogerspooner made this form for it. It has been reviewed so now we have to discuss how we'd like to pilot this.
Acceptance criteria
Responsible
Stakeholders
Aproover: