The team room is the area where your team collaborates, conducts all standups, planning and review meetings, and manages all work. The team room provides a consolidated view of your team's tasks, stories, defects, and key milestones. To open the team room:
If you’re using the new navigation:
- Select Teams in the top navigation bar and select the team you want to view information about; the team room displays.
Note: When on another team page, select Team room from the list of page options on the sidebar to get back to the team room.
If you’re using the old navigation:
- Select Team from the left Nav menu.
- Under the Team section, select Team Room; the team room page displays.
Here, select a team and a sprint from the corresponding dropdown menus.
You can switch between the following team room views:
- Dashboard view presents stories as a list and includes different sprint statistics.
- Sprint Board view presents features, dependencies, objectives, stories, tasks, and defects as a board of cards.
You can also use the following options on the toolbar:
Use the View Configuration option to tailor your team room view according to your needs by selecting the necessary cards:
- Progress. Sprint statistics, such as time left for the sprint, team velocity, percent of accepted story points, and a number of defects closed, tasks done, stories accepted, and dependencies done.
- Chat. An area for chat and discussions on any work item involved in the sprint.
- Dependencies. Dependencies for the team in this sprint.
- Impediments. Impediments blocking the team in this sprint.
- Objectives. Objectives the team set for this sprint at the planning meeting.
- Sprint Goals. The desired outcome of a sprint that is set at the planning meeting.
Short-term metrics show the following Daily Sprint Statistics charts. Point to any part of any chart to view details of that data point. You can also select any of the legend labels to show or hide the different lines on the charts.
- Story points burn down*
- Tested value points
- Trend for each story state
- Defect trend
- Planned versus earned velocity
- Risk and scope trends
*Note: The Story Points Burn Down chart X axis displays all days in the sprint, plus one. This allows the chart to capture all the work for the final day of the sprint. The ideal burn starts from the first day of the sprint and ends at the last day of the sprint. So if a sprint is from 1/1/2019 - 1/15/2019, then the ideal burn accounts for the whole day of 1/15/2019 up to time 23:59:59.
Long-term metrics show the PI burnup charts by feature and story. The burnup charts show a detailed view of what is accepted: LOE (orange line). The black line shows how overall scope changed during the PI. If the PI is not yet finished, you will see three projected lines on the end of the orange accepted line—these predict normal, optimistic, and pessimistic trends for acceptance for the remainder of the PI based on previous acceptance rate. Use these charts to understand if you have too much scope in the PI (the black line) to be able to finish on time. If the predictor lines do not approach the top of the black line, you may need to decrease scope for the PI.
Sprint progress report shows a detailed view, by story, of what tasks are needed for story completion along with a view of task hours remaining per team member. This grid provides a visual representation by day and team member of what is needed to complete the story in the given sprint identifying work remaining, increase or decrease in effort hours during the sprint. This report provides a visual representation of how the sprint is progressing by task hours remaining, provides a visual of team members workload and early identification of stories that are at risk of not being delivered based on work remaining.
Sprint health report displays the overall progress of the selected sprint at the quality level, providing a status of the stories via visual progress of story defects, test cases, and acceptance criteria per story. Each story is shown with color-coded "speedometer" progress bars for each of the three elements (story defects, test cases, and acceptance criteria) to the right of the story ID and name. On the far right are three icons representing each of the elements with a simple good or bad rating.
This report is a quick way to appraise the status of the sprint quality by story at any time. Problem areas quickly jump out as they are clearly marked in red or "bad." If used during the daily standup, the team can quickly see overall progress of each story, based on quality metrics. Bars will remain gray until xx% of the relevant items have been completed, at which point they will move to yellow. Only when 100% of relevant items are Complete will the bars turn green.
Capacity report details the team capacity throughout the sprint, and is especially helpful to Scrum Masters as they determine whether the overall goal of the sprint can be achieved with the available team members. The report should be used to determine if the team is set up for success going into a sprint. It tells the story of the sprint, such as: Can we deliver upon our commitments? Is the work distributed equally within the team? Are we progressing as planned or is work taking more/less time than estimated?
You can run a daily standup meeting—select the date of the standup, and then click Start Meeting. A Scrum Master, product owner, QA lead, or team coach can start a daily standup.
If the selected sprint has not started yet, you can start it directly from the Team Room. Click the Start Sprint button on the toolbar, and the sprint status changes to In Progress. Sprints can be started manually, or they can be started automatically if you have the Start and End Sprint Automatically team platform setting enabled. With the option enabled, if a sprint isn’t started manually, it will start automatically at 11:59 PM on its first day.