CSE 341 | Team Activity

W05 Team Activity: Coordinate Search and Pagination Work

Overview

Purpose: Coordinate your work with your team.
Task: Follow the instructions below to complete this week's team activity.

This week, your team will add pagination, searching, filtering, and sorting behavior to the Kizuna Rail API. Use this meeting to agree on route ownership, query parameter names, and response shapes before everyone starts coding.

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.

Instructions

Follow up on code reviews and outstanding pull requests

Open the team's GitHub repository.
Review the list of open pull requests from the previous week.
Identify any pull requests that are still waiting for review.
Make a plan for who will review each outstanding pull request.
Post in Microsoft Teams so the team knows who is reviewing each pull request.
Identify any pull requests that have been approved but not merged yet.
Make sure approved pull requests are merged or that the team has a clear plan for getting them merged.

Coordinate this week's query work

Review the list of feature sets for this week's assignment.
Have each teammate select a feature set to be responsible for.
Agree on consistent query parameter names such as page, limit, q, sort, and order.
Agree on the metadata shape for paginated responses.
Post each teammate's assigned feature set to Microsoft Teams so everyone is clear on the plan.

Consistency matters

API clients should not need to learn a different pagination or search pattern for every endpoint. Coordinate these decisions as a team.

Submission

When you are finished, return to Canvas to submit a quiz to report on your team coordination.