A consultancy's proof of concept met its success criteria. The sponsor wants to build the rest of the backlog immediately and skip the roadmap. What should the architect do with the proof?
Select an answer to reveal the explanation.
Short Explanation
A pilot that worked is a reason to reshuffle the job list, not a reason to build every job on it. You use the proof results to adjust which remaining use cases come first, and you scale only after that roadmap is accepted. Skipping the roadmap spends the next quarter on items the proof may have weakened.
Full Explanation
A proof of concept is evidence for the plan, not a hall pass around it. The Cloud Adoption Framework plan says to use proof results to adjust use-case priority, so a proof that met its criteria should change which remaining items come first. Items the proof made more feasible move up, items it weakened move down, and scaling starts from that updated roadmap rather than from the original pile. Building every remaining item now, and skipping the roadmap, treats one success as proof that unrelated backlog rows are ready. Discarding the successful proof and opening a new one on a different model throws away the result the sponsor just paid for and delays the ranking. Stopping the program because one proof worked confuses a passed test with a finished portfolio. The proof's success criteria stay attached to the item that passed. Exam caveat: a passed proof does not promote the whole backlog, and it is not a reason to build every remaining item while skipping the roadmap. The roadmap is where the adjusted priority is written down. Operational check: attach the proof notes to the backlog, record the new order, and start scale only on the item that now sits at the top.