The True Cost of Value.
Governed. Forecasted. Delivered.
Everything you need to model team costs, forecast PI spend, track feature ROI, and govern your lean agile portfolio — from Command Centre to RAID log.
ForecastInSite v5 is a fully browser-based lean agile financial modelling platform. There is nothing to install — open the tool, choose your starting point, select your role, and you're modelling within minutes. Your data lives in your browser's local storage and can be exported as JSON at any time.
What you get out of the box
- Three role-optimised views: Financial Controller, Portfolio Manager, and Project/Delivery Manager — each with a tailored tab set
- Pre-loaded demo data spanning 6 teams, 4 PIs, and realistic budget scenarios — activate with a single click
- Full JSON import/export so your data travels with you and can be shared with colleagues
- Persistent local storage — your last session is always waiting when you return
- Dark and light theme that adapts to your system preference
Getting Started walkthrough
Video coming soon
⏱ ~90 seconds · Startup screen, role selection, demo data
How to set up ForecastInSite for your portfolio
Open the tool and choose your start
On first load you'll see the startup screen. Choose Load Demo to explore with realistic data, Start Fresh to enter your own, or Import to load a previously exported JSON file.
Select your role
Choose Financial Controller (full cost and budget access), Portfolio Manager (feature and value focus), or Project/Delivery Manager (team and delivery focus). You can switch roles at any time from the header.
Configure your Financial Year
Navigate to Configuration → set your FY start month. This drives all quarter and PI calculations across the tool. Australia defaults to July.
Set up your PI schedule
Define how many sprints per PI and your sprint length. ForecastInSite will generate your complete PI and quarter calendar automatically.
Add your teams and members
In Teams & Capacity, create each delivery team, add members with their cost rates, and define FTE percentages. The tool calculates monthly and PI-level costs immediately.
💡 Start with demo data
Even if you have real data, run through the demo first to understand how each tab interconnects before entering your own numbers.
💡 Export early, export often
Use the Export button after every major configuration change. JSON exports are your backup — local storage can be cleared by the browser.
💡 Role switching is instant
The Financial Controller and Portfolio Manager see different tabs. Toggle between roles to understand what each stakeholder experiences.
💡 One PI at a time
Use the PI navigator (◀ ▶) to move between programme increments. Build one PI accurately before copying patterns to future PIs.
Full Setup Guide Included
Unlock the complete step-by-step playbook including data preparation checklist, PI configuration guide, and team onboarding workflow.
Unlock Full PlaybookForecastInSite v5 is role-aware. Each role sees a curated tab set built around what actually matters for their job. Switching roles is instant — no data is lost, just the lens changes.
Financial Controller
Full cost visibility across all teams and PIs. Command Centre, Budget & Actuals, Licences & Overhead, and Reporting. Owns the financial narrative.
Portfolio Manager
Feature economics, value stream, and scenario planning. Sees Feature Economics, Value Stream, Relative Sizing, and Capacity Planner. Owns the delivery-value balance.
Project / Delivery Manager
Team health, capacity, productivity, and RAID governance. Sees Teams & Capacity, Productivity, RAID Log, and Milestones. Owns delivery execution.
Choosing the right role for your context
Financial Controller — when budget accountability is primary
Use this role for PI budget reviews, finance team presentations, cost variance analysis, and licence audit reporting. The Command Centre dashboard is designed to answer "are we over budget and why?" in under 30 seconds.
Portfolio Manager — when value delivery is primary
Use this role for PI planning workshops, feature prioritisation sessions, and stakeholder value reviews. Feature Economics shows you cost-per-point and revenue per feature — the conversation shifts from "how much" to "is it worth it".
Project / Delivery Manager — when execution is primary
Use this role for daily standups, sprint reviews, and team capacity checks. The RAID log and milestones are front and centre so blockers never get buried in a spreadsheet.
Role Configuration Guide
Learn how to configure each role for your organisation's governance model and which tabs to present in which stakeholder meetings.
Unlock Full PlaybookMost delivery organisations track headcount in HR, software licences in IT, and project spend in a spreadsheet — but nobody has a single, honest view of the true cost of delivery per team, per PI, or per feature. ForecastInSite is a browser-based financial modelling platform that brings those numbers together and makes the conversation concrete.
The problem it solves
Hidden delivery cost
Headcount is visible. Licences, overhead, and AI tooling are scattered. ForecastInSite builds one fully-loaded cost model — salaries + licences + overhead — per team and per PI.
No feature-level ROI
Executives invest in features, not sprints. ForecastInSite maps every feature to a cost, a business value score, and a revenue figure — answering "what did we get for the $1.6M we spent this PI?"
AI spend without governance
AI tooling is now a line item on every technology budget. ForecastInSite models AI agents as first-class team members, making their cost and productivity multiplier visible and defensible.
Who uses it and what they see
Financial Controller
Budget vs actuals by team, variance RAG status, forecast to PI-end, licence renewal calendar, and the fully-loaded cost of delivery. Built for the finance governance conversation.
Portfolio Manager
Feature ROI, investment mix by value stream, cost-per-point trends across PIs, and which features are generating revenue versus consuming capital with nothing to show.
Project / Delivery Manager
Team capacity utilisation, velocity trends, AI agent productivity contribution, RAID log, and milestone tracking — connecting financial performance to delivery health.
Key outputs
True cost per PI — headcount + licences + overhead, per team
Cost per story point — your unit economics, tracked across PIs
Feature ROI — cost invested vs business value and revenue realised
Budget variance — RAG-rated actuals against approved PI budget
AI workforce ROI — licence + compute cost vs human-equivalent productivity
Governance artefacts — RAID log, milestone tracker, capacity planner
ForecastInSite is ready to use in minutes — but the quality of what it produces depends on the quality of the data you put in. This guide covers what to gather before you open the tool, and the correct sequence for building your model so that each module has what it needs.
Before you open the tool — gather this first
- Your team list — team names, Agile Release Train (ART) structure if applicable
- Headcount per team — names, roles, employment type (FTE or Contractor)
- Cost rates — daily or monthly rate per person (use blended rates if individual rates are sensitive)
- Your approved PI budget per team (or the previous PI actuals if a new PI hasn't been approved yet)
- Your software licence list — vendor, cost model (per-seat or flat), renewal dates
- A Jira export at Feature level — Themes, Initiatives, Epics, and Features only (not Stories or Tasks)
Setup sequence — follow this order
Teams & Capacity
Create your delivery teams and add members with cost rates. This is the foundation — every other module depends on teams existing. Include AI agents here too if you want them costed.
⚠ Must be completed before Budget & Actuals, Feature Economics, and AI WorkforceBudget & Actuals
Set the approved budget per team for the current PI. The tool will compare this against actuals as the PI progresses and surface RAG-rated variance automatically.
⚠ Requires teams to be set up firstLicences & Overhead
Add all non-headcount costs — software licences, platform subscriptions, overhead allocations. This can be done independently of teams, but is most useful once team structure is defined so costs can be allocated correctly.
Feature Economics
Import your Jira export (Feature level and above) or enter features manually. Assign each feature to a team — cost-per-feature and ROI calculations are immediate once teams have cost rates.
⚠ Requires teams to be set up first. Richer with Budget & Actuals already entered.AI Workforce
If you have AI agents added to your teams (Step 1), review the AI Workforce module to see their cost vs productivity contribution, and identify any AI tool duplication across teams.
⚠ Requires AI agents to be added in Teams & Capacity firstCommand Centre
Once steps 1–4 are complete, the Command Centre dashboard is fully populated. This is the view to use in steering committee meetings — total budget, total spend, variance, and forecast accuracy at a glance.
You're ready to present when…
- Command Centre shows non-zero Total Budget and Total Spend
- At least one team has a RAG status (green, amber, or red variance)
- Feature Economics shows at least one feature with a cost attached
- You can answer: "What is our cost per story point this PI?"
ForecastInSite works at the portfolio and program planning level — not the team execution level. This means it cares about Themes, Initiatives, Epics, and Features, and ignores everything below. Understanding this before your first import will save significant time and confusion.
The Jira hierarchy — where ForecastInSite draws the line
A typical PI backlog in ForecastInSite: 30–80 Features across 4–8 teams. If your Jira export has thousands of rows, you are exporting at the wrong level — filter to Epic and Feature issue types before exporting.
What happens if you import the wrong level
ForecastInSite automatically skips Stories, Tasks, and Bugs. When you drop in a Jira CSV, the import preview will tell you exactly how many items were imported and how many were silently ignored — so you always know what landed. You do not need to clean your export before importing.
Recommended Jira export columns
The Issue Type and Summary columns are required. All others enrich the import but are optional. ForecastInSite will map Story Points, Status, and Business Value automatically if present.
Import modes
📄 Jira CSV
Drop in a Jira export CSV. ForecastInSite reads Issue Type, Summary, Story Points, Status, and Business Value. Stories, Tasks, and Bugs are automatically skipped and counted in the import summary.
🔗 JSON Backup
A full ForecastInSite session export — restores your complete model including teams, budgets, licences, and features. Use this to share your model with a colleague or move between browsers.
🌐 PortfolioInSite
If you use PortfolioInSite Web in the same browser, ForecastInSite can read your backlog directly — no file export needed. Epics, Features, and SAFe Epics are imported with story points and business value preserved.
Command Centre is the executive dashboard of ForecastInSite — the first thing you see when you open the tool. In a single view it answers the four questions every leadership team asks at the start of a PI review: How much have we budgeted? How much have we spent? What's the variance? And how accurate is our forecast?
Key capabilities
- Four live KPI cards: Total Budget, Total Spend, Variance ($ and %), and Forecast Accuracy — updated as you change any figure in the tool
- Budget Burn by Team — grouped bar chart showing Budgeted, Actual, and Forecast for every team in the current PI
- Top 5 Over-Budget Teams table with RAG (Red/Amber/Green) status indicators and variance amounts
- Cost Per Point Trend — which teams are getting more or less expensive to deliver a story point over time
Command Centre walkthrough
Video coming soon
⏱ ~60 seconds · KPI cards, budget burn chart, over-budget analysis
How to use Command Centre effectively
Check the variance indicator first
Red variance means you're over budget for the current PI. Click through to Budget & Actuals to see which cost category is driving the blowout before escalating.
Read the Budget Burn chart by column group
Each team shows three bars: Budgeted (blue), Actual (red), Forecast (amber). If Forecast exceeds Budgeted and you're mid-PI, you have a problem you can still address. If Actual exceeds Budgeted and the PI is complete, that's a retrospective finding.
Use the Top 5 table for prioritisation
Not all over-budget teams need the same response. A team 1% over on a $50k budget is noise. A team 15% over on a $300k budget is a governance event. Use the variance $ figure, not just the RAG dot.
Cost Per Point Trend reveals hidden waste
Rising cost per point means the team is spending more to deliver the same story points. Could be overtime, contractor uplift, or velocity decay. This is the leading indicator to watch.
💡 Present this tab first
In any PI review, start on Command Centre. It anchors the conversation on facts before anyone opens a spreadsheet.
💡 Forecast ≠ Actual
Forecast is your modelled end-state. Actual is what's been spent. Keep both current for the accuracy metric to mean anything.
💡 RAG thresholds
Red = over 10% variance. Amber = 5–10%. Green = within 5%. These can be tuned in Configuration to match your governance policy.
💡 PI navigator
Use the ◀ ▶ controls in the header to compare this PI to previous ones. Cost per point trend is most meaningful across 3+ PIs.
Full Command Centre Playbook
Includes PI review presentation template, RAG threshold configuration guide, and how to use Command Centre data in executive reporting.
Unlock Full PlaybookBudget & Actuals is the financial ledger of your PI. Set your approved budget per team, enter actuals as the PI progresses, and ForecastInSite handles variance calculation, RAG status, and trend analysis automatically. This is where the financial conversation gets granular.
Key capabilities
- Set team-level budgets per PI and track actuals in real-time
- Automatic variance calculation with RAG (Red/Amber/Green) status per team
- Period-over-period comparison across multiple PIs
- Forecast-to-completion modelling based on current burn rate
Budget & Actuals walkthrough
Video coming soon
Running your PI budget cycle
Set approved budgets at PI start
Enter the approved budget for each team at the beginning of each PI. Lock these figures once the PI starts — variance is only meaningful against a fixed baseline.
Update actuals fortnightly
Align actuals updates with your payroll cycle or sprint cadence. Fortnightly is the minimum frequency for actuals to be useful as a governance signal.
Review RAG status before steering committee
Red teams need a narrative before the meeting — not during it. Use the variance $ and % to prepare a one-sentence explanation for each red team.
💡 Budget ≠ team cost
Your team cost (from Teams & Capacity) is the modelled run rate. Your budget is the approved envelope. These should align at PI planning — if they don't, you already have a problem.
💡 Variance tolerance
Set your RAG thresholds to match your finance policy. Most organisations use ±5% for amber and ±10% for red, but scaling organisations often use ±3% for red.
Full Budget & Actuals Playbook
Includes PI budget template, actuals entry workflow, variance narrative guide, and finance governance calendar.
Unlock Full PlaybookLicences & Overhead captures the non-headcount cost of delivery — software licences, platform costs, tooling subscriptions, and overhead allocations. In most agile organisations, this category is 15–25% of total delivery cost and is almost never modelled accurately.
Key capabilities
- Track all software and platform licences with seat counts, unit costs, and renewal dates
- Allocate overhead costs (office, hardware, tooling) across teams by headcount or percentage
- See total true cost of delivery (headcount + licences + overhead) per team and PI
- Licence renewal calendar to prevent unbudgeted surprises
Licences & Overhead walkthrough
Video coming soon
Building your true cost model
Gather all non-headcount costs
Pull your last invoice from every software vendor. Include Jira, Confluence, GitHub, CI/CD tools, monitoring, security tooling, and cloud infrastructure. You'll likely find 20–30% more spend than your budget spreadsheet shows.
Allocate to teams
Most licences are enterprise or per-seat. Per-seat licences allocate to the team that uses them. Enterprise licences can be split by headcount proportion or usage percentage.
💡 True cost = headcount + licences + overhead
Most "agile cost" conversations only count salaries. Add licences and overhead and the number typically increases by 30–40%. Know your real number.
💡 Renewal calendar
Enter every licence renewal date. ForecastInSite flags upcoming renewals so you can budget for them in the next PI — not scramble for emergency approval.
Full Licences & Overhead Playbook
Software licence audit checklist, overhead allocation methodologies, and the true cost model explained with worked examples.
Unlock Full PlaybookFeature Economics answers the question every executive eventually asks: "We're spending $1.6M this PI — what value are we actually getting for it?" It maps every feature to a cost, a business value score, and (optionally) a revenue figure. The result is a cost-per-point and ROI view that makes prioritisation a financial conversation, not just a planning one.
Key capabilities
- Track features with business value score, story point estimate, and delivery cost
- Mark features as revenue-generating and track actual revenue realised
- Automatic cost-per-point calculation per feature and per team
- Incomplete feature tracking — cost sunk on features not yet delivered
Feature Economics walkthrough
Video coming soon
Building your feature cost model
Add your PI features
Import from Jira or enter manually. Each feature needs a name, story point estimate, assigned team, and business value score (1–10 or MoSCoW).
Tag revenue features
Mark any feature that directly generates revenue. Add the expected revenue figure. ForecastInSite will calculate ROI automatically.
Track delivery status
As features complete, update their status. Incomplete features at PI end are your sunk cost signal — the next PI planning conversation starts here.
💡 Cost-per-point as a KPI
Cost per story point is your unit economics. Track it across 3+ PIs to spot whether your delivery efficiency is improving or degrading.
💡 Sunk cost visibility
Features started but not completed represent locked capital. Feature Economics surfaces this automatically — use it to challenge the "we've already started it" prioritisation bias.
Full Feature Economics Playbook
Includes feature scoring framework, ROI calculation methodology, cost-per-point benchmarks by team type, and the incomplete feature governance model.
Unlock Full PlaybookAI Workforce is ForecastInSite's dedicated module for modelling the financial and productivity impact of AI agents within your delivery teams. As AI tooling becomes a line item on every technology budget, AI Workforce gives you the governance framework to justify, track, and optimise that spend.
Key capabilities
- Model AI agents as team members with licence cost, compute cost, and productivity multiplier
- Calculate the human-equivalent cost of each AI tool — making ROI tangible
- See the blended human + AI cost per team against output delivered
- Track AI tool proliferation across teams and surface duplication of tools
AI Workforce walkthrough
Video coming soon
Governing your AI tooling spend
Audit all AI tools in use
Before modelling, list every AI tool each team uses — GitHub Copilot, Claude, Notion AI, Jira AI, etc. Many organisations discover 3–5x more AI spend than finance is tracking.
Set the productivity multiplier honestly
Don't use vendor claims. Use your team's actual experience. A conservative 1.2x (20% productivity boost) is more defensible than 2x and just as valuable in an ROI argument.
Compare human-equivalent cost
If a $500/month AI tool with a 1.3x multiplier replaces the equivalent of 1.3 humans at $8,000/month, the ROI is self-evident. ForecastInSite surfaces this comparison automatically.
💡 Compute cost matters
For internally deployed models, compute cost can dwarf licence cost. Always include both in your AI cost model — licence + compute = true AI spend.
💡 Tool consolidation opportunity
When multiple teams use different AI tools for the same purpose, AI Workforce surfaces the duplication. A single enterprise licence is almost always cheaper.
Full AI Workforce Playbook
AI tool audit template, productivity multiplier benchmarks by tool category, and the complete ROI governance framework for AI investment decisions.
Unlock Full PlaybookTeams & Capacity is where you build the financial DNA of your delivery organisation. Every team member, contractor, AI agent, and their associated cost rate is defined here. The module calculates monthly cost, PI-level cost, and FTE allocation automatically — feeding every other financial view in the tool.
Key capabilities
- Create unlimited delivery teams, each with a name, Agile Release Train, and primary role
- Add FTE members and contractors with daily or monthly cost rates — the tool converts to consistent monthly figures automatically
- Model AI agents as first-class team members with licence cost, compute cost, and productivity multiplier
- See real-time monthly team cost totals and PI-level projections as you configure each team
- Employment type badges (FTE / Contractor / AI Agent) give instant visibility of team composition
Teams & Capacity walkthrough
Video coming soon
⏱ ~90 seconds · Adding teams, members, cost rates, AI agents
Building your team cost model
Create your teams
Click Add Team. Give it a name that matches your Jira project or ART structure. Consistent naming matters — it flows through to all charts and reports.
Add members with cost rates
For each member, enter their name, role, employment type (FTE or Contractor), and cost rate. Choose Daily or Monthly rate — the tool normalises to monthly using a 20-working-day multiplier.
Set FTE percentage
If a member is only 50% allocated to this team, set FTE% to 0.5. Monthly cost and PI projections respect the FTE weighting.
Add AI agents
Click Add AI Agent. Enter the tool name, monthly licence cost, estimated compute cost, and productivity multiplier (e.g. 1.3 = 30% productivity boost). The tool models ROI automatically.
💡 Use blended rates for contractors
If you don't know individual contractor rates, use a blended market rate for the role. This is more defensible in governance reviews than guessing.
💡 AI agent ROI model
The productivity multiplier converts AI cost to human-equivalent value. A 1.5x multiplier on a $500/month tool means you're getting $750 worth of human capacity — model this before every AI tool renewal.
Full Teams & Capacity Playbook
Includes cost rate benchmarks by role, FTE allocation frameworks, contractor cost modelling guide, and the AI workforce ROI calculator methodology.
Unlock Full PlaybookValue Stream maps your delivery capacity to the value it produces — connecting the financial cost model to the flow of work through your organisation. It surfaces efficiency ratios, throughput trends, and where value is getting stuck before it reaches customers.
Key capabilities
- Value stream efficiency ratio — value delivered vs capacity consumed
- Flow metrics: throughput, cycle time, and WIP by team
- Cross-team value contribution analysis
- PI-over-PI value trend to identify improvement or degradation
Value Stream walkthrough
Video coming soon
Analysing your value flow
Review the efficiency ratio
Value stream efficiency = value delivered ÷ total capacity invested. An efficiency below 40% means more than half your spend is not producing customer value.
Identify throughput outliers
Teams with low throughput relative to their cost are your highest-risk investments. Use this data to ask whether team structure or backlog quality is the constraint.
💡 Value ≠ story points
High throughput teams delivering low-value features are expensive noise. Value Stream connects the two — don't manage velocity in isolation.
💡 WIP is a cost driver
Every feature in progress but not complete is capital locked. Value Stream makes WIP visible as a financial metric, not just a process metric.
Full Value Stream Playbook
Flow efficiency benchmarks, WIP limit guidance, and how to use value stream data in PI retrospectives and investment decisions.
Unlock Full PlaybookProductivity tracks team performance over time — velocity trends, capacity utilisation, and the contribution of AI agents to team output. It separates "busy" from "productive" by connecting effort to delivered value.
Key capabilities
- Velocity tracking per team across PIs and sprints
- Capacity utilisation rate — planned vs actual capacity consumed
- AI agent productivity contribution isolated and modelled separately
- Productivity trend indicators (improving ↑, declining ↓, stable →)
Productivity walkthrough
Video coming soon
Using productivity data in PI retrospectives
Review velocity trend first
Is the team delivering more or fewer story points per sprint compared to the last PI? A declining trend needs a root cause conversation before the next PI planning event.
Check utilisation rate
Teams consistently above 90% utilisation are at risk of quality problems and burnout. Teams consistently below 70% may have a backlog or dependency issue hiding a capacity problem.
💡 Velocity is a diagnostic, not a target
Never use velocity as a performance target — teams game it. Use it to spot systemic change (impediments, team restructure, tech debt load).
💡 AI contribution visibility
ForecastInSite is one of very few tools that lets you see the productivity delta from AI tooling. Track this across PIs to justify AI investment at finance review.
Full Productivity Playbook
Velocity benchmarks by team size, capacity utilisation guidance, and the AI productivity ROI model explained step by step.
Unlock Full PlaybookRelative Sizing calibrates story point estimates across teams so that financial comparisons are meaningful. If Team A's "5 points" costs $2,000 and Team B's "5 points" costs $8,000, cost-per-point is meaningless without a normalisation layer. This module provides that layer.
Key capabilities
- Calibrate story points against a reference feature to create a common sizing scale
- T-shirt to points mapping for organisations that estimate at initiative level
- Cross-team normalisation factor — comparable cost-per-point across teams of different maturity
- Historical velocity-based calibration to validate estimate accuracy
Relative Sizing walkthrough
Video coming soon
Calibrating your sizing model
Choose a reference feature
Pick one well-understood, mid-sized feature that every team can relate to. Size it as your "5-point reference". All other estimates calibrate relative to this anchor.
Apply normalisation factors
If Team A consistently delivers 2x the complexity per point compared to Team B, apply a 0.5 normalisation factor to Team B. Now cost-per-normalised-point is comparable.
💡 Don't compare raw velocity
A team doing 80 points a sprint and a team doing 40 points cannot be compared without normalisation. Relative Sizing makes this honest.
💡 Recalibrate every 3 PIs
As teams mature, their sizing baselines shift. Recalibrate every 3 PIs or after any significant team change to keep comparisons valid.
Full Relative Sizing Playbook
Calibration workshop guide, T-shirt to points conversion tables, normalisation methodology, and cross-team sizing governance framework.
Unlock Full PlaybookReporting aggregates every data point in ForecastInSite into stakeholder-ready outputs. Export PI financial summaries, team cost reports, and feature economics snapshots as structured JSON — ready for your BI tools, finance system, or governance portal.
Key capabilities
- Full data export as JSON — complete state snapshot including all teams, features, budget, and actuals
- PI financial summary — budget, actuals, variance, and forecast in a single structured output
- Feature economics report — cost, value, and ROI per feature, exportable for finance review
- Import previously exported data to restore any historical PI state
Reporting & Export walkthrough
Video coming soon
Setting up your reporting workflow
Export at every PI milestone
Export at PI planning, mid-PI review, and PI close. These three snapshots form your PI financial audit trail. Store the JSON files in your governance repository.
Share snapshots with Finance
The JSON export can be parsed by any BI tool (Power BI, Tableau, Looker) or loaded into a spreadsheet. Share the PI close export with Finance as your actuals reconciliation source.
💡 JSON is your backup
Local storage can be cleared. Every significant data entry should be followed by an Export. Treat JSON exports as your source of truth.
💡 Version your exports
Name exports with PI and date: FIS-PI4-2026-06-30.json. You'll thank yourself during the year-end audit.
Full Reporting Playbook
PI reporting templates, BI tool integration guide, governance audit checklist, and the finance reconciliation workflow.
Unlock Full PlaybookCapacity Planner connects team capacity to PI objectives — turning headcount and velocity into a concrete statement of what can be delivered this PI and at what cost. It's the bridge between the financial model and the delivery plan.
Key capabilities
- PI capacity calculation per team based on FTE, velocity, and sprint count
- Load analysis — available capacity vs planned feature point total
- Over-capacity detection with recommended rebalancing options
- Sprint-level capacity allocation for detailed PI planning
Capacity Planner walkthrough
Video coming soon
Running a PI capacity plan
Set team velocity baseline
Use the last 3–5 sprints average as your velocity baseline. Don't use the best sprint — use a realistic sustainable pace for capacity planning.
Apply availability adjustments
Subtract planned leave, innovation time, and PI ceremonies (typically 10–15% of capacity). ForecastInSite applies this as a configurable buffer.
Compare capacity to feature backlog
Load your PI feature list point totals. If total feature points exceed capacity, you're already over-committed before PI planning starts. Use this data to drive the prioritisation conversation.
💡 85% rule
Never plan to 100% capacity. 85% utilisation leaves room for unplanned work, defects, and dependencies. 100% utilisation = 0% responsiveness.
💡 Capacity is a financial constraint
A team with 200 capacity points and a $300k budget has a cost-per-point constraint. Capacity Planner makes this explicit before features are committed.
Full Capacity Planner Playbook
PI planning facilitation guide, capacity buffer framework, over-commitment detection and rebalancing methodology.
Unlock Full PlaybookThe RAID Log brings governance into the financial tool — tracking Risks, Assumptions, Issues, and Dependencies in the same context as your budget and delivery data. Every RAID item has a financial impact, an owner, and a status. No more "risks live in a separate spreadsheet no one reads."
Key capabilities
- Create RAID items across four types: Risk, Assumption, Issue, Dependency
- Assign financial impact, probability, and severity ratings to each item
- Track status (Open, In Progress, Closed, Escalated) with owner and due date
- Filter and sort by type, status, severity, and financial impact
RAID Log walkthrough
Video coming soon
Running your RAID governance cycle
Populate at PI planning
Every PI planning event should produce a RAID log. Walk through the PI objectives and ask: what could stop this? What are we assuming? What do we depend on others for? Enter each answer as a RAID item.
Review weekly
The RAID log should be a standing agenda item in your weekly PI sync. New items get added. Closed items get archived. Escalated items get immediate owner assignment.
Connect to financials
Every Risk should have a financial impact estimate. A risk with $50k impact and 70% probability is a $35k expected cost that should be in your risk reserve calculation.
💡 Dependencies are the biggest risk
In most scaled agile organisations, 60–80% of delivery delays trace back to cross-team dependencies. Capture every dependency before PI planning ends.
💡 Assumptions become risks
Every assumption that turns out to be false becomes an issue or risk. Review assumptions mid-PI — if the assumption is no longer valid, log a new risk immediately.
Full RAID Log Playbook
RAID workshop facilitation guide, financial impact estimation framework, escalation path templates, and the PI governance cadence.
Unlock Full PlaybookMilestones tracks the key delivery gates, review points, and commitments that matter to your stakeholders — with each milestone connected to the team, PI, and (optionally) a financial trigger. Never miss a steering committee date or release commitment again.
Key capabilities
- Create milestones with type (Release, Review, Commitment, Dependency), owner, and due date
- Track milestone status (Planned, At Risk, Complete, Missed) across PIs
- Link milestones to teams and features for traceability
- At-Risk detection — milestones within 7 days of due date without Completed status are flagged automatically
Milestones walkthrough
Video coming soon
Setting up your milestone calendar
Add all fixed dates first
Start with the non-negotiables: steering committee dates, release windows, regulatory deadlines, and contractual commitments. These anchor everything else.
Add PI internal milestones
System Integration Testing start, UAT start, go/no-go decision point, and PI demo. These form the internal gate structure that keeps the PI on track.
Assign owners, not teams
Every milestone must have a named owner — not a team. Teams don't miss milestones; individuals do. Named ownership drives accountability.
💡 Milestone density is a risk signal
More than 3 milestones in a single sprint is a governance smell. Compress milestone density and you reduce the risk of everything slipping together.
💡 At-Risk is a lagging indicator
Don't wait for the At-Risk flag. Review milestone confidence in your weekly sync — the 7-day flag is your last chance, not your early warning system.
Full Milestones Playbook
Milestone taxonomy, PI gate structure templates, at-risk escalation protocol, and the delivery governance calendar framework.
Unlock Full PlaybookConfiguration is where you align ForecastInSite to your organisation's financial calendar, PI structure, and governance thresholds. Get this right once and every calculation in the tool — from quarter mapping to PI cost — flows correctly from it.
Key capabilities
- Financial Year start month — drives all quarter, PI, and annual calculations
- PI schedule generator — define sprint length and count, and the tool builds your complete PI calendar automatically
- Quarter-to-PI mapping — visual confirmation that your PI boundaries align to your financial quarters
- RAG threshold configuration — set your own variance tolerances for Red and Amber status
Configuration walkthrough
Video coming soon
First-time configuration checklist
Set Financial Year start month
Australia: July (7). UK: April (4). USA: October (10) for federal, January (1) for most commercial. This single setting drives all downstream calculations.
Define your PI structure
Enter your sprint length (typically 2 weeks) and sprints per PI (typically 4–6). ForecastInSite generates the full PI schedule including IP sprint and PI dates.
Verify quarter alignment
Use the Quarter Mapping preview to confirm your PI boundaries land within financial quarter boundaries. Misaligned PIs make financial reporting significantly harder.
Set RAG thresholds
Configure your variance tolerance: Red at ±10%, Amber at ±5% is a common starting point. Align to your organisation's finance policy.
💡 Configure before adding teams
Configuration drives all downstream calculations. Add teams and features after configuration is complete — not before — to avoid recalculation surprises.
💡 PI alignment to quarters
If your PIs don't align to financial quarters, your finance team will always be reconciling estimates. Align PI planning to quarter boundaries where possible.
Full Configuration Playbook
FY configuration by country, PI structure templates for SAFe and non-SAFe teams, quarter alignment guide, and the governance threshold framework.
Unlock Full PlaybookUnlock the Full Playbook
Get complete step-by-step guidance for all 15 modules, practitioner templates, governance frameworks, and priority access to new playbook sections as ForecastInSite evolves.
Already have a licence? Open ForecastInSite →