1. Courses
  2. Strategy, Priorities & Roadmaps
  3. Capstone

Capstone project for Strategy, Priorities & Roadmaps

Planning season for the Store app

It is planning season at Mangrove Market. Department heads have sent Imran 18 requests for the Store app, from planogram photo checks and damaged-stock photos to staff shift scheduling, and the managing director wants a plan for the year in three weeks. Start from the requests in the lessons (the five in pm-12 and the store items among the 16 in pm-13) and add your own to reach 18, writing realistic estimates where the course gives none and saying so. Write a one-page strategy for the Store app and two or three outcome OKRs for the first quarter. Score and rank the 18 requests with RICE, check timing with cost of delay, and name the two scores you trust least and why. Lay out a Now/Next/Later outcome roadmap for a team of six engineers that reserves capacity for tech debt and keep-the-lights-on work. Finally, for staff scheduling, compare the five-year total cost of buying a SaaS scheduling tool, extending the Store app, and partnering with the HR system's vendor for its scheduling module, and recommend one with the contract terms you would insist on.

What you hand in

  1. A one-page strategy: a diagnosis with numbers, a guiding policy with three requests it rules out, coherent actions and why now
  2. First-quarter OKRs: one objective, two or three key results with baselines, targets, sources and owners, and two to four guardrails
  3. A scored backlog of 18 requests with the units and Impact anchors stated, a cost-of-delay check on the top items, a decision log and one written 'no'
  4. A one-page Now/Next/Later outcome roadmap with metrics, dependencies with needed-by dates, and the capacity split
  5. A build, buy or partner memo for staff scheduling: five-year TCO, adjustments for time to value and team time, the number that flips the decision, a contract checklist and an exit plan

Check your work

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

  • The diagnosis names one main obstacle with evidence, and the guiding policy rules out real requests
  • Every key result measures an outcome or impact, with a measured baseline, a source, and a guardrail that answers 'how could we hit this the wrong way?'
  • RICE uses one Reach unit, anchored Impact, and effort that includes testing and rollout, and you name the two scores you trust least
  • Scores within about 20% of each other are treated as ties and decided on strategy, dependencies or risk
  • The roadmap has three or four outcomes, not a feature list, and says where every other request went
  • KTLO is budgeted from a stated actual, and tech debt items are named and tied to the outcomes they unlock
  • The TCO uses the same five-year horizon for every option, includes internal time and price rises, and names the number that would flip the decision
  • The contract checklist covers scope and acceptance, SLA, data ownership and export, change requests, price caps and exit

0 of 8 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…