How long does the capstone take?

It's a project, not a quiz, so it runs over days rather than minutes — but you're not starting cold. By the time you reach the capstone you've already built most of these artifacts inside the five modules, so this is mostly integration: making sure the stakeholder map, the requirements doc, the options analysis, the business case, the sign-off log, and the exec briefing all point at the same initiative and never contradict each other. Most people who've worked the modules need a few focused days; spread across a few sittings it becomes the week's real work rather than an exercise.

Who grades the capstone, and how?

You do, and so does anyone whose judgment you trust. Score your Initiative-in-a-Box against the master rubric in this guide, then hand the same rubric to a manager or a peer on another team and compare reads. That is the point of writing the bar down: the rubric and the traceability bar work in a one-to-one review exactly as they would in a classroom, and nothing here is scored automatically or recorded anywhere.

Do I use my own initiative or the sample brand?

Both work, and for a working BA we recommend your own. Bring a real initiative from your own organization and the capstone doubles as deployable work — you walk out with a requirements doc, a business case, and a briefing you actually send this quarter, which is day-one ROI rather than a coursework artifact. If you'd rather learn on neutral ground first, use the sample brand Mizan and Noor Al-Suwaidi's dispute-flag initiative that runs through the whole track, then redo it for your own initiative afterwards.

Do I have to do the capstone, or can I stop after the modules?

You can stop — each module stands alone and leaves you with a usable artefact. The capstone is worth doing when you suspect the pieces don't yet cohere, which is the failure the modules can't catch on their own: five deliverables that each look fine and don't add up to one system. If you can already point at the through-line running through all five, you have what the capstone was going to teach you.

Is there a certificate for this?

No. There is no certificate, no exam, and no credential — this site does not issue one, and nothing here is scored automatically or recorded anywhere. What the capstone gives you is the work itself: the finished artifact it asks for, and the rubric you scored it against. In a hiring or a budget conversation a real deliverable with real sign-offs on it does more than a badge would, because the person across the table can read it and judge the work for themselves.

Initiative-in-a-Box — the Business Analyst capstone

You have worked the five modules — the foundation of a signed-off requirements doc and a stakeholder map, a gap and options analysis, a defensible business case with a live risk register, the full requirements-to-signoff governance cycle, and the exec briefing that compresses all of it into two minutes. Each one ended with a graded artifact: a requirements doc, an options table, a business case, a sign-off log, a briefing. The capstone is where those five stop being five.

This is the integrative project. One initiative, end to end — a complete Initiative-in-a-Box where the stakeholder map names who every requirement traces to, the requirements doc is the spine everything else inherits, the options and business case are defensible on their own numbers, the sign-off log has real names against it, and the exec briefing survives a hard question because every claim on it still traces back to a named artifact. That is a higher bar than five modules completed, and it is what the track was for: someone who has actually done this is not someone who read it, but someone who ran one initiative from a messy stakeholder ask all the way to a decision, with nothing orphaned along the way.

The capstone is not five assignments stapled together. It’s one test: does every claim in the final briefing trace, unbroken, all the way back to a named stakeholder’s actual words? A reviewer should be able to pick any number on the exec briefing, walk it backward through the business case, the options analysis, and the requirements doc, and land on a real person who said a real thing. Where that chain holds, the system works. Where it breaks — a requirement with no stakeholder, a business case number with no source, a risk with no owner — the capstone flags it, because that’s exactly where a real initiative quietly goes wrong.

The brief

Produce a complete Initiative-in-a-Box for one initiative. We recommend your own — the capstone then doubles as work you were going to do anyway (see Bring your own brand) — or the sample brand Mizan, continuing Noor Al-Suwaidi’s dispute-flag initiative that runs through the whole track, if you’d rather learn on neutral ground first.

You already know the Desktop motion: open the initiative’s folder in Claude Desktop, approve each read in the “Ask permissions” prompt, and assemble the system in the chat and the file pane. No terminal on this path. Claude drafts fast and compresses well; you’re the one who chases the actual sign-off and decides what a stakeholder really meant.

Capstone deliverable — Initiative-in-a-Box (one initiative, end to end)

