Work with a team from across the consortium schools to build a new feature.
The Elentra Engage 2019 Hackathon
Based on developers who participated in the 2018 hackathon, many spent upwards of 20 hours working on their tasks. In 2019, Elentra Consortium Core Team staff will act in an advisory role but are not meant to be the key developer in writing code.
Participating in the hackathon allows developers to make connections with developers at other schools and helps facilitate increased collaboration between schools. Typically we find that developers who have worked with people from other schools are more comfortable and confident reaching out to other developers for assistance which in turn builds a stronger, more effective community.
Hackathon TeamsUp to four team members, plus one Elentra Consortium Core Team advisor.
|August 6th||Teams will be established and introduced.|
|August 19th||Teams must declare what task they will be working on (only one).|
|August 19th - September 22nd||Teams will self-organize via Slack and work behind the scenes to develop and polish their solution.|
|September 22nd||Teams can meet in person at the conference hotel to finalize their solution and polish their presentation.|
Teams will have up to 15 minutes to present their solution.
The winning Hackathon team will be announced during the Reception and Awards on Monday evening.
Tasks – Coming Summer 2019
Learning Event Resource Integration with MedSkl.com
MedSkl.com is a free resource for medical school students and practicing physicians to learn and review the fundamentals of clinical medicine: https://medskl.com/about
The goal for this task is to easily allow faculty members to browse the available MedSkl.com courses and learning modules, and link a MedSkl.com online module as a resource on a learning event scheduled in Elentra.
Faculty members or administrators must be able to add, edit, and delete “MedSkl Learning Modules” from the Admin > Manage Events > Event > Event Resources section.
From a learner perspective, MedSkl Learning Modules should display in the appropriate Resources section of an event page and learners should be able to click on a title and be redirected to the module. Administrators accessing the event page should be able to view how many times the resource has been accessed and by whom.
What do we win?
How is it judged?
|Criteria/Rating||Need Improvement (1)||Developing (2)||Good (3)||Excellent (4)|
|Functionality/meets requirements||Does not clearly tie to the requirements and/or does not function||Addresses some requirements but does not function||Meets most requirements||Meets all requirements|
|User Experience||Neither intuitive nor clear to user; steps confusing, process sloppy||Usable but not without clear instructions||Usable with clear steps for user||Very intuitive; easy to use at first glance; flow makes sense; experience mimics other parts of Elentra|
|Workflow/Process||No Jira Epic/User Stories or PR in GitHub||Includes either Jira Epic and User Stories or PR in GitHub, but titles, labels or details confuse the reader||Includes Jira Epic and User Stories, and PR in GitHub but titles are unclear, or some detail is lacking||Included Jira Epic and User Stories, with appropriate details; GitHub PR includes all requirements outlined in documentation|
|Presentation||Presentation is disorganized to the extent that it impedes the audience understanding of the product||Presents ideas with some confusion but audience understands majority of what product includes||Clear, appropriate to the audience, includes relevant information||Clear, appropriate to the audience, includes only relevant information, engaging|
|Communication/Collaboration||Little to no, or negative communication, and not all group members participated in project||Communication is sporadic or minimally effectiveness; not all group members participated in project||Regularly communicated and most group members actively contributed to project||Effectively communicated at regular intervals and all group members actively contributed to project|