Deciding the System Architecture in Scrum

In Scrum, decisions about the system architecture are collaborative and involve input from various team members and stakeholders to ensure that the architecture supports the goals of the project.

Exam Question

Who decides the system architecture of a product developed using Scrum?
(choose the best answer)
A. The software architect assigned to the Scrum Team.
B. The Developers with input from the Scrum Team and others.
C. The Chief Architect.
D. The Architect chosen by the Scrum Team.

Correct Answer

B. The Developers with input from the Scrum Team and others.

Explanation

Correct Answer

B. The Developers with input from the Scrum Team and others:
In Scrum, the responsibility for deciding the system architecture primarily lies with the Developers. The Developers are responsible for all technical decisions, including the architecture of the system. However, they collaborate with other members of the Scrum Team, such as the Product Owner and Scrum Master, and may seek input from external stakeholders, like architects or technical experts, to ensure that the architecture aligns with the overall goals and constraints of the product. This collaborative approach ensures that the architecture supports the needs of the product while leveraging the collective expertise of the team.

Why the Other Options Are Less Appropriate

A. The software architect assigned to the Scrum Team:
While a software architect may provide valuable input and guidance, the decision on the architecture is not made solely by an assigned architect. The Developers collectively make this decision, ensuring that it aligns with the team’s goals and the product’s requirements.

C. The Chief Architect:
The Chief Architect might have a role in setting overall architectural guidelines or standards within an organization, but in Scrum, the Developers are responsible for making decisions about the specific architecture of the product they are building.

D. The Architect chosen by the Scrum Team:
Similar to option A, while the Scrum Team might choose to work with an architect, the final architectural decisions are made by the Developers, who may incorporate the architect’s input into their decision-making process.

Relevance to the PSD Exam

Understanding the collaborative nature of architectural decisions in Scrum is important for the PSD exam. It emphasizes the self-organizing nature of Scrum Teams and the collective responsibility for technical decisions.

Key Takeaways

• Developers are responsible for making decisions about the system architecture in Scrum.
• They collaborate with the Scrum Team and seek input from others to ensure that the architecture meets the product’s goals and constraints.
• The decision-making process in Scrum is collaborative and collective, reflecting the self-organizing principles of Scrum Teams.

Conclusion

In Scrum, the system architecture is decided by the Developers, who collaborate with the Scrum Team and other stakeholders to ensure that the architecture supports the product’s goals. This approach ensures that architectural decisions are well-informed and aligned with the team’s collective expertise. For more information on preparing for the PSD exam, visit our Professional Scrum Developer PSD™ Exam Prep.