Teams - Make Teams Page

[anthonybernardi]

Overview

Create a space where FinishLine users can find information about individual teams, including team leads, members, current projects, and a brief summary of team activities.

Stakeholders

Product Stakeholder: Tom Weatherbee Engineering Stakeholder: Arnav Joshi Reference Users: JP and Nick DePatie

User Story

As a current/prospective member, I want a place where I can find all the teams at NER along with what each does and which projects each is working on.

Success Metrics

Success will be measured based on the increase over time of page views. As this feature doesn’t exist and the majority of users will likely be prospective members, we’ll set a baseline at 0.

Feature Adoption Metrics

Feature adoption throughout the year can be measured by user traffic relative to current club membership. During recruiting periods, we can measure feature adoption by comparing the number of prospective members attending meetings to the number of Teams page accesses.

Rollout Plan

• Deploy only the main teams page to production (ie. excluding individual team pages and ensuring there’s no link to them on the main page yet)
  • After some brief bug testing, can be rolled out to all members
• Deploy individual teams pages
• Work with team leads to fill out their team-specific summary section
  • Observe difficulties and feedback throughout this process

Out of Scope

Discussed QOL improvements, specifically regarding expanding/contracting box indicators, which will likely be relegated to a separate epic or set of tickets in the future

Background / Context

Currently, most of any given team’s relevant information is scattered throughout Slack, Google Drive, and Gantt charts, making it difficult for prospective members to learn about different teams, and for current members to locate what projects their team is working on. With this project, we’re trying to consolidate most of the basic information about a specific team into one place, focusing on membership, projects, and a brief summary of the team’s activities.

Acceptance Criteria & Mock-ups

Main Teams Page

• Lead, Members, and Projects should all be auto-generated
• Individual projects link to their corresponding FinishLine project pages
• Clicking the team name should bring the user to the Team-specific page for that team
• Clicking on a contracted box outside of the team name should expand the box
• All team boxes on this main page should start contracted

Team-specific Page

• As before, everything aside from the markdown box should be auto-generated
• Clicking on any of the red project names should take you to the corresponding project page on FinishLine
• Markdown box, serving as a summary section
  • Should be editable by the team lead corresponding to this specific page
  • Basic text formatting capabilities (bold, italic, underline, strikethrough, bullets, numbering)
  • Max of 300 words to discourage leads from using this in place of Confluence

[anthonybernardi]

After some discussion we've decided to go with this design and not include the markdown description on the overall teams page because it will be too cluttered. We are going to just include the description on the individual team page when that gets added.