Deciding Architecture in a Scrum Team

In Scrum, the approach to architecture is adaptive and collaborative, allowing the architecture to evolve as the system is developed.

Exam Question

How is architecture decided by a Scrum Team?
(choose the best answer)
A. The architect works in the early part of each Sprint to define the architecture for that Sprint.
B. Upfront designs are presented to the Scrum Team prior to the first Sprint.
C. It emerges as the Developers create the system.
D. An architect on the Scrum Team undertakes all architecture tasks.
E. The architecture cares for itself as code is written and deployed.

Correct Answer

C. It emerges as the Developers create the system.

Explanation

Correct Answer

C. It emerges as the Developers create the system:
In Scrum, architecture is not fully designed upfront. Instead, it emerges and evolves as the Developers work on creating the system. This approach allows the architecture to adapt to the changing needs and insights that come with each Sprint. By allowing the architecture to emerge, the team can make informed decisions based on the current understanding of the product and its requirements, which helps to avoid the pitfalls of rigid, upfront design.

Why the Other Options Are Less Appropriate

A. The architect works in the early part of each Sprint to define the architecture for that Sprint:
This option implies that architecture is defined in isolation at the start of each Sprint, which is not how Scrum approaches architecture. The architecture evolves continuously as part of the development process, rather than being defined upfront in each Sprint.

B. Upfront designs are presented to the Scrum Team prior to the first Sprint:
Presenting upfront designs contradicts the Scrum principle of iterative development. In Scrum, the architecture should emerge over time rather than being fixed at the beginning of the project.

D. An architect on the Scrum Team undertakes all architecture tasks:
While there may be an architect on the team, architecture in Scrum is a shared responsibility among the Developers. The architecture emerges through collaboration, not by a single individual handling all architectural decisions.

E. The architecture cares for itself as code is written and deployed:
This option suggests a lack of intentional design and adaptation. In Scrum, while the architecture does emerge, it requires deliberate thought, collaboration, and adaptation as the system is developed.

Relevance to the PSD Exam

Understanding how architecture is handled in Scrum is crucial for the PSD exam, as it highlights the importance of iterative, emergent design in creating a flexible and adaptable system.

Key Takeaways

• Architecture in Scrum emerges as the Developers work on the system, allowing it to adapt to new information and requirements.
• This approach avoids the rigidity of upfront design and encourages collaboration and continuous improvement.
• Developers share the responsibility for the architecture, ensuring that it evolves in a way that supports the product’s goals.

Conclusion

In Scrum, architecture is not predetermined but emerges as the system is developed. This approach allows for flexibility and adaptation, ensuring that the architecture evolves in response to the team’s growing understanding of the product. For more information on preparing for the PSD exam, visit our Professional Scrum Developer PSD™ Exam Prep.