What BEST defines embryonic customer requirements?
Suggested Answer: C
Get Premium PRINCE2-Agile-Foundation Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
33 comments · newest first
LE
Lelia
11 months ago
Surprised to see 'fine-grained' as the answer!
NA
Nana
12 months ago
Really? I thought technical stories were the way to go.
GI
Gilma
12 months ago
Sub-products? Not sure about that one.
BR
Brandon
1 year ago
I think epics fit better for this.
RH
Rhea
1 year ago
Definitely 'fine-grained' user stories!
LI
Lili
1 year ago
I practiced a similar question where epics were mentioned as high-level requirements. Maybe that's what they mean here?
NO
Nobuko
1 year ago
I feel like technical stories might be too specific for this question. I think embryonic requirements are broader, but I can't quite remember.
ME
Melodie
1 year ago
I remember we discussed epics in class, but I can't recall if they really fit the definition of embryonic requirements.
TW
Twana
1 year ago
I think embryonic customer requirements are related to early-stage user needs, but I'm not sure if that means 'fine-grained' user stories or something else.
LE
Levi
1 year ago
'Fine-grained' user stories sound like they might be the most detailed and specific requirements, so I'm leaning towards that as the best answer.
DI
Dierdre
1 year ago
Okay, I think I've got this. Embryonic customer requirements are the most basic, high-level needs that customers have, which would likely be captured in epics. I'll go with that.
JA
Jackie
1 year ago
Hmm, I'm a bit unsure about the difference between 'fine-grained' user stories and technical stories. I'll need to review my notes on that.
SC
Scarlet
1 year ago
This question seems straightforward, but I want to make sure I understand the terminology correctly before answering.
JO
Jonelle
1 year ago
Embryonic requirements, huh? I bet that's when the customer is still just a little egg, waiting to hatch into a fully-formed product. A for the win!
WY
Wynell
1 year ago
Sub-products? What is this, some kind of embryonic software development? I'm going with A, 'fine-grained' user stories.
SH
Sheldon
1 year ago
Technical stories? Really? That doesn't sound right at all. This is about the customer, not the technical implementation.
JE
Jeff
1 year ago
Technical stories are more about the technical implementation, not the customer requirements.
SU
Susana
1 year ago
D) Technical stories
DE
Denae
1 year ago
C) Sub-products
KA
Karon
1 year ago
B) Epics
AN
Antione
1 year ago
A) 'Fine-grained' user stories
ZA
Zack
2 years ago
Hmm, I was thinking that epics would be the best choice since they encompass the broader customer needs. But I could be off base here.
CH
Christa
1 year ago
C) Sub-products
DO
Dorothy
1 year ago
B) Epics
AM
Amie
1 year ago
A) 'Fine-grained' user stories
RO
Royal
2 years ago
I'm pretty sure embryonic customer requirements are those that are still in the early stages of development, like 'fine-grained' user stories. A seems like the best answer to me.
MA
Maia
1 year ago
I think technical stories could also be part of embryonic customer requirements.
FE
Felice
1 year ago
I'm not sure, but maybe epics could also be considered embryonic customer requirements.
ER
Eric
2 years ago
I agree, A) 'Fine-grained' user stories seem to be the best fit for embryonic customer requirements.
SO
Sommer
2 years ago
I think embryonic customer requirements are like 'fine-grained' user stories.
SE
Serita
2 years ago
That makes sense, but I still think A) is more specific and detailed.
ST
Stephen
2 years ago
I disagree, I believe it's B) Epics because they capture high-level customer needs.
SE
Serita
2 years ago
I think it's A) 'Fine-grained' user stories.