1. Courses
  2. Business Analysis
  3. Capstone

Capstone project for Business Analysis

Move phone orders into the Partner app

About 4,000 partner orders a week reach Mangrove Market, and about 1,500 of them still come by phone to 40 sales reps, who write them down and re-key them into the back office at the end of the day. About 1 phone order in 12 is corrected after delivery, at about $9 a correction, and the head of partner sales wants the app's share to rise from 62% to 75% within a year. Lagoon Digital, the agency that builds the Partner app, is waiting for a backlog. Produce the analysis pack the team needs: measure the problem, plan how you will work with shop owners, reps, finance, the distribution centres and Lagoon, find out why shops still phone, model the ordering process today and after the change, write the requirements and business rules (credit limits, the 6 pm cut-off, pack sizes), turn them into a backlog of user stories with acceptance criteria, and show how every requirement traces to a need and a test, with a UAT plan for a pilot with 20 shops.

What you hand in

  1. A one-page problem statement with today's numbers and two to four measurable objectives
  2. A stakeholder map with an engagement plan, and an elicitation summary that names the evidence behind each finding
  3. Current-state and future-state BPMN models of partner ordering, with the waste you found and how the future state removes it
  4. A requirements list with IDs (business, functional, non-functional, transition), the business rules as decision tables and a short data dictionary
  5. A backlog of 12 to 20 user stories with Given/When/Then acceptance criteria and a story map showing the first release
  6. A traceability matrix from objectives to requirements, stories and tests, and a UAT plan with entry and exit criteria

Check your work

Tick each item when your project meets it. Be strict: this is the rubric the reviewer uses.

  • The problem statement is measured: today's phone share, corrections and their cost come from data, and the objectives are numbers with dates
  • Findings about why shops phone come from evidence (interviews, observation, data), each with its source, not from assumptions
  • The BPMN models are correct and readable: pools and lanes, one start event, labelled gateways, message flows between organisations, and the future state removes named waste
  • Requirements are atomic and testable, non-functional requirements have measures, and business rules sit apart from the requirements that use them
  • Stories are small, valuable and testable, split by workflow, rule or data, and their acceptance criteria cover the edge cases (over the credit limit, after cut-off, offline, case versus unit)
  • Every requirement traces back to an objective or need and forward to at least one test, and gaps in the matrix are called out
  • The UAT plan names real testers, scenarios from the future process, defect severities and exit criteria that decide sign-off

0 of 7 checked

Model answer

The model answer opens once your capstone passes the review, so you can compare your work with an outline of a strong submission.

Hand in your capstone

Your links are checked automatically, then the work is scored against the rubric above, item by item, with comments. A pass counts toward the course certificate and shows on your profile.

Loading…