Sonoma State University
Department of Computer Science
CS-370: Software Design and Development
Exercise 4: Team Formation

OBJECTIVE

In this exercise you will form a team of four students. Next, you and your team will discuss, negotiate, then answer the following questions below.

The exercise:

After forming a four-member team, please answer the following questions:

  • What is the name of your team?
  • What are the full names of each member of your team?
  • List the roles and responsibilities for each team member (e.g. Quality Assurance tester, Database admin, Front-end developer, Back-end developer, Programmer Lead, etc.)
  • Will your team use a code repository to manage the software you write? Which code repository? Example code repositories include: Github, Bitbucket, SourceForge, Subversion, etc. If your team will not be using a code repository, how will your team members manage and coordinate your software project updates (push and pull requests) for CS-370?
  • How often (frequency) will your team member meet (e.g. once per week, twice per week, etc.)? What will be the team meeting modality (e.g. via Zoom, Discord, Slack, etc.)?
  • How will your team resolve conflict?
  • What programming language(s) for all server-side application development will you likely use for this project? Possible languages are: Python, Java, Perl, PHP, C, or C++.

Uploading your solution:

Please upload your answers to the above questions. Everyone listed on a given team will receive the same credit for this exercise. At least one member of each team should upload the exercise answers.

Grading Rubric

CRITERIA RATINGS POINTS
Team name:
What is the name of your team?		 Proficient
1 point
Team name is listed.		 Below Expectations
0 points
No team name is listed.		 1 point
Team roles and responsibilities:
What are the team roles and responsibilities for each team member?		 Proficient
4 points
The roles and responsibilities for four team members are listed		 Satisfactory
2.8 points
At least three members have clearly defined roles and responsibilities. The fourth member's role is not clearly identified or their responsibilities are vague.		 Needs improvement
2.4 points
Two members have clearly defined roles and responsibilities. The other member's roles and/or responsibilities are vague.		 Below Expectations
0 points
No team member roles or responsibilities are listed.		 4 points
Code repository:
How will you team manage the software project?		 Proficient
1 point
A code repository is listed.		 Below Expectations
0 points
No software repository is listed.		 1 point
Team meeting frequency and modality:
How often will your team meet (frequency) and with what modality?		 Proficient
1 point
Team meeting frequency is listed as well as the modality (e.g. Zoom, Discord, Slack, etc.)		 Satisfactory
0.7 points
One of the following is missing: team meeting frequency OR team meeting modality.		 Below Expectations
0 points
Team meeting frequency and meeting modality are not listed.		 1 point
Conflict resolution:
How will your team resolve conflict?		 Proficient
2 points
Team lists one or more ways team conflict will be resolved. In the event of a stalemate or tie-vote (if applicable), the team also states the members will contact the Executive Champion (Professor Bruce) to resolve the conflict.		 Satisfactory
1.4 points
Team lists one or more ways team conflict will be resolved. The team fails to mention how conflict will be resolved in the event of a stalemate or tie-vote.		 Needs improvement
1.2 points
The team's plan for conflict resolution is vague or incomplete.		 Below Expectations
0 points
The team fails to mention how team conflict will be resolved.		 2 points
Programming Language:
What programming language(s) will your team use for this project?		 Proficient
1 point
One or more of the following programming languages are noted for server-side, common gateway interface application development: Python, Java, Perl, PHP, C, or C++.		 Below Expectations
0 points
No server-side, common gateway interface programming languages are listed; OR a programming language is listed that is not included in the allowed-programming languages specification.		 1 point
Total points: 10