Handling Architecture and Infrastructure in Scrum

In Scrum, architecture and infrastructure are crucial components that need to be integrated into the product development process. This article explores a specific exam question about how these elements are managed within the Scrum framework, providing detailed explanations and insights relevant to the PSM I exam.

Exam Question

What are two ways that architecture and infrastructure are handled in Scrum? (choose the best two answers)

• A. They are discussed, determined, and documented before the actual feature development Sprints.
• B. They are built by a separate team through the creation of an architectural runway.
• C. They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality, no matter how small.
• D. They are implemented along with functional development of the product.

Correct Answers

C. They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality, no matter how small.
D. They are implemented along with functional development of the product.

Explanation

Correct Answers

C. They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality, no matter how small: In Scrum, architecture and infrastructure tasks are treated as Product Backlog items. These tasks are prioritized and worked on in early Sprints to ensure that the necessary foundation is in place. However, even in these early Sprints, it is essential to deliver some business functionality to maintain a focus on delivering value.

D. They are implemented along with functional development of the product: Architecture and infrastructure are integrated into the ongoing development work. Rather than separating these tasks into different phases or handled by separate teams, they are addressed as part of the regular Sprint work. This integration ensures that architectural and infrastructure needs evolve alongside the product, supporting iterative development and continuous delivery.

Incorrect Answers

A. They are discussed, determined, and documented before the actual feature development Sprints: This approach aligns more with traditional project management methodologies (waterfall) and contradicts the iterative and incremental nature of Scrum. In Scrum, upfront detailed planning and documentation are minimized to allow for adaptability and responsiveness to change.

B. They are built by a separate team through the creation of an architectural runway: This approach separates the architectural and infrastructure work from the development work, which is contrary to Scrum principles. Scrum promotes cross-functional teams that work collaboratively on all aspects of product development, including architecture and infrastructure.

Responsibilities in Scrum

• Product Owner: The Product Owner is responsible for ensuring that architecture and infrastructure tasks are included in the Product Backlog. They prioritize these tasks based on their value and importance to the overall product development.
• Scrum Master: The Scrum Master facilitates the integration of architectural and infrastructure work into the regular Sprint activities. They ensure that the team follows Scrum practices and supports the team in removing any impediments.
• Developers: Developers collaborate on both functional and non-functional requirements, including architecture and infrastructure. They ensure that these elements are addressed as part of the incremental delivery of the product.

Relevance to the PSM I Exam

Understanding how architecture and infrastructure are handled in Scrum is crucial for the PSM I exam. It demonstrates knowledge of Scrum principles and the importance of integrating these elements into the iterative development process. Mastering this concept ensures that Scrum Teams can effectively manage all aspects of product development.

Key Takeaways

• Architecture and infrastructure tasks are added to the Product Backlog and addressed early while still delivering some business functionality.
• These tasks are implemented alongside functional development, supporting an iterative and incremental approach.
• Scrum promotes the integration of all aspects of development within cross-functional teams, ensuring comprehensive and cohesive product delivery.

Conclusion

In Scrum, architecture and infrastructure are handled by integrating these tasks into the Product Backlog and addressing them alongside functional development. This approach ensures that these critical elements evolve with the product and support continuous delivery. Understanding this concept is essential for effective Scrum implementation and success in the PSM I exam. For comprehensive preparation and practice exams, check out PSM I Exam Prep to enhance your understanding and application of Scrum principles.