MENU
In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.
The user story written on the card is:
"As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email."
By applying the 3C concept, which ONE of the following statements is CORRECT?
Suggested Answer: D
Get Premium CTFL-AT Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
40 comments · newest first
WI
William
11 months ago
A is the best answer, no doubt about it!
LA
Lavera
11 months ago
B is just wrong. The card should always reflect the user story.
TY
Tyra
11 months ago
Wow, I can’t believe some think D is an option. No convo? Really?
SA
Sarina
11 months ago
I disagree, C makes sense too. Confirmation isn’t always needed.
VI
Vincenza
11 months ago
A is definitely the right choice! Acceptance criteria are key.
RO
Rodrigo
12 months ago
I practiced a question like this, and I think we can't just jump into development without having a conversation first.
MA
Marjory
12 months ago
I feel like the product owner still needs to confirm the user story with the team before we start, right?
SA
Samira
1 year ago
I'm a bit unsure, but I think the card should actually contain the user story, not just requirements.
AR
Arlene
1 year ago
I remember the 3C concept emphasizes the importance of conversation, so I think we should definitely discuss acceptance criteria.
CA
Casie
1 year ago
This is a tricky one. I'm not entirely sure which option is correct, but I think I'll go with A. The conversation with the product owner seems like the key step here, and discussing the acceptance criteria would be an important part of that.
MO
Mozell
1 year ago
Okay, I think I've got it. The correct answer is A - Conversation should include the acceptance criteria discussion. The user story is just the starting point, and the team needs to have a conversation with the product owner to clarify the details and acceptance criteria.
KA
Karon
1 year ago
I'm a bit confused by this question. The user story seems clear enough, but I'm not sure how the 3C concept applies here. I'll need to re-read the question and options carefully to make sure I understand what they're asking.
GE
Geraldo
1 year ago
Hmm, this seems pretty straightforward. I think the key here is to focus on the 3C concept - Conversation, Confirmation, and Card. The question is asking which statement is correct, so I'll need to carefully consider each option.
KA
Kandis
1 year ago
I'm a bit confused on the best approach here. Should I just accept the sponsor's requirements or try to push back?
FR
Francesco
1 year ago
I'm a bit confused on the splunkd logs part. Do those count against the quota or are they exempt? I'll have to double-check that.
BR
Brandon
1 year ago
Hmm, I'm not sure about this one. I'm debating between B and C. The software installation in C could also be considered a standard change, but the security patch in B might be the better example. I'll have to think this through a bit more.
CH
Christa
1 year ago
I'm a bit confused by this question. I'll need to review my notes on Alfresco's SOLR subsystem to make sure I understand the implications of no in-transaction indexing.
ME
Merissa
1 year ago
Okay, I think I've got this. The service-level profile would likely contain higher-level information about the overall purpose and functionality of the service, while the capability-level profile would have more technical details about the individual service capabilities.
BE
Bette
1 year ago
The team should start developing? Yeah, and I should start running marathons without any training. Good one!
AI
Aimee
1 year ago
The team should start developing? Yeah, and I should start running marathons without any training. Good one!
TA
Tayna
1 year ago
B) The card should contain requirements not the user story.
LA
Lashawnda
1 year ago
A) Conversation should include the acceptance criteria discussion.
NI
Nicholle
1 year ago
Start developing without understanding the requirements? That's a recipe for disaster. I'll pass on that one.
BA
Barbra
1 year ago
Start developing without understanding the requirements? That's a recipe for disaster. I'll pass on that one.
WA
Walton
1 year ago
B) The card should contain requirements not the user story.
HO
Howard
1 year ago
A) Conversation should include the acceptance criteria discussion.
ET
Ettie
1 year ago
The product owner has written a user story, so confirmation is needed to ensure the team understands it correctly.
JU
Junita
1 year ago
Seriously? The card should contain the requirements? What is this, the 90s?
RE
Rebeca
1 year ago
A) Conversation should include the acceptance criteria discussion.
OR
Oretha
1 year ago
Seriously? The card should contain the requirements? What is this, the 90s?
UL
Ulysses
1 year ago
B) The card should contain requirements not the user story.
MA
Malcolm
1 year ago
A) Conversation should include the acceptance criteria discussion.
LE
Lenny
2 years ago
The conversation is crucial to understand the user story. Acceptance criteria should definitely be discussed.
VE
Venita
1 year ago
B) The card should contain requirements not the user story.
HU
Hubert
1 year ago
A) Conversation should include the acceptance criteria discussion.
NI
Nina
1 year ago
B) The card should contain requirements not the user story.
MA
Magdalene
1 year ago
A) Conversation should include the acceptance criteria discussion.
ER
Erin
2 years ago
I believe the product owner has written a user story, but it's still necessary to have a conversation to ensure everyone is on the same page.
RA
Raymon
2 years ago
I agree with Marshall, it's important to clarify the details before starting development.
MA
Marshall
2 years ago
I think the conversation should include the acceptance criteria discussion.