Posts connected by the technical-program-management tag.
2 posts
Roughly 80% of the software I produce now starts as a prompt, not a keystroke. Mapped onto the Quest Engine, that means agents have moved into the Drive (the How) and are eating into the four W's. What is left for me is the Why, the context still trapped in people's heads, and the work of running a fleet of agents predictably.
Start with the code works for the software engineering circle of the Venn diagram, but a technical program manager naturally starts from the why, not the code. Once agents act like subordinates, the person steering them sits in the overlap and needs two documents: a Why doc facing outward toward the problem and stakeholders, and a How doc facing inward toward the agent's technical direction.