Weekly Status Report
Template
Summary
• Key update 1
• Key update 2
• Key update 3
• Key risk 1
• Key issue 2
• Key dependency 3
Key Updates Key Risks, Issues, and Dependencies
STORY STATUS
Jira ID Title Overal
Status
Codin Dev
testing
Demo Issues/Dependencies Remarks
On track Done <target
date>
24-Jan-
2023
Issues
Delayed
RAID
Issue
#
Issue
type
Issue description Status Owner Severi
y
ETA Issue history Remarks
Linked
to Jira#
Risk/Assump
tion/Issue/D
ependency
Risk/Assumption/Issue/Depend
ency
On track Name of
the
owner
High/Me
dium/Lo
w
18-Jan-
2023
18-Jan-
2023
14-Jan: person confirmed it’ll get
resolved by <date>
18-Jan: escalated to xyz
20-Jan: CUSTOMER acknowledged that
the story will get delayed due this.
Issues
Delayed
Action Items
S# Description Status Owner Priority ETA Action item history Remarks
Linked to
Jira#
Get xyz done to resolve abc issue On track Name of
the owner
High/Medi
um/Low
18-Jan-2023
18-Jan-2023
14-Jan: person confirmed it’ll get resolved
by <date>
18-Jan: escalated to xyz
20-Jan: Customer acknowledged that the
story will get delayed due this.
Get def done to mitigate xyz risk Potential
delay
Delayed
Appendix
Decision Log
S# Type Decision Description Approve
By
Decision History Remarks
Decision
#
Technical/Del
ivery/
Risk/Assumption/Issue/Dependency 14-Jan: person confirmed it’ll get resolved
by <date>
18-Jan: escalated to xyz
20-Jan: Customer acknowledged that the
story will get delayed due this.
Thank You

Weekly Status Report Template for Software Development Projects

  • 1.
  • 2.
    Summary • Key update1 • Key update 2 • Key update 3 • Key risk 1 • Key issue 2 • Key dependency 3 Key Updates Key Risks, Issues, and Dependencies
  • 3.
    STORY STATUS Jira IDTitle Overal Status Codin Dev testing Demo Issues/Dependencies Remarks On track Done <target date> 24-Jan- 2023 Issues Delayed
  • 4.
    RAID Issue # Issue type Issue description StatusOwner Severi y ETA Issue history Remarks Linked to Jira# Risk/Assump tion/Issue/D ependency Risk/Assumption/Issue/Depend ency On track Name of the owner High/Me dium/Lo w 18-Jan- 2023 18-Jan- 2023 14-Jan: person confirmed it’ll get resolved by <date> 18-Jan: escalated to xyz 20-Jan: CUSTOMER acknowledged that the story will get delayed due this. Issues Delayed
  • 5.
    Action Items S# DescriptionStatus Owner Priority ETA Action item history Remarks Linked to Jira# Get xyz done to resolve abc issue On track Name of the owner High/Medi um/Low 18-Jan-2023 18-Jan-2023 14-Jan: person confirmed it’ll get resolved by <date> 18-Jan: escalated to xyz 20-Jan: Customer acknowledged that the story will get delayed due this. Get def done to mitigate xyz risk Potential delay Delayed
  • 6.
  • 7.
    Decision Log S# TypeDecision Description Approve By Decision History Remarks Decision # Technical/Del ivery/ Risk/Assumption/Issue/Dependency 14-Jan: person confirmed it’ll get resolved by <date> 18-Jan: escalated to xyz 20-Jan: Customer acknowledged that the story will get delayed due this.
  • 8.