Note: You will not be penalized for not being “diverse” enough. This is an exercise to explore diversity and identify how your team’s backgrounds may impact your ability to empathize with customers, see ethical considerations, etc. There are no diversity criteria
This assignment works to help you get to know your team and dive into the topic of diversity and inclusion. This is a topic that is generally not covered in your undergrad, but it permeates our industry. It is hoped that through this assignment you learn about both diversity, as well as intersectional roles in order to be a more effective engineer.
We expect you to thoughtfully write and dive into these topics past surface level. We expect you to watch the lectures on this topic before submission in order to gain a better understanding of the topics.
We expect all members of your team, including CSC454/2527 students, to participate in this assignment.
Your “startup” is global. The moment you launch, your project is global. It will target groups and demographics around the world, it will (hopefully) hire people who aren’t like you, it will grow as an collection of humans who are different. When your company lacks diversity, it stunts its own growth and contributes to toxicity in the industry.
Diversity is a very broad term and encompasses a lot of areas, both broad and niche. Some major areas of diversity include:
There are a lot more niche and broad topics that we could discuss, but this subset is just to get you started. The notion here is that people with different combinations of life experiences will help identify how your product may or may not work for them, provide novel ideas, and help with conflict resolution in the workplace as people are more accommodating by workplace culture of others’ differences, etc.
Keep in mind that we are not suggesting to selectively hire people based on their “diversity”, but to understand that diversity can help you grow and you can take proactive steps to ensure a welcoming environment for diverse candidates and customers.
You must create a release on your repo. This will give us a snapshot in time and allow us to grade it. See release body criteria and example below. Assignments without a coherent release body that follow the instructions in this assignment will be rejected and marked 1 day late.
Assignments are always due at 11:59:59pm Eastern Time.
Second, you must submit the release on the LearnSoftware application. You can find the submission location here: https://learnsoftware.engineering/my_assignments
Release bodies must include:
|Expertise||Describes how each team member’s existing expertise can benefit the project|
Describes areas where your team may not have adequate expertise. This should include areas outside of engineering.
|Subject Matter Experts||Students identify areas where they may lack expertise and describes subject matter experts that can help fill those holes.|
Areas are more than surface-level deep (e.g. students don’t just list out “engineering, will ask instructors to advise” or “industry partners”). Clear thought and care has gone into the rhetoric.
|Unconscious Bias||The team has clearly given some thought into potential areas bias may occur and describes the situations.|
The writing clearly goes beyond surface level bias and the students have given serious thought about it.
Writing also provides examples of possible solutions to help mitigate these biases.
|Participation & Teamwork (Individual Grade)||Effectively worked as a team member and shared equitable work load during this assignment.|
Communication was regular and effective & acted in accordance with team principles.
This scale is used for each line of the rubric above.
|Outstanding, Thoughtful and thorough||100% of pts|
|Strong, Provides some thought||80% of pts|
|Acceptable, Simple explanation||60% of pts|
|Insufficient, Little effort was made to give explanations||40% of pts|
|Unacceptable, No effort was made or the section was missing||0% of pts|