A Senior Software Engineer and you have a talk over coffee. She tells you she thinks Scrum is really cool, but that it doesn't work for projects that require complex architecture decisions upfront. Being a Scrum ambassador, you respond by telling her that in Scrum:

A Senior Software Engineer and you have a talk over coffee. She tells you she thinks Scrum is really cool, but that it doesn’t work for projects that require complex architecture decisions upfront. Being a Scrum ambassador, you respond by telling her that in Scrum:

A Senior Software Engineer and you have a talk over coffee. She tells you she thinks Scrum is really cool, but that it doesn’t work for projects that require complex architecture decisions upfront. Being a Scrum ambassador, you respond by telling her that in Scrum:
A . Architecture can receive more attention during early sprints, as long as a working piece of software is delivered.
B. Architecture is of little concern, as long as working valuable software is delivered.
C. Architecture typically emerges as part of the work being done.
D. Architecture is kept to a bare minimum. Simplicity – the art of maximizing the amount of work not done – is essential.
E. Architecture is handled in any self-managing way the cross-functional Scrum Team sees fit.

Answer: A,C

Explanation:

Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems.

Software is complex, and its architecture emerges during the Sprints. It will likely need more attention in early sprints. A few of the other answers are somewhat right but do not explain the way Scrum looks at emergent architecture.