Guide topics · version 1.1.0-beta

Agile Buddy guide

Reports and workload

Home, project reports, and team workload use stored history. They do not invent metrics.

Home

Home is personal. My Work lists items assigned to you: not started, in progress (including review), blocked, due within 7 days or overdue, and done in the active sprint. Items without a due date are not treated as due soon. Due soon and days remaining use the server calendar day, not the browser clock. Work finished in an earlier sprint is not counted in the current one. A blocked item assigned to you also lists stored blocked-by keys. The other item's status is shown when you belong to that project. Action Required lists review items assigned to you, user stories whose work is all Done that you can accept, blocked or overdue work in the active sprint, and feedback that needs your response. A platform administrator sees newly submitted feedback. Other open feedback is not treated as waiting on you. Active sprints and historical burndown and velocity stay on the page. While the note at the top names the next step, the burndown section only says the chart stays blank. Once a sprint is active and the chart is still empty, that section names the sprint, dates, and days remaining. It does not estimate a percent complete. Charts use recorded events only. If you have no project membership, Home names the next step for your role and leaves the counts at zero. It does not show sample work. A member whose home is still empty is pointed at the project backlog. When you can accept stories and something is waiting, Pending reviews is the open group, with those stories listed ahead of review items assigned to you. Team workload appears only for projects where you are Product Owner or Scrum Master, as a link to that page.

Project reports

Reports on the project summarize item counts, roadmap status, releases, sprint capacity, and open retro actions. When export is enabled, members can download an Excel file. That download is audited. PDF reports are not available.

Team workload

Workload is visible to the Product Owner and Scrum Master. It compares open assigned estimate hours with each person’s available hours for the current week (working days times 8 hours). Done and archived items are excluded. Hours on a multi-assignee item are split evenly. The view includes open work across that person’s projects, and it hides platform administrators from the roster.

  • Within capacity, Near capacity, and Overloaded are the three bands.
  • The comparison is against the person’s week, not against a 100% allocation on this project alone.