This requires a hybrid methodology approach often termed contractual Agile or Water-Scrum-Fall. The Business Analyst must establish a Requirements Traceability Matrix that maps high-level Waterfall deliverables to Epics while maintaining the contractual baseline. Implement a Proof of Concept phase within the design milestone to satisfy stakeholder validation needs without violating fixed-price constraints. Create a Change Control Board with strict variance thresholds and document assumptions as explicit contractual exclusions.
At a manufacturing firm, we faced exactly this conflict during a Salesforce CPQ rollout for complex configurable machinery. The $2M fixed-price contract required signed off Technical Design Documents by month two, but the sales operations team insisted they couldn't validate pricing rules without interacting with a live system. The vendor threatened invocation of penalty clauses whenever we requested scope adjustments after discovering that the Apex code couldn't handle the matrix pricing complexity originally estimated.
Solution 1: Pure Waterfall with Big Design Up Front
We considered completing exhaustive documentation before any development, creating detailed Visio process maps and UML diagrams for every pricing scenario. This approach would satisfy contractual milestones and minimize penalty risks by freezing scope early. However, the cons were severe: stakeholders couldn't visualize the UI flow, leading to 40 hours of rework per pricing rule discovered during UAT, and the business refused to sign off on theoretical designs they couldn't test.
Solution 2: Pure Agile with Contract Renegotiation
Alternatively, we could have pivoted to Scrum sprints and attempted to renegotiate the statement of work to time-and-materials. This would allow iterative prototyping with Lightning Web Components and genuine stakeholder feedback. The cons included legal impossibility—the procurement team had no authority to alter the signed contract—and the CFO's refusal to accept open-ended budget exposure given the quarter-end deadline pressures.
Solution 3: Hybrid Model with Design Prototype Milestone
We chose to bifurcate the Technical Design Document into "Static Design" (data model, integration architecture) and "Dynamic Prototype" (clickable Figma mockups with Salesforce sandbox data). We embedded a four-week Sprint Zero within the design phase, delivering working CPQ configurations for three representative product families. This satisfied the contractual obligation by delivering a detailed design specification that included functional prototypes, while maintaining the fixed-price boundary by treating the prototype as a design artifact rather than working software.
The result was successful: stakeholders validated pricing logic early, reducing UAT defects by 70%. We delivered within the 10% variance window by documenting all non-prototyped features as Phase 2 exclusions in the TDD appendix. The hybrid approach became our standard template for future fixed-price Agile engagements.
How do you prevent scope creep when stakeholders demand "just one more small feature" during prototype reviews without triggering contractual penalties?
Candidates often suggest simply saying no or immediately invoking change orders. The correct approach involves establishing a Scope Triage Protocol before any demo sessions. Categorize all requests into Defect (existing functionality not working), Clarification (ambiguous requirement interpretation), or Enhancement (new capability). Only enhancements trigger the change control process. Document everything in Confluence with decision logs attributed to specific contract clauses.
For the 10% buffer protection, maintain a Risk Reserve of story points (typically 15% of sprint capacity) specifically for Clarification work. This reserve absorbs uncertainty within budget rather than treating every discovery as scope change. Track these reserves in Jira using labels or a separate buffer epic to maintain visibility while protecting the contractual variance threshold.
What is the specific technique for mapping Waterfall BRD sections to Agile Epics without losing contractual traceability?
Many candidates suggest simply attaching the BRD to Jira tickets. This fails audit requirements. Instead, use a Bidirectional Traceability Matrix with hierarchical decomposition. Map Business Requirements to Epics, Functional Requirements to Features, and Technical Specifications to User Stories. Assign each BRD requirement a unique identifier (e.g., BRD-3.2.1) that persists through all Jira versions.
When the contract mandates a Design Specification, export the Epic descriptions, acceptance criteria, and Figma links into a formal document. Use DocuSign for signatures to maintain version control. This creates a legal artifact that references Agile work items while satisfying Waterfall documentation standards and provides auditors with the required paper trail.
How do you handle the technical discovery that Salesforce CPQ cannot support the complex pricing model assumed in the contract, when the vendor claims it's standard configuration?
Candidates often panic and suggest switching platforms or accepting defeat. The professional approach involves Technical Spike Documentation and Constraint Analysis. Immediately document the specific Apex governor limits or CPQ Quote Calculator plugin constraints preventing the solution. Create a Decision Record comparing three options: custom Lightning component development (high cost, high risk), process workaround (business impact), or third-party AppExchange solution (licensing cost).
Present this to the Change Control Board with a Business Impact Assessment showing revenue at risk if the constraint isn't addressed. If the constraint stems from a contractual assumption (e.g., system shall support unlimited tier pricing), argue that this constitutes a Cardinality Assumption violation. This reclassification potentially moves the item from scope change to contractual clarification, thereby avoiding penalties while delivering a viable technical solution.