Q: 4
Complete the sentence. When considering agile development, Architecture to Support Portfolio will
identify what products the Enterprise needs, the boundary of the products, and what constraints a
product owner has; this defines the Enterprise's
Options
Discussion
Option C is the fit here. D is tempting since operating model sounds 'big picture', but agile talk about product boundaries and constraints usually means backlog. Pretty sure C, but if I missed a subtlety let me know.
Makes sense to pick C here, backlog lines up with agile product owner constraints.
C , backlog directly maps to product constraints in agile so that's the match here.
Is it possible the question is intentionally steering us away from D by focusing on product boundaries and constraints? Operating model usually covers organization-wide processes, not agile product-level details. Feels like C fits better in agile context, but curious if anyone has a perspective for picking D here.
Are we sure C is the right fit here? Option D (operating model) is tempting since it's about enterprise structure, but "backlog" aligns more with agile terms for prioritizing work based on constraints and product boundaries. Is it possible the wording is trying to steer us away from traditional enterprise lingo toward agile-specific roles?
Makes sense, but it's really about what gets built next in agile. C fits since backlog is what product owners prioritize based on enterprise needs and constraints. Not 100 percent sure but this lines up with typical agile terminology.
Yeah, I agree with C since that's where agile teams keep the work items and constraints for products. Operating model (D) is more about how everything works at a business level, not the breakdown of stuff to build. If the question talked about processes or operations rather than products, I'd look twice at D. Anyone else see it another way?
C , since in agile the backlog is exactly where those product boundaries and owner constraints get documented. D (operating model) is broader, not really tied to product lists. I might be missing something subtle but pretty sure C.
Probably C for this one. In agile, the backlog is literally what gets defined by identifying products, boundaries, and constraints. D trips people up since operating model is more about how the business functions overall, not the specific list of things to build in agile. Unless I'm missing some odd wording, it's gotta be C.
C tbh, had something like this in a mock and backlog was definitely the answer tied to product constraints in agile.
Be respectful. No spam.
