Skip to content

Project Risk Digest

Example prompt: "Every Friday at 3pm, scan our Jira board for blocked tickets, tasks that haven't moved in 5 days, and any stories added mid-sprint. Summarise the risks in a Slack message to #project-leads."

How to automate project risk reporting with GloriaMundo

The Problem

Project risks rarely announce themselves. They accumulate quietly — a task sits in "In Progress" for a week with no updates, a blocker label gets added but nobody follows up, three new stories appear mid-sprint and nobody recalculates whether the team can absorb them. By the time these signals surface in a status meeting, the damage is done: deadlines slip, scope creeps unnoticed, and the team is firefighting instead of delivering. Compiling a risk picture manually means trawling through every task on the board, cross-referencing dates and statuses, and making judgement calls about what matters — work that takes 30-45 minutes and is easy to skip when things feel busy.

How GloriaMundo Solves It

We build a weekly workflow that queries your project board for early warning signs. An integration step pulls all tasks from Jira, including their status, assignee, last update timestamp, and any blocker flags. A code step identifies risks: tasks that have not been updated in 5 or more days, items flagged as blocked, and stories added after the sprint started. An LLM step takes the flagged items and writes a concise risk digest — grouping issues by severity, naming the responsible people, and suggesting next steps. The digest is posted to Slack so the project lead can act on it before the week ends. Glass Box preview lets you review the full digest and verify the risk logic before anything is sent.

Example Workflow Steps

  1. Trigger (scheduled): Runs every Friday at 3:00 PM.
  2. Step 1 (integration): Query Jira for all tasks in the active sprint — status, assignee, last updated date, labels, and story points.
  3. Step 2 (code): Identify risks — tasks not updated in 5+ days, items with blocker labels, stories added after the sprint start date, and tasks with no assignee.
  4. Step 3 (conditional): If no risks are found, send an all-clear message and end. Otherwise, proceed to the summary.
  5. Step 4 (llm): Generate a structured risk digest grouping items by severity (blocked, stalled, scope creep), with assignee names and suggested actions.
  6. Step 5 (integration): Post the risk digest to the #project-leads Slack channel.

Integrations Used

  • Jira — source of task data including statuses, update timestamps, labels, and sprint membership
  • Slack — delivers the formatted risk digest to the project leads channel

Who This Is For

Project managers and delivery leads overseeing sprints of 15-40 tasks who want a weekly early-warning system rather than relying on gut feeling or end-of-sprint surprises. Particularly valuable for teams where the PM is managing multiple projects and cannot monitor every board daily.

Time & Cost Saved

Manually reviewing a project board for risks and writing up a summary takes 30-45 minutes per week. Over a year, that is 25-40 hours of analysis work. More importantly, catching a blocked task on Friday rather than the following Wednesday can save days of downstream delay. This workflow surfaces risks consistently every week, even when the team is too busy to do it manually.