As a Scrum Master, what is the most appropriate action you can take?

After Sprint 6, Developers say they need to complete the software architecture before they can begin working on the functional requirements.

As a Scrum Master, what is the most appropriate action you can take?
A . The Scrum Master should ask the Developers to resolve this issue themselves.
B. Stop the ongoing Sprint and focus on completing the architecture first.
C. Consider the architecture as technical debt and only focus on the functionality which needs to be built.
D. Coach the Developers that the architecture does not need to be perfect.

Answer: D

Explanation:

Agile Principle: Simplicity–the art of maximizing the amount of work not done–is essential. KISS: An acronym for "keep it simple, stupid", is a design principle noted by the U.S. Navy in 1960. The KISS principle states that most systems work best if they are kept simple rather than made complicated; therefore, simplicity should be a key goal in design, and unnecessary complexity should be avoided. YAGNI: "You aren’t gonna need it" is a principle of extreme programming (XP) that states a programmer should not add functionality until deemed necessary. XP co-founder Ron Jeffries has written: "Always implement things when you actually need them, never when you just foresee that you need them." Other forms of the phrase include "You aren’t going to need it" and "You ain’t gonna need it". The application’s overall architecture is not designed upfront, as the actual implementation of it emerges. The emergence

of the Architecture is based on guidelines and agreed principles. The System’s architecture is decided throughout the project, as understanding emerges, and the Developers learn more about the project.

Latest PAL-I Dumps Valid Version with 305 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments