├── README.md ├── ProjectTimeline.md └── ProjectDescriptions.md /README.md: -------------------------------------------------------------------------------- 1 | # Rewrite Your Summer 2020 2 | 3 | Everyone in the Rewriting the Code community has been impacted in one way or another by the pandemic. 4 | On-campus classes and activities have been halted, leaving students with extra time on their hands. Many 5 | internships have been canceled, creating uncertainty for thousands of students regarding what they’ll be doing 6 | this upcoming summer. 7 | 8 | Despite the unfortunate circumstances, this is an opportunity to realize visions, meet and collaborate with 9 | others in the community, and learn new skills through technical projects. For women whose internships have 10 | been cancelled, RTC plans to engage our company partners to help our passionate and skilled women, many 11 | of whom have already demonstrated interest in using their newly-found time productively, to make the most of 12 | their time. 13 | 14 | ## Program Goals: 15 | * Provide students the opportunity to participate in a meaningful summer project with peers and mentors 16 | in the absence of a traditional internship where they will develop code, project solutions, and work 17 | artifacts for use during the 2020 fall recruiting season. 18 | * Help students ideate projects and create solutions they’re passionate about. 19 | * Create opportunities for students to develop and learn team, technical, and business skills through 20 | hands-on experience and collaboration. 21 | * Further develop and strengthen relationships within the RTC community. 22 | * Expose students to RTC company partner engineers and recruiters. 23 | 24 | ## Slack Workspace: 25 | * Be sure to [join](https://join.slack.com/t/rewriteyoursummer/shared_invite/zt-exvowc2p-Q5sv1lNLicloe7irZSd_SA) the Rewrite Your Summer Slack Workspace. If you're a student, request access to the students-only channel. If you're a mentor, request access to the mentors-only channel. You should also add yourself to the project and team channel that's relevant for you. 26 | -------------------------------------------------------------------------------- /ProjectTimeline.md: -------------------------------------------------------------------------------- 1 | # Rewrite Your Summer Project Timeline 2 | ## Week 1 - Introductions + Stakeholder Input 3 | * Students should set up a [team charter](https://www.lce.com/Team-Charters-What-are-they-1219.html) and form consensus on the team’s code of conduct. 4 | * The team should establish a [daily stand up time](https://www.agilealliance.org/glossary/daily-meeting/#q=~(infinite~false~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'daily*20meeting))~searchTerm~'~sort~false~sortDirection~'asc~page~1)) and start attending this daily meeting. 5 | * All team members should familiarize themselves with [Git](https://lab.github.com/githubtraining/introduction-to-github). 6 | * Collecting Stakeholder Data: 7 | * The team should discuss the project’s problem statement and scope and define any remaining questions they have for key stakeholders (i.e. project points of contact and the RTC community at large). 8 | * All RTC project questions for stakeholders should be grouped into an RTC-wide “Tech Survey” and sent to the entire RTC community to get input on people’s experiences with different RTC processes. 9 | i.e. If the project is to build an RTC Job Board, the team would develop questions around what challenges the RTC community faces when trying to find opportunities that have been shared with the community. The tech survey would include a section for each team’s questions. 10 | * Team reviews their questions for the RTC Tech Survey with their mentors and gets feedback. 11 | * Final tech survey is sent out to the RTC community and results are shared with all team members. 12 | * Mentor expectations: Review team charter and team’s proposed tech survey questions + provide feedback. Answer any lingering questions about Git. 13 | ## Week 2 - Research + Technical Design 14 | * Team reviews results from RTC Tech Survey 15 | * Team researches technology options for implementing a solution. 16 | * Team develops a technical design document with their plans for implementing the technical solution. The document should also include weekly development milestones. 17 | * Team presents the document to the technical mentor and makes changes based on feedback. 18 | * Team presents document to project points of contact [optional]. 19 | * Mentor expectations: Review team’s design document + provide feedback. Review results from team’s tech survey results. 20 | ## Week 3 - Development 21 | * Team begins implementation of technical solution. 22 | * Mentor expectations: Review team’s progress against the development timeline they lay out in their design document. If necessary, provide technical advice and review pull requests. 23 | ## Week 4 - Development 24 | * Team continues implementation of technical solution. 25 | * Mentor expectations: Review team’s progress against the development timeline they lay out in their design document. If necessary, provide technical advice and review pull requests. 26 | ## Week 5 - Development + Develop user testing program 27 | * Team continues implementation of technical solution. 28 | * By the end of this week, the team should also have a plan for asking users to test their solution and collect structured feedback. 29 | * Mentor expectations: Review the team’s progress against the development timeline they lay out in their design document. If necessary, provide technical advice and review pull requests. Review and provide feedback on the team’s user testing program. 30 | ## Week 6 - Development + Initial User Testing 31 | * Team continues implementation of technical solution. 32 | * By the end of this week, the team should have done one round of user testing and reviewed the feedback with their mentor. 33 | * Mentor expectations: Continue tracking the team’s development work. Help the team prioritize the actionable development work based on the user feedback. 34 | ## Week 7 - Finishing touches + Begin final presentation 35 | * The team should be making final touches on their solution based on their user feedback and should begin developing their final presentation. 36 | * Mentor expectations: Advise on the structure of the team’s final presentation. 37 | ## Week 8 - Final Presentations 38 | * Team develops a demo and final presentation of their work. 39 | * Team presents their work. 40 | * Mentor expectations: Watch a dry run of the team’s final presentation and provide final feedback. 41 | -------------------------------------------------------------------------------- /ProjectDescriptions.md: -------------------------------------------------------------------------------- 1 | ## Current Team Breakdown: 2 | 3 | 4 | 5 | * Modular Learning - 3 teams 6 | * Virtual RTC Onboarding Experience - 2 teams 7 | * RTC Chat Bot - 2 teams 8 | * Data Visualization Pipeline - 3 teams 9 | * Job Board - 3 teams 10 | * Task Tracking/Volunteer Opportunities - 1 team 11 | 12 | Total: 14 RTC Project Teams + 4 Code for America Teams + 1 GenderMag Team + 1 ResistBot Team = 20 teams 13 | 14 | ## RTC Specific Projects 15 | 16 | 17 | 18 | * Modular Learning - Create your own journey [3 Teams] 19 | * Technical Areas: Web Design/Development, Software Design, UI/UX, Frontend, Backend 20 | * Problem: Once a student joins RTC, they don’t necessarily know about all the resources that came before they joined (like webinars and even FB posts). We need a way for a new RTC member to plan their own learning path based on their different interests. Previous RTC resources need to be tagged with relevant career interest categories and made easily accessible/searchable. 21 | * Example: If I join RTC and want to know more about PM careers I should be able to drag and drop RTC resources and create a 10 week summer learning plan for myself. 22 | * Proposed Team Breakdown: 23 | * Team 1: Modular Learning Console 24 | * This team will focus on the front end UI/UX for this project 25 | * Team 2: Modular Learning Content 26 | * This team will focus on the backend to make sure that all RTC content is available and tagged automatically in the “Create your own journey” service 27 | * Team 3: Modular Learning Data Collection (works closely with Team 1) 28 | * This team will focus on collecting data from the service to inform us on popular choices for modules, common patterns in constructing journeys and informing templates for different career interests based on other similar users 29 | * Point of contact: Myra Gupta, [mgupta@rewritingthecode.org](mailto:mgupta@rewritingthecode.org) and Jade Barricelli, [jbarricelli@rewritingthecode.org](mailto:jbarricelli@rewritingthecode.org) 30 | * Virtual RTC Onboarding Experience + Gamification [2 Teams] 31 | * Technical Areas: Data Mining/Analysis, Software Design, Web Design/Development, UI/UX, Graphic Design, Backend software development, Frontend software development 32 | * Problem: We currently have a lot of different documents and processes that we want new RTC fellows and members to follow when engaging with different RTC programs. We don’t have a good way of ensuring that the new RTC women read through all of these resources. This project will be to create a virtual onboarding experience for new RTC members including gamification where it’s useful. On the backend, we would need to collect data on who successfully completes which training and where people stumble with selecting the right answers so that we can adapt our own material to make those guidelines clearer. 33 | * Example: [https://tinyurl.com/RTCProfessionalEtiquetteGuide](https://l.facebook.com/l.php?u=https%3A%2F%2Ftinyurl.com%2FRTCProfessionalEtiquetteGuide%3Ffbclid%3DIwAR2F75bGMPAPIVn5zX1KXLdy-BcrhTPcvMO6rgoJZH0kD-S6sILQ82rxk_w&h=AT3rwP3n7dkgyW4wRVyS0Ziva6hUcbFzvxNEcCBK3n9keNZ4tqXpC0kHgefPHxTOlXKxnZg00XW55eL-PhHGsgc-sV1tbrIC5jlfc9G2TDUYZfkYtZvwr0edBAOVrtgTrc3oYu6jhxHiZPvZTVBe&__tn__=-UK-R&c[0]=AT2U4qK4_q4_yv57zuLT98sl6cizHpCY5iCEJBR5E-hWwJ1Qor8mlHjj4sZZ5LGPRfYley2c6aA4i8ifnieDMt42bxwMXrixYg3vCw9PPNecDw2gHA5b2cEpJFPoYTpHhZvcONhGrnjHZY-qAtszi-R98Op_SwdnFuz3q0Hk4qbsN8h27G3a9Q) could be gamified to have a virtual simulation of various networking/professional situations and users would be able to select the responses they think are appropriate. 34 | * Proposed Team Breakdown: 35 | * Team 1: Onboarding Console 36 | * This team will focus on the front end UI/UX for this project 37 | * Team 2:Onboarding Infrastructure 38 | * This team will focus on data collection and the relevant infrastructure on the backend of the onboarding service 39 | * Point of contact: Myra Gupta, [mgupta@rewritingthecode.org](mailto:mgupta@rewritingthecode.org) 40 | * RTC Chat Bot [2 Teams] 41 | * Technical Areas: Machine Learning, Software Design, Web Design, Backend software development, Frontend software development 42 | * Problem: RTC leadership often struggles with a huge volume of repetitive questions from students about different RTC procedures. There is room to automate this process so that leaders aren’t bogged down with menial questions and so that there is a single source of information for common questions that can get people instantaneous answers. On the backend, we could track common questions and make sure that the chat bot is updated with the most relevant information. A simpler scope project would have this learning be manual, a more complex project could use some AI in the background. 43 | * Example: There are many posts on Facebook during the Fellowship application period about who can apply for the fellowship and when decisions will be released. A chat bot could easily spit out the answers to these questions. 44 | * Proposed Team Breakdown: 45 | * Team 1: Chat Bot Console 46 | * This team will focus on the front end UI/UX for this project 47 | * Team 2: Chat Bot Infrastructure 48 | * This team will focus on getting data for and training the chat bot 49 | * Point of contact: Myra Gupta, mgupta@rewritingthecode.org 50 | * Data Visualization Pipeline [3 Teams] 51 | * Technical Areas: Data Engineering, Data Analysis, Data Visualization, Software Design, UI/UX, Backend software development 52 | * Problem: We currently collect data from RTC students through a variety of different sources and for different purposes - some for internal metrics on whether RTC programs are successful and others that we share with the community and with companies. Once we collect data, there is often a manual process in creating visualizations and presenting it to the relevant stakeholders. This project would entail identifying all the RTC data sources and building pipelines to automatically generate visualizations. 53 | * Example: The alumni program leaders sent out a survey to ask alumni about what they’re looking for in their next jobs, when they plan on switching careers and which companies they’re interested in working with. The visualizations for this data have to be manually regenerated every month and transferred from Airtable to a shareable platform. 54 | * Proposed Team Breakdown: 55 | * Team 1: Student Profiles 56 | * This team will focus on collecting, organizing and presenting student profile data in a way that is continuous and allows us to map the timeline of each student in RTC 57 | * Specific areas of focus: 58 | * Pre-College Data 59 | * a. High School: name, location, ranking by the number of RTC students, colleges where they matriculate. We have this info in Airtable. Would be great to have visualizations - perhaps a map displaying HS school location and location of the schools (I’d like to see such a map for colleges and the top 20 companies/locations of where they head. I.e., Cornell interns/grads go where, as well as displaying Amazon, what are the top 20 schools for internships and full time 60 | * b. HS State origin - compare to the states where their colleges are located 61 | * c. Hometowns - usually correlates to the high school location, but international students, boarding schools impact this data. I like to share downtown info as well as college location with regional companies who recruit and would prefer a regional approach rather than national approach to recruiting interns and FT candidates 62 | * d. High CS dept/CS faculty - see in the attached spreadsheet. Cassidy used the data from Airtable and then had to manually research the dpt website/CS faculty. Would be helpful to build out at least the top 50 high schools by #RTC alums so that we can contact HS to raise awareness of RTC - offer the [RTC Bridge Program](https://rewritingthecode.org/bridge-program/) to graduating seniors. 63 | * e. 1st Gen 64 | * International Students 65 | * intl students who attend colleges/universities in the US 66 | * a. Country of origin 67 | * b. Sponsorship - yes/no 68 | * c. 1st gen - yes/no 69 | * d. Companies where they intern/work 70 | * e. Ethnicity 71 | * intl students who are part of RTC yet attend college outside the US. The later is a possible area for collaborations with RTC. 72 | * a. Country 73 | * b. Top colleges/university 74 | * Team 2: Job Search Data 75 | * This team will focus on collecting, organizing and presenting data from students’ job searches (including pre-summer and post-summer surveys) in a way that is easily accessible and has different “views” for different stakeholders i.e. students vs. RTC leadership vs. company partners 76 | * Team 3: College Profiles 77 | * This team will focus on collecting and aggregating data at the college level and will focus on building views that allow students to identify other RTC members and alumni from their own universities. 78 | * Point of contact: Myra Gupta, mgupta@rewritingthecode.org 79 | * Job Board [3 Teams] 80 | * Technical Areas: Database development, Web design, UI/UX, Frontend software development 81 | * Problem: We need a single student-facing place to post all RTC partner company opportunities (jobs+internships). We currently post opportunities to our Facebook group but they are difficult to find with the traffic of our group. There are also a lot of opportunities sourced from students themselves (not necessarily from our partner companies) that get posted on Facebook and then lost in the jumble of posts. We need a way to automatically populate these posts into a jobs portal (there may be Facebook APIs we could use for this) 82 | * Example: In the past we have used Airtable, creating a form for the company to fill out which feeds a database we can then share with our students. The problem with this solution was that companies wouldn't take the time to fill out the form and the student-facing side was not very visually appealing. We need something simple for the companies (like pasting in a URL) but nice looking and easy to navigate on the student end. 83 | * Proposed Team Breakdown: 84 | * Team 1: Job Board Console 85 | * This team will focus on the front end UI/UX for this project 86 | * Team 2: Job Board Infrastructure 87 | * This team will focus on getting data for and building an automated pipeline for collecting the opportunities that feed the job board 88 | * Team 3: Job Board Data Collection (works closely with Team 1) 89 | * This team will focus on finding ways to collect data from the Job Board on which opportunities are most appealing for RTC students, most clicked, most applied to, etc. 90 | * Point of contact: Jade Barricelli, jbarricelli@rewritingthecode.org 91 | * RTC Volunteer Opportunities Board + Task Tracking [1 Team] 92 | * Technical Areas: Database development, Web design, UI/UX, Frontend software development, implementing and researching existing softwares 93 | * Problem: We need a better way to post RTC’s many volunteer and leadership opportunities so that students can find them easily and so that leaders have a quick view of who is supposed to be working on what tasks. There will need to be an RTC-wide view as well as views specific to the different sub-groups i.e. Sue+Jade+Staff, RTC Alumni Board, RTC Student Council. 94 | * Example: Some tasks are left floating because we aren’t actively tracking them i.e. the alumni community needed to revamp our office hours program and we mentioned it frequently but never assigned an owner and weren’t clear on the status of the project at different points. 95 | * Proposed Team Breakdown: 96 | * 1 single team will complete the entirety of this project 97 | * Point of contact: Myra Gupta, mgupta@rewritingthecode.org 98 | 99 | ## Non-RTC/Open Source Projects 100 | 101 | 102 | 103 | * [Code For America Priority Action Areas](https://brigade.codeforamerica.org/priority-action-areas) [1 team per action area] 104 | * Court Notifications 105 | * Rapid Response 106 | * Voting Rights 107 | * Creating Pathways to Record Clearance 108 | * Point of contact: Myra Gupta, mgupta@rewritingthecode.org 109 | * [GenderMag Recorder’s Assistant](https://github.com/mendezc1/GenderMagRecordersAssistant/?fbclid=IwAR3rX3y7jK7E1M9KzGx-GOQC2dRCGxNUYCM6wEvlFMCmSc0cQo43l6aZE8A) [1 team] 110 | * Point of contact: Myra Gupta, [mgupta@rewritingthecode.org](mailto:mgupta@rewritingthecode.org) 111 | * [ResistBot](https://github.com/resistbot) [1 team] 112 | --------------------------------------------------------------------------------