1. The foundation (Modules 1-2 basis)
   - stakeholder-map.md — who cares, RACI per key decision
   - requirements-doc.md — the ask, the underlying need, each
     requirement traced to a named stakeholder
   - process-map.md — the as-is process, where it breaks, who owns
     each step (if the initiative involves a broken current process)

2. The analysis (Module basis)
   - gap-analysis.md — current vs. desired state, root causes named
   - options-analysis.md — 2-4 options on one honest scorecard
   - business-case.md — costs, benefits tagged measured/estimated,
     payback
   - swot-risk-register.md — risks named, owned, mitigated

3. The governed pipeline (Module basis)
   - requirements-to-signoff.md — the sign-off log: who reviewed,
     who signed, what changed and why
   - user-story-backlog.md — stories traced to their source
     requirement (if the initiative reaches delivery)

4. The exec briefing (Module 5 basis)
   - exec-briefing.md — one page, ask-first, under 300 words
   - sources appendix — every claim on the page traced to a named
     artifact above

Bilingual teams: an authored Arabic twin of exec-briefing.md (not
translated), citing the same sources appendix.

Every piece must trace to #1. That traceability is the whole assignment.

The integration is not a formality. A reviewer will pick a number off the exec briefing and check whether it traces cleanly through the business case back to a named requirement and a named stakeholder. They will check whether every risk on the register has a real owner, not “the business” or “TBD.” They will check whether the sign-off log has actual names against actual dates, not a checklist that was never really circulated. Where the chain holds end to end, the capstone passes. Where it breaks anywhere, it’s a revise.

How it’s assessed — the master rubric

Five criteria, each scored meets / nearly / not yet. One “nearly” anywhere is a revise, not a pass — because an initiative that traces cleanly in four places and breaks in the fifth still means a decision got made on an untraceable claim, and that’s exactly the failure this whole track exists to prevent. The bar throughout is a single question: could a skeptical steering committee member pick any claim in this initiative and trace it back to a real person who said a real thing?

Master rubric — Initiative-in-a-Box
Each criterion: meets / nearly / not yet. The bar: can every claim be
traced back to a named stakeholder and a named artifact, on demand?

1. Traceability end to end
   meets Every requirement names its source stakeholder; every
            story in the backlog names its source requirement; every
            claim on the exec briefing names its source artifact. Pick
            any node in the chain and walk it both directions cleanly.
   nearly Most of the chain holds, but one or two requirements or
            claims are asserted without a named source.
   not yet Requirements, options, or briefing claims read as
            confident assertions with no stakeholder or document
            behind them.

2. The business case is defensible
   meets Every benefit is tagged measured or estimated, honestly.
            Costs and payback are shown, not just stated. The
            recommended option is the one that actually scores best
            on the options scorecard, not the one that was decided
            first and justified after.
   nearly Mostly sound, but a benefit is stated without its
            measured/estimated tag, or the recommendation doesn't
            clearly follow from the scorecard.
   not yet Numbers read as confident-sounding fiction — no tagging,
            no scorecard, no visible reasoning from data to
            recommendation.

3. Sign-off is real
   meets requirements-to-signoff.md names real people, real dates,
            and at least one real piece of feedback that changed the
            document. Nothing in the final package is asserted as
            "agreed" without a named owner's sign-off.
   nearly Most requirements are signed off, but one or two carry no
            named approver, or the log reads as pro forma.
   not yet No real sign-off log — requirements are treated as final
            without anyone's name actually on them.

4. The briefing survives scrutiny
   meets The ask leads, in one sentence. Status is stated plainly,
            including if it's bad news. The 2-3 numbers that matter
            are sourced. Risks are named without hedging. Every claim
            has a place in the sources appendix.
   nearly Mostly there, but one number is unsourced, or a risk
            reads softened rather than plainly stated.
   not yet The briefing buries the ask, hedges the risks, or asserts
            numbers with no appendix behind them.

5. Arabic quality (bilingual initiatives)
   meets The Arabic exec briefing is authored from the same
            sources, not translated from the English draft. Numbers
            stay Western numerals; both languages cite the same
            appendix and could never disagree on a figure.
   nearly Competent but translation-flavored, or a figure could
            plausibly differ between the two versions.
   not yet English run through translation. Reads foreign, or the
            Arabic version was skipped where it was called for.

