The city permits portal ART plans together each PI but never integrates work or holds a System Demo. What pattern should the RTE correct?
Select an answer to reveal the explanation.
Short Explanation
Planning the parade route is not the same as actually marching together. An ART that never integrates or demos the permits portal is just a planning club. The System Demo is where the train proves one working increment.
Full Explanation
An effective ART regularly integrates and demonstrates a working system, not just a shared plan. When a city permits portal ART plans together each PI but never integrates work or holds a System Demo, it has synchronized calendars without synchronized product outcomes for applicants and bureaus. The RTE should correct that pattern by restoring integration and demo cadence. Claiming planning together is enough and that integration can wait until annual inspection season delays feedback until defects are expensive. Replacing System Demos with individual team slide decks sent by email substitutes status for working permitting software. Skipping demos because residents never see internal software ignores that internal users and integrated subsystems still need validated increments. Exam caveat: Not every team ships to the public portal every PI, but the ART still needs an integrated System Demo of the current increment. Operational check: Schedule System Demo on the permits ART calendar, require an integrated build, and track which cross-team stories actually appear working versus merely planned. In municipal settings, pressure to look busy, compliant, or politically safe is constant; the RTE earns trust by holding the principle through that pressure and verifying the next cadence event shows improved civic delivery, not just a quieter meeting. Capture the before/after signal so sponsors see the operational evidence.