Agile puts working software above comprehensive docs, per the Agile Manifesto. The other options flip agile values around, which isn't accurate. Pretty sure it's D, but open to other takes.
Q: 2
Which of the following value comparisons MOST accurately reflects the agile development
approach?
Options
Discussion
D fits best here. Agile is about delivering working software and not getting bogged down in heavy documentation. The other options flip the agile values, so pretty sure D is correct but open to other thoughts if I missed something.
C/D? Both get picked sometimes but I'm saying D. That's the straight-up Agile Manifesto wording.
D
Agile puts working software above comprehensive docs, per the Agile Manifesto. The other options flip agile values around, which isn't accurate. Pretty sure it's D, but open to other takes.
Agile puts working software above comprehensive docs, per the Agile Manifesto. The other options flip agile values around, which isn't accurate. Pretty sure it's D, but open to other takes.
C , since planning is huge in dev projects. I know Agile values adaptability, but following a plan seems more accurate if you consider how teams actually try to structure sprints. D feels a bit too obvious a trap here. Could be wrong though.
D , that's the closest match to Agile's actual values.
D imo, that's straight from the Agile Manifesto-working software prioritized over docs every time.
I don't think it's D, since Agile is more about collaboration and flexibility. B looks tempting because contract negotiation sometimes gets highlighted as important in large orgs, so I'd say B for this one. Trap option with D if you aren't careful.
Maybe D here, since the others are all giving the wrong priority (that's a common trap for Agile values questions). If it's about what Agile really emphasizes, working software wins over docs but not 100 percent sure.
B . Contract negotiation over customer collaboration makes sense to me since you want the agreement sorted out early for less risk, especially in bigger projects. Agile talks a lot about collaboration, but sometimes contracts are the real foundation. Not 100% if this is what they’re after but that’s my take.
Don’t think it’s D here, since Agile actually values documentation less than working software. For this, maybe A is closer but I could be off-tricky question the way they inverted the values.
Be respectful. No spam.
Question 2 of 35