Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project Proposal Feedback #2

Open
ShanEllis opened this issue Feb 13, 2024 · 2 comments
Open

Project Proposal Feedback #2

ShanEllis opened this issue Feb 13, 2024 · 2 comments

Comments

@ShanEllis
Copy link
Contributor

ShanEllis commented Feb 13, 2024

Project Proposal Feedback

Score (out of 9 pts)

Score = 8.25

Feedback:

Quality Reasons
Abstract N/A
Research question D where are you looking - all across the world? the US? California? What's your population? Please be more specific. On what basis will you decide if a company is "large" or "small"?
Background P Please mention what exactly you will be doing that is different from the existing work.
Hypothesis P
Data D For the variables, over what time period do you want these data? What is the ideal size of your dataset? Please provide some details about the datasets you found.
Ethics D Need to be more elaborate. Please read the guidelines provided for this section and make it more detailed, addressing each sub question, for e.g. How are you going to check for bias in your data? How are you going to address it?
Team expectations D Lacking specifics for what expectations y'all actually have to ensure success as a team.
Timeline P

Rubric

Unsatisfactory Developing Proficient Excellent
Abstract The abstract is confusing or fails to offer important details about the issue, variables, context, or methods of the project. The abstract lacks relevance or fails to offer appropriate details about the issue, variables, context, or methods of the project. The abstract is relevant, offering details about the research project. The abstract is informative, succinct, and clear. It offers specific details about the educational issue, variables, context, and proposed methods of the study.
Research question The research issue remains unclear. The research purpose, questions, hypotheses, definitions variables, and controls are still largely undefined, or when they are poorly formed, ambiguous, or not logically connected to the description of the problem. Unclear connections to the literature. The research issue is identified, but the statement is too broad or fails to establish the importance of the problem. The research purpose, questions, hypotheses, definitions or variables, and controls are poorly formed, ambiguous, or not logically connected to the description of the problem. Unclear connections to the literature. Identifies a relevant research issue. Research questions are succinctly stated, connected to the research issue, and supported by the literature. Variables and controls have been identified and described. Connections are established with the literature. Presents a significant research problem. Articulates clear, reasonable research questions given the purpose, design, and methods of the project. All variables and controls have been appropriately defined. Proposals are clearly supported by the research and theoretical literature. All elements are mutually supportive.
Background Did not have at least 2 reliable and relevant sources. Or relevant sources were not used in relevant ways A key component was not connected to the research literature. Selected literature was from unreliable sources. Literary supports were vague or ambiguous. Key research components were connected to relevant, reliable theoretical and research literature. The narrative integrates critical and logical details from the peer-reviewed theoretical and research literature. Each key research component is grounded in the literature. Attention is given to different perspectives, threats to validity, and opinion vs. evidence.
Hypothesis Lacks most details; vague or interpretable in different ways. Or seems completely unrealistic. A key detail to understand the hypothesis or the rationale behind it was not described well enough The hypothesis is clear. All elements needed to understand the rationale were described in sufficient detail The hypothesis and its rationale were described succinctly and with clarity about how they are connected to each other
Data Did not describe ideal dataset fully AND does not include at least one reference to an external source of data. Either does not describe the ideal dataset fully AND does not include at least one reference to an external source of data that could be used to answer the proposed question. Ideal dataset(s) well-described and includes everything needed for answering question(s) posed. Includes at least one reference to a source of data that would be needed to fully answer the question proposed. Ideal dataset(s) well-described and includes everything needed for answering question(s) posed. Includes references to all sources of data that would be needed to fully answer the question proposed. The details of the descriptions also make it clear how they support the needs of the project and discuss the differences betweeen the ideal and real datasets.
Ethics No effort or just says we have no ethical concerns Minimal ethical section; probably just talks about data privacy and no unintended consequences discussion. Ethical concerns raised seem irrelevant. The ethical concerns described are appropriate and sufficient. Ethical concerns are described clearly and succinctly. This was clearly a thorough and nuanced approach to the issues
Team expectations Lack of expectations The list of expectations feels incomplete and perfunctory It feels like the list of expectations is complete and seems appropriate The list clearly was the subject of a thoughtful approach and already indicates a well-working team
Timeline Lack of timeline. Or timeline is completely unrealistic The timeline feels incomplete and perfunctory. The timeline feels either too fast or too slow for the progress you expect a group can make It feels like the timeline is complete and appropriate. it can likely be completed as is in the available amount of time The timeline was clearly the subject of a thoughtful approach and indicates that the team has a detailed plan that seems appropriate and completeable in the allotted time.

Scoring: Out of 9 points

  • Each Developing => -0.75 pts
  • Each Unsatisfactory/Missing => -1.5 pts
    • until the score is 0

If students address the detailed feedback in a future checkpoint, they will earn these points back.

Comments

@Sebewe
Copy link
Collaborator

Sebewe commented Feb 25, 2024

In our most recent submission for DataCheckpoint, we have modified our Research Question to be more specific, our Data section to include more information on what we would ideally have and what we are lacking in given the dataset we are using. We have also modified our ethics to be much more broad and encompassing of ethical concerns for our project. Additionally, we have added more expectations for our team. Please let us know how else we can improve.

@mckayladavid
Copy link
Collaborator

mckayladavid commented Feb 26, 2024

While we did improve and modify our team expectations section of the Data Checkpoint, for clarification purposes, I was curious as to why we were docked points. In the "FinalProject_Guidelines" file it states, "These expectations are for your team’s use and benefit — they won’t be graded for their details," under the "Team Expectations" section. Thank you for your help and clarification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants