The 400-Page Filing: Planning the BA Approach Under Merged Constraints

Start from what the plan must achieve, not from the CIO's template.

Drivers to weigh

• Deadline is externally fixed (regulatory filing) and therefore non-negotiable, so scope must flex rather than the date.
• Availability: two business units are unavailable for five of eight weeks; your second BA is domain-new and part-time.
• History and culture: a failed integration in which the business never owned requirements. Formality alone will not fix that; ownership mechanisms will.
• Regulatory exposure: sign-off must be evidenceable, which favours traceability over document bulk.
• Complexity and risk: two legacy billing systems, two vendors, market-operations rules.

Proposed approach

1. Iterative, not waterfall - three increments aligned to business unit. BU3 and BU4 first (available now), BU1 and BU2 later, with regulatory cross-cutting items threaded through.
2. Prioritise scope with the CIO in week one using a value/risk/effort cut, so that filing-mandatory content is guaranteed and discretionary content is explicitly droppable.
3. Deliverables: a structured, versioned requirements repository with unique identifiers, plus a concise approved summary per increment - not 400 pages at the end. A repository produces a traceable specification for the regulator more reliably than prose does.
4. Incremental approval with named business owners per increment; this is the direct remedy to the previous failure.
5. Elicitation sequencing: document analysis of existing filings and both legacy rule sets first (cheap, consumes no SME time), then 90-minute facilitated sessions for SMEs.
6. If a single end-sign-off is politically required, run it as formal ratification of already-agreed increments - the CIO gets the artefact without the schedule risk.

State the rationale for each tailoring choice in the plan. The exam rewards the reasoning, not the deliverable name.

Map first, then decide who receives scarce BA time.

Analysis

• CIO: high influence, high interest, currently negative toward any method other than a BRD. Engage closely, and frame the conversation around risk to the filing date, not methodology preference.
• BU1 and BU2 billing SMEs: high interest, low availability for five weeks, high influence over correctness. They are the schedule constraint. Negotiate named deputies and 45-minute standing slots, or accept later elicitation and place their scope later in the sequence.
• BU3 and BU4 leads: available now, high influence. Use them to validate the approach and build momentum.
• Regulator market-operations: high influence, low interest in the project, high interest in compliance. Formal, written, milestone-based engagement; do not expect dialogue.
• Vendors: medium influence, high interest. Include at design-level reviews only, after business requirements are agreed, to avoid solution-first anchoring.

Attitude, not just power and interest. A high-power sceptic cannot be managed by sending more documents. Give the CIO a decision he owns - for example, chairing the scope-prioritisation session - so the deferrals become his decisions rather than yours.

Engagement logistics for the blocked units: pre-reads one week ahead, a single decision owner per unit, agendas limited to three or four decisions, notes circulated within 24 hours, and a visible decision log so they can see their input was used.

If resistance persists, escalate as a dated risk: 'without BU1 SMEs before week 6, the filing content for billing disputes cannot be evidenced.'

Monitoring means producing evidence that the plan still fits the situation, then acting on it.

Measures worth tracking weekly

• SME attendance and hours delivered versus hours promised - the binding constraint here.
• Requirements churn: proportion of approved requirements changed after sign-off. Rising churn indicates incomplete elicitation, not a difficult business.
• Open issues and decisions outstanding, with ageing.
• Review cycle time from draft to approval.
• Ambiguity and defect rate found at review by the second BA or the vendor.
• Traceability coverage of regulatory obligations (target 100%).

Diagnose cause before responding

• If SMEs are simply absent, the plan was unrealistic. Renegotiate the sequence so BU1 and BU2 scope moves later, and record the CIO's acceptance of that risk.
• If sessions happen but requirements keep changing, the technique is wrong - likely interviewing one person instead of the group that owns the rule. Switch to facilitated workshops with the rule owners.
• If sign-offs stall, approval authority was never named. Fix decision rights, not the document.
• If the second BA is the bottleneck because she is domain-new, pair her on document analysis rather than stakeholder sessions.

Respond in the artefacts, not just in conversation: update the business analysis plan and the stakeholder engagement plan, show the revised dates against the fixed filing date, and present options with a recommendation. A plan that is never revised is not being monitored.