pwaLUPMIS2/LUPMIS2_Work_Breakdown_Open_Scope.xlsx
ekke 1f8b0c96c0 Work breakdown for the open scope: 61 tasks, 163-268 developer days
A sequenced schedule of everything not yet addressed, drawn from the Functional
Specifications v4, the Open Issues and Estimates handout of 18 September 2026,
Development Status Report v9, and this month's review of the running system.

The estimates from September are carried over unchanged; a Source column marks
which figures are the project's own, which come from the status report, and
which are mine. Twelve items are new from the October review and were not in
either document: the Save action in the drawing toolbar has no listener
registered, so edits are never written back; overlay analysis holds the main
thread for about nine seconds at 8,000 features; spatial.lu_parcels carries
3.1 million rows with zero indexes; the parcel geometry column is declared bare
so catalogues report SRID 0 while the data is EPSG:4326; collector zones sit in
a text column as WKT; and the Applicant Portal's only dependency on this
module, the parcel-map embed endpoint, is not built.

The Seq column is a recommended start order rather than a serial plan, since
fourteen of the sixty-one belong to infrastructure, the database team, LUSPA or
the permitting team. It opens with the container's AllowOverride setting,
because that leaves an already-deployed fix inert, and raises the four LUSPA
inputs and the MoU process early only because they have the longest lead times.
Foundations follow — index and repair the parcel and zone data before building
on it — then the pilot-workshop feedback, then the remaining specification
scope.

Role-based access control and the server audit trail appear once rather than
twice, and a third sheet lists what has closed since September so nothing is
counted in both places.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-10-20 15:11:14 +02:00

16 KiB