Believe it or not, our Fellowship Program started about a year ago. We already have one cohort of fellows who have gone through the program (@mozzy and @gcliff with the support of @k.joseph). And our second cohort is about halfway through their fellowships.
Over the past several weeks, I’ve spoken with some of our fellows and mentors about their experience and what we can do to improve the program. Here are a few suggestions that I heard:
We still have some gaps in our stage skill & expectations worksheet to work through, whether around frontend/backend dev skills, additional QA skills, or omrs skills.
Have each fellow work on a “capstone” project. This should be a project that can be completed in 4-6 weeks and draws on multiple skill sets that they’ve worked on over the course of their fellowship. Something along the lines of what @mozzy and @gcliff did for their final presentations.
Even though fellows may have an area they concentrate on (product management, QA, frontend, FHIR, analytics, etc), there are still some cross-cutting skills that almost everyone thought all fellows should work on. Some of these, like open source leadership, communication, and learning/mentorship, are already captured in our omrs stages.
I expect we’ll keep working through the skill + expectation gaps. What do you think about the latter two suggestions? Can we work these into our current fellowships? Any other ideas for improving the fellowship experience?