When faced with a tight timeline, the project sponsor suggests that the project team start development without creating traceability artifacts. What should the business analyst do?

The business analyst's primary role is to advocate for practices that ensure value delivery and project success. Traceability is a critical activity that links requirements to business objectives and solution components, managing scope and impact. When a key stakeholder suggests skipping it, the BA's first responsibility is to educate them on the value of the practice and the significant risks of omitting it, such as scope creep, gold plating, and an inability to perform effective impact analysis. This aligns with the BA's role as a trusted advisor.

A. This is a reactive and irresponsible action that accepts a high-risk practice without challenging it, failing to perform due diligence as a business analyst.
C. Negotiation is a potential next step, but it should only occur after the sponsor understands the value and risks. Explaining the "why" must come first.
D. This is the same as option A. Eliminating a core business analysis activity without explaining the consequences is a dereliction of the BA's duty.

1. Project Management Institute. (2017). The PMI Guide to Business Analysis. Section 6.1, p. 169. (Discusses the purpose and importance of traceability in ensuring requirements link to business needs and objectives).

2. Project Management Institute. (2015). Business Analysis for Practitioners: A Practice Guide. Section 5.5.1, p. 98. (Details how traceability supports impact analysis, coverage analysis, and managing requirement relationships, highlighting its value).