Answering: “When is a system’s architecture decided?”

Deciding a System’s Architecture in Scrum

In Scrum, the architecture of a system is not fully designed upfront. Instead, it evolves as the team gains more understanding of the project requirements and the challenges they face during development. This approach allows the architecture to be more flexible and adaptable to changes.

Exam Question

When is a system’s architecture decided?
(choose the best answer)
A. Before writing code.
B. In the beginning of the project, during Sprint 0.
C. Throughout development, as understanding emerges.
D. It is designed along with the vision, before the first Sprint.

Correct Answer

C. Throughout development, as understanding emerges.

Explanation

Correct Answer

C. Throughout development, as understanding emerges:
In Scrum, architecture is not set in stone at the beginning of a project. Instead, it evolves as the team learns more about the product and the challenges that arise during development. This emergent design approach allows the architecture to be more resilient to changes and better aligned with the actual needs of the product.

Why the Other Options Are Incorrect

A. Before writing code:
Deciding the architecture entirely before writing any code is more characteristic of traditional waterfall approaches. In Scrum, the architecture evolves and adapts as the project progresses.

B. In the beginning of the project, during Sprint 0:
The concept of Sprint 0 is not part of Scrum, and focusing solely on architecture at the beginning does not align with the iterative and incremental nature of Scrum.

D. It is designed along with the vision, before the first Sprint:
While some initial architectural decisions may be made before the first Sprint, the architecture is not fully decided at this point. It continues to evolve as the team gains more insight and experience throughout the development process.

Relevance to the PSD Exam

Understanding when and how a system’s architecture is decided is crucial for the PSD exam. It emphasizes the importance of flexibility and adaptability in the Scrum framework, where decisions are made based on the team’s growing understanding of the project.

Key Takeaways

• Emergent Architecture: The architecture evolves throughout the development process as the team’s understanding deepens.
• Flexibility: Scrum supports adaptability, allowing the architecture to change as new information and challenges arise.

Conclusion

In Scrum, a system’s architecture is decided throughout the development process as the team’s understanding of the project evolves. This approach allows for greater flexibility and ensures that the architecture remains aligned with the project’s needs.