Bỏ qua, tới nội dung chính
Đỗ Hoàng Anh
VI
Tiếng ViệtEnglish中文

Mẫu tài liệu

Báo cáo tuần gửi khách hàng

Báo cáo được viết từ dữ liệu Jira và bổ sung nhận xét của BA. Phần đầu luôn là tóm tắt và các quyết định cần khách chốt, để người đọc bận rộn chỉ cần đọc một đoạn.

Case study liên quan: Dashboard KPI của team từ Jira API

Weekly status report

Tài liệu tiếng Anh

Project
PRJ (confidential)
Period
Mon 09 – Fri 13
Prepared by
Business Analyst
Audience
Client PM, Client CTO
Sprint 14 · On track

1. Summary

Sprint completion81%21 of 26 points
Blockers21 resolved, 1 needs the client
Open High bugs0last week: 1
Oldest open bug6 dayslast week: 15
Sprint 14Committed points
  • Done
  • Carried over to Sprint 15

  • 26 points committed81% done

The 5 carried-over points are US-04 CRM sync, which depends on the client's CRM sandbox (B-2).
  • Decision needed from the client: confirm the CRM field mapping (section 5) by Tuesday to keep US-04 in Sprint 15.

2. KPIs

KPIsLast week → this week
  • Last week
  • This week

  • Sprint completion✓ 68% → 81%

    68%
    81%

  • Throughput (tickets to Done)✓ 11 → 14

    11
    14

  • Cycle time (median)✓ 3.5 days → 2.5 days

    3.5 days
    2.5 days

  • Oldest open bug✓ 15 days → 6 days

    15 days
    6 days

  • Blocked tickets✓ 2 → 1

    2
    1

  • Client feedback backlog✓ 5 → 2

    5
    2
Open bugsBy severity
  • High
  • Medium
  • Low

  • Last week11

  • This week8

3. Delivered this week

Ticket Title Status Note
US-01 Renewal reminders UAT signed Timezone bug fixed and re-verified
US-02 Grace period and read-only mode UAT signed
US-03 Admin manual extension with audit log In UAT Client UAT scheduled for Monday
BUG-231 Duplicate webhook extends subscription twice Done Idempotency check added; regression passed

4. Blockers and risks

Blockers and risksWho owns what, and what we need
ImpactOwnerStatus or ask
B-1 · Payment sandbox rate-limitedWebhook tests blocked 1 dayDev AResolved on Thursday
B-2 · CRM sandbox access missingUS-04 cannot startClientPlease share access by Tuesday
R-1 · Legacy accounts enter grace on release dayMediumBABanner and support macro ready
R-1: we recommend releasing on Tuesday, not Friday, so support has a full week to absorb any extra volume.

5. Decisions needed from the client

DecisionsBoth needed by Tuesday
  • CRM field mapping for the "about to churn" list: confirm or edit the five proposed fields (attached).Tue
  • Release window: Tuesday 08:00 PT for the expiry feature (see R-1).Tue

6. Plan for next week

Next week
  1. B-2 resolvedclient shares CRM access
  2. US-04 CRM synccarried over
  3. Billing regressionbefore release
Also new: US-05 daily churn-risk email, from the meeting on the 12th; three clarification questions sent.

7. Client feedback log

Date Feedback Ticket Status
10th Banner text is too alarming during the grace period FB-22 Done Copy softened, screenshot attached
12th Sales also wants the churn list by email FB-23 Analysed Turned into US-05

Verified by the Business Analyst. Source: Jira API extract, Friday 17:00 ICT.

Tài liệu mẫu, dữ liệu mô phỏng. Cấu trúc và cách trình bày là cách tôi làm thật.