Final answer:
In programming, result components are typically built after procedures to ensure that they properly display or act upon the outcomes of the procedures, though methodologies like Agile may differ.
Step-by-step explanation:
It is typically important for result components to be built after procedures in a programming or software development context. This is because procedures, which are sequences of programmed instructions, often determine the logic and outcomes that the result components display or act upon. If the result components are designed or built first without a clear understanding of the procedures, it could lead to mismatches between what the components are supposed to do and what the procedures actually produce. However, in some methodologies like Agile or when employing rapid prototyping, components may be built first as a visual or interactive mock-up, but these are usually refined or completely rebuilt once the procedures are defined.