Skip to content

Product backlog

Summary of docs/SISS - Project Planning V1.0 - Product Backlog V1.csv — six focus areas, ~15,700 man-hours total.

Focus areas

# Focus area Milestones Features (illustrative) Effort range Complexity Risk
1 Pre-submission / Pre-consultation M2 Technical agency pre-check · information pack for PSP · admin document pre-check · email notification S – L (5–20 man-days) Low – Moderate Minimal – Elevated
2 AI Checking vs SIRP Checklist M2 – M3 SIGL certificate report generation · automated SIRP criteria checking · HITL review M – XXL (60+ man-days per feature) Very High – Extremely High High – Extremely High
3 Technical Comment Management M3 Structured comment templates · Kertas Perakuan preparation · inline comment + markup L – XL (45–60+ man-days) Moderate – Very High Elevated
4 BIM File Handling M4 – M5 BIM presence / integrity check · lot boundary overlay · visual massing viewer · visual compliance checklist M – XL Moderate – Very High Elevated – High
5 BIM AI Capabilities M5 Height extraction · zoning comparison M – XL (45–60+ man-days) Very High High
6 Core Platform M2 CMU workflow · RBAC · SSO · integrated file storage · submission dashboard · ACC / CDE integration S (2–5 man-days per feature) Low Low

Complexity vs risk (quadrant view)

quadrantChart
  title Backlog focus areas — complexity × risk
  x-axis Low complexity --> High complexity
  y-axis Low risk --> High risk
  quadrant-1 "Validate carefully"
  quadrant-2 "De-risk first"
  quadrant-3 "Just build it"
  quadrant-4 "Iterate"
  "Core Platform": [0.15, 0.15]
  "Pre-consultation": [0.30, 0.30]
  "Technical Comments": [0.60, 0.45]
  "BIM File Handling": [0.60, 0.55]
  "BIM AI Extraction": [0.85, 0.75]
  "AI Checking vs SIRP": [0.95, 0.90]

Highest-risk items

  • AI Checking vs SIRP (Focus area 2) — the backlog flags "no clear pathway on how to train the AI to pre-fill each technical agency checking." See the open issue.
  • BIM AI Capabilities (Focus area 5) — M5 gates on ≥ 90% height extraction accuracy; the golden set needs to be large enough to be statistically meaningful.
  • Technical Comment Management (Focus area 3) — depends on curated historical comments per department; sourcing this corpus is its own project.

Sizing legend

Used in the spreadsheet; reproduced here for reference.

Size Range
S 2 – 5 man-days
M 5 – 20 man-days
L 20 – 45 man-days
XL 45 – 60 man-days
XXL 60+ man-days

This is a summary

See docs/SISS - Project Planning V1.0 - Product Backlog V1.csv for the full, feature-by-feature breakdown with user stories, intended outcomes, and split between "Dev" and "AI" effort estimates.