MENU
A company develops a new children's education suite. The product contains four applications:
- an application for learning how to read
- an application for learning to count
- an application to tram basic addition and subtraction
- an application for parents or teachers to accompany the children's applications
All the product's applications are interdependent and must integrate with one another The company will be using a Nexus to scale the project
What is the best way to scale the product backlog?
Suggested Answer: B
Get Premium ASM Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
38 comments · newest first
AN
Anika
11 months ago
Not sure a single backlog will handle all the dependencies effectively.
NI
Nieves
11 months ago
Each app needs its own backlog, so A seems right.
IS
Isreal
11 months ago
Surprised they didn't mention user testing in the backlog!
NO
Norah
11 months ago
I disagree, option C could work better with separate focus.
MA
Mammie
12 months ago
I think option D makes the most sense for alignment.
DE
Denise
12 months ago
I recall that having a single Product Owner can streamline decision-making, but I wonder if that would work well with such different applications. Option D seems logical, but I have my doubts.
GA
Gail
12 months ago
I think we practiced a similar question where integrating components was key. I lean towards option C, but I'm not completely confident about having multiple Product Owners.
CO
Cortney
1 year ago
I'm not entirely sure, but I feel like having separate backlogs for each application could help manage priorities better. Maybe option A?
MA
Mattie
1 year ago
I remember we discussed how interdependent applications might benefit from a single backlog to avoid misalignment. So, I think option D could be a good choice.
KA
Karan
1 year ago
I think the key here is balancing the need for individual app ownership with the overall product integration. Option C of a single backlog with separate POs could work, but I'm not sure how well that scales. Lots to consider.
AV
Avery
1 year ago
I'm not sure - option A of having a separate backlog for each app seems simpler, but I'm worried that could make the integration harder to manage. Hmm, tough call.
PH
Phung
1 year ago
This seems like a tricky one. I'd want to think through the interdependencies between the applications and how that impacts the backlog structure.
LA
Lai
1 year ago
Okay, let's see. Since the apps are all interconnected, I'm leaning towards option B - creating a backlog for each tech layer that handles the integration. That way we can focus on the shared functionality.
MA
Marlon
1 year ago
I'm a bit confused by the wording here. I'll need to review my notes on bank security measures to decide if this is true or false.
SY
Sylvia
1 year ago
I remember practicing with similar questions, and I feel like Custom rules might work too.
IZ
Izetta
1 year ago
Hmm, I'm a bit unsure about this one. The IGMP settings seem pretty technical, and I'm not super familiar with the details. I'll have to read through it a few times to make sure I understand.
WI
Wilbert
1 year ago
Wait, they're using a Nexus to scale this project? I hope they've got some good plumbers on the team to handle all that pipe integration!
MU
Murray
1 year ago
D) Create a single product backlog and appoint a single Product Owner for the product
AL
Alaine
1 year ago
C) Create a single product backlog and appoint a Product Owner for each application
AR
Armando
1 year ago
B) Create a product backlog for each technological layer that handles integration
MA
Madelyn
1 year ago
A) Create a product backlog and set of product backlog items for each application
LO
Lorriane
1 year ago
Option A sounds like a lot of overhead to manage. Four separate backlogs? Yikes, that's gotta be a nightmare to coordinate!
DI
Dion
1 year ago
I'm leaning towards B. Focusing the backlog on the integration layers could help ensure the whole suite works seamlessly together.
LE
Leslee
1 year ago
Agreed, focusing on integration will be key for the success of the children's education suite.
LY
Lynda
1 year ago
Creating a product backlog for each technological layer sounds like a solid plan.
GL
Glory
1 year ago
I think B is a good choice. It's important to prioritize the integration layers.
CA
Carin
1 year ago
Option D seems a bit risky, having a single Product Owner for the entire product. Might be better to have individual owners for each app to ensure they get the attention they need.
MI
Mickie
1 year ago
A: That's true, it would help in managing the interdependencies between the applications more effectively.
TI
Tiera
1 year ago
B: I think creating a product backlog for each technological layer that handles integration could also be a good approach.
BE
Bettina
1 year ago
A: I agree, having individual Product Owners for each application would ensure they get the attention they need.
LO
Lou
1 year ago
Hmm, I think option C is the way to go. Separating the product backlog by application makes the most sense since they're all interdependent.
ED
Eden
1 year ago
That's true, it could help ensure that each application gets the attention it needs for successful integration.
LO
Lorean
1 year ago
I see your point, but having separate Product Owners could lead to better specialization and attention to detail.
VA
Val
1 year ago
But wouldn't it be more efficient to have a single Product Owner for the entire product?
WA
Wayne
1 year ago
I agree, having a Product Owner for each application would ensure focus and accountability.
AN
Annelle
2 years ago
That's an interesting perspective. I can see how having a single Product Owner for each application could ensure better focus and coordination.
ED
Edwin
2 years ago
I disagree, I believe creating a single product backlog and appointing a Product Owner for each application would be more efficient.
AN
Annelle
2 years ago
I think the best way to scale the product backlog is to create a product backlog for each technological layer that handles integration.