Notice that four of the five criteria grade the seams between artifacts, not the quality of any single document. The modules already graded each piece on its own; the capstone grades whether the whole initiative holds together as one traceable chain from a stakeholder’s actual words to the decision a leader makes.

Bring your own brand

Use your own initiative. We recommend it for one blunt reason: the capstone stops being coursework and becomes the actual body of work you run this initiative on. The stakeholder map, the requirements doc, the business case, the sign-off log, the exec briefing — this is not a portfolio artifact, it’s the file you open on Monday to move a real decision forward. That is day-one ROI: the assessment, the portfolio piece, and the real work are the same artifact.

The sample brand Mizan is here for when neutral ground is the point — a new BA hire learning the discipline, or a practitioner who wants to practice the full chain once before running it on a live, higher-stakes initiative. It’s fully worked through every module, so you can study the moves on an initiative with no politics attached, then turn around and do it for real. Either path clears the same rubric.

What you earn

Clearing the rubric means one thing, and it is the thing worth having: proof that you can run a complete initiative on a traceable system, not just describe the individual documents.

Two honest notes about how that judgement is made:

Have a person grade it. Hand the master rubric above to someone whose judgment you trust — a manager, a peer on another team — and have them score your Initiative-in-a-Box against it and say what is weak. The rubric and the traceability bar are the useful part, and they work just as well in a one-to-one review as in a classroom.
It is not an accreditation-body badge. Its weight is the work behind it: a complete, traceable initiative that clears a professional standard. That’s a real thing to point at — and a more useful one than a quiz score.

Nothing is gated, scored automatically, or recorded anywhere. What you take away is the system you built and an honest read on where it is weak.

What good looks like

The detailed examples live in the five modules. What the capstone adds is the through-line — the same initiative visibly traceable from the first stakeholder conversation to the final briefing. Here is Noor Al-Suwaidi’s Mizan Initiative-in-a-Box at a glance, one or two lines per stage, so you can see the chain the rubric is really grading:

Mizan — Initiative-in-a-Box at a glance
(the dispute-a-charge self-serve feature, requested by Dana Al-Qassimi
after the March 1 double-billing incident)

Stakeholder map Dana Al-Qassimi (accountable), Support's Layla
                   Al-Nasser and Engineering's lead (consulted),
                   Finance's Youssef Hamdan (informed) — a RACI that
                   names who signs off before anything gets drafted.

Requirements doc The stated ask ("a self-serve dispute button") vs.
                   the underlying need ("reduce repeat billing-dispute
                   tickets and rebuild trust after March 1") — every
                   requirement traced to Dana's or Layla's own words.

Gap & options Current state: no self-serve path, all disputes hit
                   Support manually. Three options scored on one
                   scorecard; Option B (self-serve flag + triage view)
                   recommended on cost, speed, and the compliance-depth
                   priority the business case weighed explicitly.

Business case AED 62,000 cost, payback inside one quarter via
                   ticket deflection — tagged ESTIMATED, honestly,
                   since no comparable feature has shipped yet.

Sign-off log 4/4 stakeholders signed by name; one real revision
                   (Engineering and Support's escalation-routing
                   conflict, resolved and logged) — not a rubber stamp.

Exec briefing One page: the ask (approve the build) first, status
                   "at risk" stated plainly, the same numbers from the
                   business case, the same risks from the register,
                   sourced in the appendix — nothing new asserted.

Read it top to bottom and the test is obvious: the “self-serve dispute button” Dana asked for in the first conversation is the same feature the exec briefing asks her to approve six artifacts later — same scope, same numbers, same named risks, nothing invented and nothing quietly dropped along the way. That’s what “meets” on traceability and completeness looks like — not five strong documents, but one chain that holds from the first ask to the final decision.

Now ship it

You have the brief, the rubric, and the bar. The capstone isn’t harder than the modules — it’s the modules, run together for one initiative, with the seams made to hold. Pick the initiative, open the folder, and assemble the system Claude drafted and you decided.

One thing to keep beside you as you build: the Business Analyst operating guide — the data-handling and sign-off discipline that belongs underneath a BA putting real stakeholder conversations, requirements, and business cases through Claude, especially where those conversations carry HR, legal, or customer-sensitive detail that never belongs in the chat unredacted.

Build the chain and clear the rubric. The traceability is the point — and the traceability is what you keep.