forecast-report

Generate delivery forecast reports from backlog size and team velocity.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/devmuslim/pdm-skills --skill forecast-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forecast-report
Source: https://github.com/devmuslim/pdm-skills/tree/main/pdm-metrics-reporting/skills/forecast-report
Command: npx skills add https://github.com/devmuslim/pdm-skills --skill forecast-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a data-driven forecast for release completion dates, offering stakeholders a realistic view of project timelines.

Core Features & Use Cases

  • Delivery Forecasting: Calculates projected completion dates based on historical team velocity and remaining backlog.
  • Scenario Planning: Presents optimistic, realistic, and conservative forecast scenarios.
  • Use Case: When asked about the release timeline, use this Skill to generate a forecast and compare it against the committed date, identifying any gaps.

Quick Start

Generate a delivery forecast report using the provided backlog and team velocity data.

Frequently Asked Questions about forecast-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I forecast release dates using sprint velocity and backlog size?

Forecast release dates by calculating remaining sprints based on your current backlog size and historical team velocity. This generates a data-driven delivery report with optimistic, realistic, and conservative scenarios with corresponding forecast dates.

What is the best way to compare my committed release date against a forecast?

Compare your committed release date against a forecast by generating a delivery report that calculates projected completion dates. It automatically identifies any timeline gaps and suggests acceleration options if a delay exists.

How does scenario planning work for agile delivery forecasting?

Agile delivery forecasting scenario planning works by applying your historical team velocity to the remaining backlog. It produces optimistic, realistic, and conservative scenarios, each with a corresponding forecast date and a confidence statement.

Can I use this to calculate remaining sprints for my current backlog?

Yes, you can calculate remaining sprints by dividing your current backlog size by your historical team velocity. This calculation forms the baseline for generating the delivery forecast report and its timeline scenarios.

What data do I need to generate a delivery forecast report?

To generate a delivery forecast report, you need your current backlog size and historical team velocity data. This information allows the system to calculate remaining sprints, project completion dates, and suggest acceleration options.

Why does my release forecast show a gap against the committed date?

Your release forecast shows a gap when the projected completion date based on historical velocity and backlog extends beyond your committed date. The report identifies this gap and suggests acceleration options to help close it.