WDD 430: Web Full-Stack Development

W04 Team: Project

The team project prepares you for employment by helping you become a skilled collaborator and by giving you a portfolio piece you can continue to expand. It helps you develop software development skills, become an effective group member, and serve and teach one another, which is a core principle at BYU-Idaho.

Overview

This week is about active development and accountability. Each team member should arrive with meaningful progress on their assigned tasks. During the meeting you will share your work, unblock each other, and — most importantly — open a Pull Request for your feature branch. Those PRs are what your teammates will review in coming weeks, so having them open by the end of this week is required.

Before the Meeting

Individually complete the following before the meeting:

  1. Complete the learning activities.
  2. Review the project description as needed.
  3. Make meaningful progress on your assigned task from the project board so you have something concrete to share at the meeting. Push your work-in-progress to a feature branch before the meeting begins.
  4. If you are this week's Group Leader:
    • Send a meeting reminder to all team members at least one day before the meeting.
    • Prepare a meeting agenda based on the objectives below and the action items captured last week.

During the Meeting

  1. Invite the Spirit: Open the group meeting with prayer and invite the Spirit into your discussion.
  2. Individual Progress Updates: Each team member briefly demos or describes what they have built this week.
    • Share your screen and walk through your work-in-progress on your feature branch.
    • Report the GitHub issue(s) you are addressing and the current status.
    • Note anything you were unable to complete and why.
  3. Unblock: As a team, identify and resolve blockers before everyone breaks off to work individually.
    • Are any features blocked by shared TypeScript types, database schema, or API contracts that haven't been agreed on yet?
    • Are there merge conflicts or integration issues between branches that need to be addressed together?
    • Does anyone need a code walkthrough or pair-programming session to move forward?
  4. Copilot Instructions File: Review and finalize the team's .github/copilot-instructions.md file.
    • Verify it accurately reflects your current stack, component structure, data model, and naming conventions.
    • Test it: ask GitHub Copilot a question about your project and evaluate whether the response reflects your team's decisions.
    • Commit the final version to main so all team members benefit from it going forward.
  5. Open Individual Feature PRs: Each team member must open a Pull Request for their feature branch before the end of the week.

    These PRs are required. Your teammates will use them to conduct code reviews in Weeks 05 and 06. A Pull Request that is missing or empty means your reviewer has nothing to evaluate.

    • Push your latest commits to your feature branch: 
      git add .
git commit -m "Week 04 feature work: [brief description]"
git push origin your-feature-branch
    • On GitHub, open a Pull Request from your feature branch into main.
    • Give the Pull Request a clear title describing the feature (For example, "Add product listing page with filtering").
    • In the Pull Request description, note: what the feature does, any known issues or incomplete pieces, and the GitHub issue number it closes.
    • Leave the Pull Request open — do not merge it. Your peer reviewer needs to read the diff.
    • Copy the Pull Request URL and add it to your row in the team's team-membership.docx file in Microsoft Teams.
  6. Update GitHub Project Board: Reflect the current state of the project.
    • Move completed issues to Done.
    • Add any new issues surfaced during today's discussion.
    • Confirm that Week 05 issues are assigned and clearly scoped.
  7. Group Leader: Select a new group leader for the next meeting.

Submission Instructions

Each team member submits the following sections as a text entry in Canvas:

Team Meeting

  1. The names of the team members who were present at the synchronous meeting and the name of the team leader.

Project Progress

  1. A valid URL to the team's public GitHub repository.
  2. A valid URL to the team's GitHub Project Board, showing updated issue statuses.

Individual Feature Pull Request

This is the Pull Request your teammate will be assigned to review.

  1. The URL of your open Pull Request on GitHub. The Pull Request must be from your feature branch into main and must contain meaningful code changes — not an empty or placeholder diff.
  2. A one-sentence description of what your Pull Request implements.

W04 Team: Code Review Report

This content comes from your Week 04 Team: Code Review assignment.

  1. The URL of the GitHub Pull Request where you submitted your code review comments on a teammate's Sacrament Meeting Planner repository.