Notebook
Below you will find an overview of the major deliverables, decisions, and brainstorming from each week of our project timeline! Each date is for the week of.
Wet Lab
03/03/21
Dry Lab
HP
02/01/21
03/01/21
04/20/21
Wet Lab
05/03/21
Dry Lab
05/10/21
05/17/21
05/24/21
HP
05/10/21
05/17/21
05/24/21
Wet Lab
06/14/21
06/28/21
Dry Lab
05/31/21
06/07/21
06/14/21
06/28/21
HP
05/31/21
06/07/21
06/14/21
06/28/21
Wet Lab
07/5/21
Dry Lab
07/5/21
07/12/21
07/19/21
07/26/21
HP
07/12/21
07/19/21
07/26/21
Wet Lab
Dry Lab
08/2/21
08/16/21
HP
08/9/21
08/16/21
Wet Lab
09/13/21
Dry Lab
08/30/21
09/13/21
09/20/21
HP
09/13/21
Wet Lab
Dry Lab
HP
Team Operations Timeline
Below you will find our yearly project timeline and materials we used to keep our team organized. We hope that future teams can use this information to structure there teams in a way to complete their project on time and maintain an organized team.
Time Period | Action | What happens | Purpose |
---|---|---|---|
December | Recruitment | Create google survey of an application that includes name, major, year, and an essay that shows literature reading and writing capabilities and creative ideas | Limits the number of applicants so we can find the individuals best fit for our team |
Post application on social media, ask professors to send it out | Promotes the team existence and campus awareness | ||
Deadline is due first Sunday of January, the following week will be hosting interviews for those whose applications matched our criteria | Practices professional development and simulates an actual job interview. Also an opportunity to meet the applicants face to face | ||
January | Meet the team | Host interviews and our first meeting. This time is used to meet the team and gather necessary information. We also introduce them to our platforms we use: Slack, google drive, zotero, and benchling | An introduction to keep our team organized and everyone knows how to communicate and save research findings |
February | Welcome to iGEM | Medal Criteria overview | An introduction to the vast idea of iGEM, which is a lot to explain to someone who has no background in it. |
Past project presentation | This is our first 'assignment' where we pair a new member with a returning member as a sort of mentor/mentee system. This allows new members to explore what previous teams have done and to start generating ideas for our project. Also practices professional development presentation skills. Also gives members a personal connection to someone on the team which is especially hard because we were meeting online | ||
Brainstorm | After getting a deeper understanding of what iGEM is and what can be done, we begin to brainstorm. We start by having students look for problems that could be addressed, interesting things about science, and anything else that just gets ideas out there. We will then begin to research and narrow down our options by determining what's feasible and what is the largest issue at hand. | Get ideas down for possible iGEM projects to look into | |
March/April | We narrow down our choices based on everyone's interest. This year we had everyone draft a proposal that included project background, what we would do, and what impact this project would have. We then take the projects that members wrote their proposal on and vote to narrow down to 2 or 3 project ideas. | Determine who is interested in what and to see which ones are our top choices | |
After splitting the team based on interest for our top 2 or 3 project ideas, we spend the next month meeting with professionals and finding more research that supports the feasibility and purpose of our top project choices. To conclude this phase teams will submit a written proposal (more in depth that before), project timeline, and create a project presentation that is presented to our entire team and the attendees of an Infectious Disease SCOPE meeting at the Ohio State Battelle Center | Go really in depth into our top choices to see which one is best | ||
May | Project | School has ended and we've voted on our top project choice from the presentations taking into advice from our advisors and ID scope. We then split our team into committees (wet, dry, HP, visual) and go more in depth to planning out our summer | |
Summer | Meetings | We have a weekly general meeting where everyone attends to discuss team progress and expectations, what is happening in each committee, and then we have a discussion on any troubles each commiittee is having or if they have any work to present | |
Each committee will have meetings based on material (wet lab generally has 2), Dry and HP has 1, and visual tends to be every other week | |||
Expectations | To keep everyone accountable and on top of things, and as a way to check our team progress and monitor where everyone's time is going we have everyone filling out weekly timesheets that include hyperlinks to the materials they worked on, a short description, and the hours they spent on that item | ||
Useful documents | Common documents that we have used throughout the summer are the timesheet spreadsheet where you can download the excel template here (we converted ours to a google spreadsheet to host on our shared Drive). You can also download an the Agenda template we used for our general meetings here. As a large part of the iGEM competition is documenting our project, we have created an excel file that keeps everyone accountable to have an even share in the write-ups. This spreadsheet automatically marks cells when an assignment is late, and records how many write-ups each member has signed up for. This can be downloaded here. Once downloaded it would need to be converted into a google spreadsheet file and the cells with FALSE should be changed to a check box. |
Below are examples of our useful documents that we have used to keep our project deliverables organized and no information is lost. The timesheets were especially helpful in keeping track of what each member is working on and how much time spent on each item. This helps make sure we are spending our time where it needs to be. The excel file makes seeing where are time is going easily because it automatically compiles everyone's hours into one graph, but one could still go into each person's timesheet to find the links to the work they focused on that week.
We used the agenda template shown below for our general meetings to keep our meetings organized, on track, and to avoid loosing any ideas or topics addressed at the meetings. We recommend including an agenda that contains topics to be addressed and a action items list to keep everyone aware on what to focus on for that week.
Lastly, we organized a spreadsheet to make dividing the wiki documentation easier. We value this experience of learning how to document the project's progress and wanted to ensure each member got experience! The spreadsheet contains automatic functions that tally how much a person has signed up for, and will turn the cell red when an assignment is marked late.