In an Agile Service Cloud implementation, how should the consultant deliver to ensure continuous feedback and adjustments?

• A. Deliver the entire project simultaneously so as to present UC with a completed solution
• B. Set a cutoff date of 1.5 months before user acceptance testing for any change request
• C. Generate continuous feedback from the project team, and adjust the requirements and deliverables accordingly
• D. Schedule a meeting with the UC executives at the start of the project to generate all the requirements

Answer: (C)

Iterative, feedback-driven delivery is essential in Agile Service Cloud projects. By generating continuous feedback from the project team and stakeholders and adjusting the requirements and deliverables accordingly, the consultant keeps the solution evolving with real needs, delivering value in small, usable increments. Frequent feedback—through sprint reviews, demos, and ongoing backlog refinement—lets the team learn, reassess priorities, and incorporate new insights as they arise, reducing risk and misalignment.

Alternatives that fix requirements too early or wait for a single, large delivery don’t fit this mindset. Locking in changes before user testing prevents new learnings from shaping the solution; scheduling one-time requirements gathering at the start ignores changing needs; delivering everything at once resembles waterfall and misses opportunities for early value and course correction. Continuous feedback and adjustment, in contrast, keeps the Service Cloud implementation flexible, user-focused, and better aligned with the business over time.