Q: 6
During Scoping the customer indicated that they neededcustomization to salesforce CPQDue to a
process in a legacy system what is the first stepin ensuring the requirement isAccounted for in
Scoping?
Options
Discussion
Makes sense to go with A here. Asking follow up questions helps confirm if customization is really needed or just legacy habit, which avoids scoping in unnecessary work. Pretty sure that's Salesforce's standard approach, but open to other views.
Not convinced B or C should be first, since you'd be planning customization before confirming it's even needed. You want to dig in and make sure the legacy process has a real business reason before anything else. That's why A makes more sense to me-gather info first so you don't just build extra work. Anyone disagree?
I don't think C is right here. The first step should be to make sure the legacy process is really needed before putting dev resources into scope. Otherwise, you might waste effort on unnecessary work. Pretty sure A is correct, since confirming business justification always comes first. Open to other views though if anyone's got a strong reason for C.
B makes sense too since you might want to account for extra hours early if customization is mentioned at scoping. I know A is technically safer, but sometimes people just go straight to hours based on legacy needs.
Its A, saw similar on practice and official doc says confirm business value before planning hours or dev. Could be wrong though.
Most reports say A, official guide and some practice exams mention verifying business need first.
A makes the most sense here imo. Before you burn budget scoping dev work or extra hours, you need to verify there's a real business case for keeping the legacy process in the new CPQ. Otherwise, you risk building custom stuff that's not even needed. Pretty sure that's best practice, unless I'm missing something.
Not really seeing how B would be first here. You want to ask follow-up questions (A) and get clear on the business need before locking in hours or dev work. Otherwise, you risk scoping for something that's not actually needed. Pretty sure it's A, but happy to hear other takes if I'm missing something.
Probably A since you always want to validate the business need for legacy processes before adding extra resources or hours.
Option A
Be respectful. No spam.
