CSE 341: Web Services

W03 Team Activity: Coordinate Features and Reviews

Overview

This week, your team will work in the same codebase. The goal of this activity is to complete or assign the shared team setup tasks, decide who is responsible for each data collection and frontend page feature, and decide who is available to review pull requests.

Decide how you will coordinate

You may meet live with your team. If your schedules do not allow that, complete the same coordination process by posting messages in your Microsoft Teams channel.

Professional teams often span multiple countries and coordinate in both of these ways as well.

Activity Instructions

Review the assignment features

Open the Week 03 assignment and review the single list of five feature sets. Each person will own one complete feature set, which may include Mongoose schemas, model functions, API controllers and routes, and client-side page updates.

The first three feature sets are required for every team. Feature Set 4 is assigned when the team has at least four people, and Feature Set 5 is assigned when the team has five people.

Plan the shared team setup tasks

Your team must make sure the shared Render and MongoDB setup tasks get completed. You may complete them during this team activity, or you may assign specific teammates to complete them later. Either way, everyone should know who is responsible and when the setup should be done.

  1. Set up the team's Render project and deploy the Kizuna Rail app from the team GitHub repository.
  2. Make sure the deployed app is connected to the team's repository.
  3. Make sure every teammate has permission to view the Render project and deployment logs.
  4. Set up a MongoDB Atlas cluster for the project.
  5. Make sure the deployed Render app and each teammate's local project can connect to the same database.
  6. Decide how the MongoDB connection string will be shared privately with teammates.
  7. Post the setup plan in your Microsoft Teams channel.

Share the database connection safely

When your team sets up the MongoDB Atlas cluster, make sure the cluster can be accessed from any IP address so each teammate and the deployed Render app can connect. In Atlas, this usually means adding 0.0.0.0/0 to the IP access list.

Everyone on the team will need the MongoDB connection string in their local .env file. Share that value through a private team channel, not in the repository. Do not commit the .env file or paste the connection string into code, issues, pull requests, or screenshots.

Assign features without duplicating work

  1. Assign one complete feature set to each team member; do not divide the Mongoose and frontend portions of a feature set between different people unless the team agrees to collaborate on the same assigned set.
  2. Make sure Feature Sets 1, 2, and 3 each have an owner before assigning the optional feature sets.
  3. If the team has four people, assign Feature Set 4. If the team has five people, assign Feature Set 5 as well.
  4. Identify any dependencies between feature sets and decide what work must be available first.
  5. Write each feature set, its owner, and any dependency in your Microsoft Teams channel so everyone can see the plan.

Plan next week's reviews

Your Week 03 pull requests will be reviewed at the beginning of Week 04. Decide how your team will make sure every PR is reviewed.

  1. Agree on how you will notify the team when a PR is ready. Use your Microsoft Teams channel for this assignment.
  2. Agree that each person will complete at least two reviews at the beginning of Week 04.
  3. Agree that the team will make sure every PR receives a review and that authors respond to review feedback before later integration work.

Completion Checklist

Submission

When you are finished, return to Canvas to complete the team activity report or quiz.

Other Links: