Which approach best describes delivering work in small increments in agile?

Delivering all features in one large release

Delivering only the most complex features first

Delivering small, valuable pieces of functionality frequently

Releasing all features at the end of the project

A team is working on a project where the primary stakeholder is often unavailable. The team has a short iteration length and wants to collect feedback regularly. What is the best way to ensure feedback is still collected?

Proceed without feedback and assume the stakeholder's needs are understood

Establish a feedback channel that allows the stakeholder to provide input asynchronously, such as a shared document or feedback tool

Ask the product owner to make all decisions on behalf of the stakeholder

Wait for the stakeholder to be available, even if it means skipping feedback for an iteration

A team is developing a new customer relationship management (CRM) system. The sales team is the primary stakeholder and has strong opinions about the features. What is the best way to ensure their feedback is incorporated into each iteration?

Collect sales feedback only at the end of the project

Ask the product owner to summarize sales feedback after each sprint

Send a survey to the sales team after each release

Invite a sales representative to the sprint review and backlog refinement sessions

What is the recommended cadence for collecting stakeholder feedback in an agile project?

Only when the project is complete

Only at the start of the project

A team is building a new customer portal. The product owner wants to validate the navigation flow before investing in full visual design. Which approach best enables early feedback on the navigation?

Build the complete portal in a single release to avoid partial features

Wait until the full portal is built, then conduct a usability test

Develop a clickable prototype with basic wireframes and test it with a few users

Ask the product owner to review the navigation requirements document

PMIAgile Certified Practitioner (PMI-ACP)

Domain 4Objective 1

Task 1 Seek Early Feedback PMI-ACP Practice Questions (Page 4)

Part of the Domain 4 Delivery domain, which accounts for 28% of the PMI-ACP exam. PMI does not publish an official question count, but from its 180-minute exam (~70–120 total, ~20–34 in this domain), expect 3–5 from this objective — we provide 24 practice questions to prepare you well beyond it. (estimate)

24questions here

5free pages

3concepts

28%of the exam

Questions 16–20

16foundation · easy
Which approach best describes delivering work in small increments in agile?
Select an answer first
17expert · hard
A team is working on a project where the primary stakeholder is often unavailable. The team has a short iteration length and wants to collect feedback regularly. What is the best way to ensure feedback is still collected?
Select an answer first
18application · medium
A team is developing a new customer relationship management (CRM) system. The sales team is the primary stakeholder and has strong opinions about the features. What is the best way to ensure their feedback is incorporated into each iteration?
Select an answer first
19foundation · easy
What is the recommended cadence for collecting stakeholder feedback in an agile project?
Select an answer first
20application · medium
A team is building a new customer portal. The product owner wants to validate the navigation flow before investing in full visual design. Which approach best enables early feedback on the navigation?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to PMI-ACP

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by PMI. “PMI-ACP” is a trademark of its owner, used for identification only.