How are architecture and infrastructure treated in Scrum?

In Scrum, architecture and infrastructure are considered essential components of the product being developed. Treating them by adding them to the Product Backlog and addressing them in early Sprints aligns with the principles of iterative and incremental development inherent to Scrum. This approach allows the team to identify and build foundational elements of the product that support future development efforts. It ensures that architectural decisions are made in a timely manner, reducing the risk of encountering significant issues later in the development process that could hinder progress or lead to technical debt.

Addressing architecture and infrastructure early in the development cycle allows for continuous refinement and adaptation of both as requirements evolve. This is crucial in Scrum, where the focus is on delivering value incrementally and fostering collaboration among team members. By prioritizing these elements in the Product Backlog, the Scrum Team can ensure that they are integrated with feature development, enhancing the overall quality and performance of the product.