WDD 430: Web Full-Stack Development

W05 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. This week centers on integrating authentication and metadata while moving unfinished sprint work toward a releasable state.

Overview

This week your team should continue implementation and focus on integration quality. Most teams will still have unfinished sprint items, so your goal is to complete high-priority stories, document remaining work, and prepare clean Pull Requests (PRs) for a second structured review next week.

Before the Meeting

Individually complete the following before the meeting:

  1. Complete the learning activities.
  2. Review your assigned GitHub issue(s) and confirm acceptance criteria are clear.
  3. Push your latest work-in-progress commits to your feature branch so your team can review current progress during the meeting.
  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 with objectives for auth, metadata, and unfinished sprint work.

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 demos current feature progress from their branch.
    • Identify which user story or issue each update addresses.
    • Call out what is complete, in progress, and blocked.
    • Highlight any risks that could delay integration or review.
  3. Authentication Planning Tasks: Establish the implementation plan for Authentication.
    • Discuss and finalize the selected auth strategy and provider at a high level.
    • Define baseline login/logout behavior and session expectations.
  4. Metadata and Discoverability Tasks: Ensure pages are prepared for production quality.
    • Add or refine page metadata (title, description, Open Graph where applicable).
    • Check for consistent metadata patterns across layouts and routes.
    • Assign and document any pages still missing metadata in the sprint backlog.
  5. Unfinished Sprint Triage: Convert incomplete work into clear next steps.
    • Move partial tasks into well-scoped GitHub issues with acceptance criteria.
    • Prioritize blockers that prevent integration or deployment.
    • Assign owners and target completion dates for Week 06.
  6. Prepare PRs for next week's code review: Every member should have an open, reviewable PR.

    Remember that the next week includes a structured team code review. If your Pull Request is missing, empty, or outdated, teammates will not be able to complete that review activity.

    • Push your latest changes: 
      git add .
      git commit -m "Feature work: [brief description]"
      git push origin your-feature-branch
    • Open or update your Pull Request from your feature branch into main.
    • In the Pull Request description, include completed criteria, known gaps, and linked issue numbers.
    • Leave the Pull Request open for review unless your team has explicitly finished and approved it.
  7. Update GitHub Project Board: Keep sprint status accurate.
    • Move completed issues to Done.
    • Create new issues for carryover work.
    • Confirm assignments for this week and plan on final submission by the end of next week.
  8. 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 team members 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 and carryover items.
  3. A brief summary that includes at least one challenge, one success, and one insight from this week's sprint meeting.

Individual Feature Pull Request

This is a Pull Request that will be reviewed by a teammate in a code review next week.

  1. The URL of your open Pull Request from your feature branch into main, containing meaningful code changes.
  2. A one-sentence summary of what your Pull Request implements, including whether it covers authentication, metadata, or unfinished sprint work.

W05 Team: Code Review Report

This content comes from your Week 05 Team: Code Review assignment as a reviewer.

  1. Submit the URL of the GitHub Pull Request where you submitted your code review comments on a teammate's team-project Pull Request.