Business Analysis by the Numbers: Stakeholder Grids, RACI Checks, Elicitation Plans, Requirement Quality, MoSCoW Capacity, Objective Traceability, Process Gaps & the Business Case

What you'll build

What you will be able to do

Each lab ends with a concrete result that you build yourself and the checker confirms, cell by cell.

• Score twelve stakeholders of a portal project on power and interest, sort each into a quadrant with IFS, count the quadrants with COUNTIFS and draw the power/interest grid as a scatter chart.
• Check a ten-task RACI matrix with COUNTIF: one A per task, at least one R, a status flag with IFS and the R + A workload of each role against a fictional team limit.
• Turn a plan of interviews, workshops and surveys into analyst hours including preparation and write-up, check that every stakeholder group is covered and find the last elicitation day with ROUNDUP and WORKDAY.
• Check 30 fictional portal requirements: count vague words with IFERROR(FIND(…)), measure the share without acceptance criteria, give each requirement a quality score and count the ones that are ready to build.
• Check the Must share of a release against a fictional 60 % team rule, find how many Must days have to be renegotiated and draw the cut line with a running total of effort.
• Trace 16 requirements to five business objectives: count orphan requirements, build a small trace matrix, measure how many objectives are covered and how many person-days go into requirements that serve no objective.
• Cost a fictional order process before and after the portal: count hand-offs, price each order including rework, turn the difference into yearly savings and find the step with the biggest gap.
• Build the portal's five-year business case from one-off cost, running cost and the savings of lab 7, discount it with NPV, judge three change requests on payback and go-live date and chart costs against benefits.