MENU
Over the past month, a business analyst (BA) has worked with various stakeholders at Cloud Kicks to document requirements for an upcoming Tableau implementation. A stakeholder suggested a revision to the requirements. The BA sent the updated requirements to the stakeholders and they signed off.
Where should the BA track this milestone?
Suggested Answer: B
Get Premium Salesforce Certified Business Analyst (BA-201) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Strategy analysis is the process of identifying and evaluating the risks and benefits of a proposed solution, as well as its alignment with the business goals and objectives. A business analyst performs strategy analysis to understand the impact of a solution on the project timeline, budget, scope, quality, and stakeholders.
https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-certification-prep/perform-strategy-analysis
https://www.iiba.org/standards-and-resources/babok/strategy-analysis/
35 comments · newest first
CY
Cyndy
11 months ago
Change log is the way to go! Keeps everything organized.
IN
In
11 months ago
Really? I thought sprint plans were for tracking progress, not changes.
JE
Jennifer
12 months ago
Wait, shouldn't this be in the statement of work?
LA
Layla
12 months ago
I agree, change log makes the most sense here.
JO
Josephine
1 year ago
Definitely the change log! It's all about tracking changes.
BI
Billy
1 year ago
I feel like the statement of work might be too broad for this specific milestone. The change log seems more focused on the updates we’re discussing.
BR
Brianne
1 year ago
I’m a bit confused about the sprint plan. I thought that was more for tracking tasks during development rather than documenting requirements changes.
MA
Maricela
1 year ago
I remember practicing a question about tracking changes, and I think the change log was the right answer there too. It’s important to keep everything documented.
MA
Mabel
1 year ago
I think the change log makes the most sense here since it tracks revisions and approvals. But I'm not entirely sure if the statement of work could also be relevant.
EA
Earlean
1 year ago
Based on the information provided, I'd say the change log is the best place for the BA to track this milestone. The question mentions the stakeholders signing off on the updated requirements, so that seems like a key change that should be documented in the change management process.
MA
Marva
1 year ago
I'm a bit confused on where exactly this should be tracked. Is the statement of work the right place, or the change log? I'll have to review the material again to make sure I understand.
TH
Theron
1 year ago
Okay, I think I've got this. The BA should track the milestone of the stakeholders signing off on the updated requirements in the change log, since that's where they're managing changes to the requirements.
EL
Ellsworth
1 year ago
Hmm, not sure about this one. Is the change log the right place to track the stakeholder sign-off on the updated requirements? I'll have to think this through.
RO
Rozella
1 year ago
This seems like a straightforward requirements management question. I'd focus on tracking the changes in the requirements documentation.
NO
Norah
1 year ago
Alright, this seems straightforward. The /etc/auto.home file is likely where the indirect maps for mounting file systems are defined, so I'll go with option A.
MI
Mila
1 year ago
Wait, are we sure the BA didn't just send the requirements to the stakeholders via carrier pigeon? Because that would be a whole different kind of milestone to track!
LU
Luis
1 year ago
I'm going with the change log. It's like a diary of all the ups and downs in the project - the BA can't afford to miss this juicy tidbit!
ED
Edelmira
1 year ago
Dorinda: It's like a roadmap of all the twists and turns in the project.
WI
Willow
1 year ago
User 3: The change log will help the BA keep track of the project's progress.
DO
Dorinda
1 year ago
User 2: Definitely, it's important to keep a record of all changes made.
TI
Timothy
1 year ago
User 1: I agree, the change log is the best place to track revisions.
CA
Carmelina
1 year ago
Hold up, what about the statement of work? Isn't that where the client and the BA agree on the project scope and deliverables? Seems like the perfect place to record this milestone.
BA
Barbra
1 year ago
Hmm, the sprint plan seems like a logical place. After all, the stakeholders have signed off on the changes, so it should be reflected in the project's roadmap.
AL
Altha
1 year ago
C) Sprint plan
LI
Lisbeth
1 year ago
B) Change log
CA
Carri
1 year ago
A) Statement of work
ST
Stephaine
2 years ago
I think the BA should track this milestone in the change log. That's where all the requirement updates and revisions are documented, right?
KR
Kristine
1 year ago
Agreed, it's important to have a clear record of all changes made.
IL
Iluminada
1 year ago
Yes, the change log is the best place to track requirement updates.
LU
Lucia
1 year ago
C) Sprint plan
MA
Marya
1 year ago
B) Change log
NO
Nohemi
1 year ago
A) Statement of work
MI
Mirta
2 years ago
I think the BA should track this milestone in the Statement of work, as it documents the overall project scope.
MA
Matthew
2 years ago
I agree with Lashon, the Change log is the best place to track this revision.
LA
Lashon
2 years ago
I think the BA should track this milestone in the Change log.