MENU
How is architecture decided in a scrum team during a project?
Suggested Answer: B, C, D
Get Premium PSD Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Refinement meeting and release planing are no scrum events. The others are, and they are all about feedback: inspection and adaptation. (And in order for the inspection to have a good outcome, the artifacts need to be transparent)
38 comments · newest first
BE
Bette
10 months ago
E is a myth, teamwork is key for architecture decisions.
AL
Alisha
11 months ago
Wait, D? Can architecture really take care of itself?
CH
Christiane
11 months ago
C is outdated, we need flexibility in design!
CE
Cecily
11 months ago
I disagree, B makes more sense for sprint planning.
MA
Man
11 months ago
A is spot on! Architecture evolves with the project.
GA
Gail
12 months ago
I vaguely recall something about architecture being a team responsibility, but I can't remember if that means it takes care of itself like in option D.
YU
Yuki
12 months ago
I feel like upfront designs are not really a scrum thing, so I’d probably rule out option C.
CY
Cyril
12 months ago
I’m not sure, but I think we talked about architects defining things early in sprints, which makes me lean towards option B.
AM
Amber
1 year ago
I remember discussing how architecture can evolve during the project, so I think option A might be correct.
SH
Shakira
1 year ago
I'm a bit confused on this. Is the architecture defined upfront, or does it evolve over time? I'll need to think through the Scrum principles to decide.
HY
Hyun
1 year ago
I feel pretty confident about this one. In Scrum, the architecture emerges organically as the team builds the system, so I think A is the right answer.
GW
Gwenn
1 year ago
Okay, I've got a strategy for this. I'll start by eliminating the options that don't sound like typical Scrum practices.
RE
Ressie
1 year ago
Hmm, I'm not totally sure about this. I'll have to review my notes on Scrum to figure out the right way architecture is handled.
KR
Krystina
1 year ago
This is a tricky one. I'll need to think through the different approaches to architecture in a Scrum team.
CL
Clement
1 year ago
Okay, I'm pretty sure the answer is D. Supplier.Open (CRS620) seems like the most relevant program for registering a supplier in Accounts Payable.
RE
Rebeca
1 year ago
This is a straightforward question, in my opinion. The answer is clearly option D - a multiplier is applied to each SMS message based on the destination country. That would explain the high Super Message usage if NTO's subscriber base is global.
MO
Monroe
1 year ago
This seems like a straightforward routing question. I think I'll go with option A - creating a more specific route pointing to instance-B with no tag.
AN
Anglea
1 year ago
Okay, I think I can handle this. I just need to plug the given information into the right formulas and do the math. As long as I don't make any silly mistakes, I should be able to figure out the right probability.
GE
Genevieve
1 year ago
Option D is just plain silly. Architecture doesn't have a mind of its own - it needs to be intentionally designed and implemented.
KR
Krystina
1 year ago
E) An architect on the team undertakes all architecture tasks
AL
Alyssa
1 year ago
C) Upfront designs are presented to the developers prior to the first sprint
JA
Javier
1 year ago
B) The architect works in the early part of each sprint to define the architecture of that sprint
CA
Cathrine
1 year ago
A) The developers emerge architecture as the system is created
TR
Trinidad
1 year ago
Option E sounds like a recipe for a solo architect trying to control everything. I think a more collaborative approach is better.
RA
Raina
1 year ago
A) The developers emerge architecture as the system is created
JI
Jina
1 year ago
Option E does seem like it could lead to one person making all the decisions
AR
Aracelis
1 year ago
B) The architect works in the early part of each sprint to define the architecture of that sprint
FL
Fletcher
1 year ago
A) The developers emerge architecture as the system is created
FA
Fabiola
1 year ago
Option C is a bit too rigid for my liking. Upfront designs can often become outdated as the project progresses.
HE
Helga
1 year ago
I'd go with option B. Having an architect work on the architecture upfront for each sprint allows for a more structured and planned approach.
WI
Winfred
1 year ago
True, it's important to adapt the architecture process to what works best for the team and project.
RE
Reena
1 year ago
I think it depends on the project and team dynamics. Both approaches have their pros and cons.
JA
Jackie
1 year ago
But what about letting the developers emerge the architecture as they go along? That could be more flexible.
VE
Veronika
1 year ago
I agree, having a defined architecture at the beginning of each sprint helps set the direction.
VO
Von
1 year ago
Option A seems like the most agile approach. The developers should have the flexibility to shape the architecture as the project evolves.
SH
Sharen
2 years ago
I prefer option A, as it allows for flexibility and adaptation as the project progresses.
SH
Shaniqua
2 years ago
I agree with Cammy, developers emerge architecture during the project.
CA
Cammy
2 years ago
I think architecture is decided as the system is created.