BacklogThe plan

The plan

Everything you need that is not on your own team page: the iteration goals, the roles, the cross-team contracts, the calendar and the fallback order. Source: Documents 32 to 35, now in the piDSS repository under docs/planning.

Iteration 3 · 14 to 28 October 2026

A client can see an honest savings estimate and payback for any of their sites.

Iteration 4 · 28 October to 11 November 2026

A client can save a bank-ready Decision Dossier and send it to an installer.

Who is who

The 11 assignable roles (contract C5) plus the visitor. Partner accounts register and a manager approves them.

Visitor
Browses without an account: the prelude and the Solar Offset Calculator.
Client
A business owner. Models their sites, sees savings and payback, saves the Dossier.
Client Manager
Keeps client records and tracks every quote request from sent to accepted.
Procurement Manager
Keeps the supplier and technician directories; approves suppliers and technicians.
Supply Manager
Curates the solar equipment catalogue, builds kits, tracks supplier pricing.
Rates Manager
Maintains every tariff, fuel charge and rule with its source and effective date.
Operations Manager
Keeps the installer directory; approves installers; oversees surveys.
Service Manager
Maintains maintenance plans and professional services.
Supplier
An approved equipment vendor keeping their own prices and as-of dates current.
Installer
An approved contractor receiving Dossier-backed quote requests and sending quotes.
Technician
An approved specialist certifying panel mounting area measurements.
Platform Owner
Assigns the roles above and holds the administrative override.

Cross-team contracts

Each owner publishes the contract plus seeded sample data by the date shown; consumers build against that from day one.

ContractOwnerPublish byWhat it fixes
C1 SiteTeam 5Thu 22 OctThe sites table every team keys records to (one record per building).
C2 Rates and rulesTeam 5Fri 23 OctOne store for tariffs, FCA, VAT, peak sun hours, insurance and loan rates. Nothing hard-coded.
C3 System designTeam 6Fri 23 OctThe sizing result (panels, inverter kW, battery kWh) that cost stories consume.
C4 Energy balanceTeam 6Fri 23 OctGenerated, self-consumed, exported and curtailed kWh. Export can never exceed generation.
C5 Role valuesTeam 5Thu 22 OctThe 11 role values in one field, replacing the separate admin flag for everything except the owner override.

Priorities and the fallback order

Every story on the board carries a Must, Should or Could badge. Work Must first. If your team falls behind, drop Should items in this order rather than whatever looks easiest:

  1. 2.12 View Panel Mounting Area (Team 3)
  2. 5.16 Loan calculator (Team 4). It moves to the head of Iteration 4
  3. 7.2 / 7.3 Kit add and edit (Team 3). Keep the as-of price date field in Iteration 3
  4. 1.12 then 1.11 Archive and edit site (Team 5)

Could haves (dropped first if velocity slips): platform services 4.6 to 4.9, glossary 0.8, equipment search and presets 2.2 and 2.4. Protected in Iteration 4: battery necessity 5.3 and the three-scenario comparison 5.18. Iteration 4 priorities are provisional until the Iteration 3 Review.

Dates that matter

Thu 22 Oct
Contract workshop (one developer per team plus the PO, 60 minutes)
Mon 26 Oct
Integration check, Teams 1, 4 and 6: savings page on real engine outputs
Wed 28 Oct
Iteration 3 Review (joint) and Overall Retrospective
Thu 29 Oct
Iteration Planning One and Two for Iteration 4
Wed 4 Nov
Integration check, all teams: Dossier and quote flow end to end
Mon 9 Nov
Feature complete; only fixes and tests after this
Wed 11 Nov
Iteration 4 Review and final demonstration