A developer is titled System Architect on the state DMV licensing ART but never offers architectural guidance or runway items at PI Planning. What is missing?
Select an answer to reveal the explanation.
Short Explanation
A nameplate that says System Architect is not the job. The job is showing up at PI Planning with technical vision and the next strip of runway so DMV licensing teams can actually build. Title without guidance is costume.
Full Explanation
System Architect/Engineering provides technical vision, guidance, and runway support during planning. A developer titled System Architect on a state DMV licensing ART who never offers architectural guidance or runway items at PI Planning is missing the job behind the title. Requiring that the architect estimate every licensing story for the teams is not the architect's defining duty and confuses guidance with team estimating. A rule that architecture is only discussed after the PI ends arrives too late to shape the plan drivers and clerks depend on. Transferring the architect title to the RTE so facilitation includes design confuses roles and still leaves technical vision unserved if the RTE is not actually doing architecture. Exam caveat: Architecture engagement should be collaborative and just-enough, not a gate that freezes teams, but absence from planning is the failure mode here. Operational check: Require architecture briefing and enabler candidates in the DMV planning agenda, and check that runway items appear on the program board with owners. 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.