Final answer:
In Scrum, architecture is evolved as the product development progresses, and infrastructure is developed and adapted based on product needs. These are handled iteratively, with a focus on technical excellence and accommodating future changes.
Step-by-step explanation:
In the Scrum framework, architecture and infrastructure are incorporated iteratively and incrementally. First, architecture is evolved as the product evolves; it is not something that needs to be perfectly defined upfront but is developed throughout the sprints as the team learns more about the problem space and solution space. Second, infrastructure development follows a similar path, created and adapted as the needs of the product emerge, promoting the DevOps culture of continuous integration and continuous delivery. For example, the Scrum team can identify architectural components and make necessary infrastructure choices as part of Sprint Planning while being flexible to accommodate future changes and improvements.
Sprint Planning allows the Scrum team to identify architectural needs and infrastructure requirements at the beginning of each sprint, and Sprint Review meetings provide opportunities for revisiting and adjusting architectural decisions as the product develops. The aim is not only to strive for functional completeness but also to ensure the system's architecture can support the upcoming features, potentially requiring a refactoring effort as part of the development work. Emphasizing on technical excellence, a Scrum team integrates architectural work within Sprints to manage complexity and maintain product quality.