PRINCE2-Agile-Foundation Exam - Topic 2 Question 68 Discussion

Actual exam question for PRINCE2's PRINCE2-Agile-Foundation exam

Question #: 68
Topic #: 2

[All PRINCE2-Agile-Foundation Questions]

What BEST defines embryonic customer requirements?

A'Fine-grained' user stories

BEpics

CSub-products

DTechnical stories

Show Suggested Answer

Suggested Answer: C

by Na at Feb 10, 2025, 04:23 AM

Limited Time Offer

25%

Off

Get Premium PRINCE2-Agile-Foundation Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Lelia

8 months ago

Surprised to see 'fine-grained' as the answer!

upvoted 0 times

...

Nana

8 months ago

Really? I thought technical stories were the way to go.

upvoted 0 times

...

Gilma

8 months ago

Sub-products? Not sure about that one.

upvoted 0 times

...

Brandon

9 months ago

I think epics fit better for this.

upvoted 0 times

...

Rhea

9 months ago

Definitely 'fine-grained' user stories!

upvoted 0 times

...

Lili

9 months ago

I practiced a similar question where epics were mentioned as high-level requirements. Maybe that's what they mean here?

upvoted 0 times

...

Nobuko

9 months 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.

upvoted 0 times

...

Melodie

9 months ago

I remember we discussed epics in class, but I can't recall if they really fit the definition of embryonic requirements.

upvoted 0 times

...

Twana

10 months 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.

upvoted 0 times

...

Levi

10 months 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.

upvoted 0 times

...

Dierdre

10 months 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.

upvoted 0 times

...

Jackie

10 months 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.

upvoted 0 times

...

Scarlet

10 months ago

This question seems straightforward, but I want to make sure I understand the terminology correctly before answering.

upvoted 0 times

...

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!

upvoted 0 times

...

Wynell

1 year ago

Sub-products? What is this, some kind of embryonic software development? I'm going with A, 'fine-grained' user stories.

upvoted 0 times

...

Sheldon

1 year ago

Technical stories? Really? That doesn't sound right at all. This is about the customer, not the technical implementation.

upvoted 0 times

Jeff

1 year ago

Technical stories are more about the technical implementation, not the customer requirements.

upvoted 0 times

...

Susana

1 year ago

D) Technical stories

upvoted 0 times

...

Denae

1 year ago

C) Sub-products

upvoted 0 times

...

Karon

1 year ago

B) Epics

upvoted 0 times

...

Antione

1 year ago

A) 'Fine-grained' user stories

upvoted 0 times

...

Zack

1 year 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.

upvoted 0 times

Christa

1 year ago

C) Sub-products

upvoted 0 times

...

Dorothy

1 year ago

B) Epics

upvoted 0 times

...

Amie

1 year ago

A) 'Fine-grained' user stories

upvoted 0 times

...

Royal

1 year 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.

upvoted 0 times