Basecamp roadmap: where we are

20 weeks · 12 milestones · week 1 · the plan · Ridgeline Outfitters

“The boring half is done. The next four are the ones people feel.”

Line status week 1 plan → week 9 now

Milestones done
0 → 5
In progress
0 → 2
Weeks elapsed
0 → 9 of 20
Budget used
0% → 41%
Open risks
1 → 3
Staff on the new system daily
0 → 9 of 14
donein progressnextplanned▮ line closed = open riskshaded zone = budget used

Click a station · ride in to its platform · ← → move along the line

Stations on this line milestone · date · status

Notice board · nine weeks in

Nine weeks in, the path so far was the boring half: make the numbers agree, make the printer print. The next four milestones are the ones staff will feel — the scanner app puts Basecamp in every hand in the warehouse.

The three risks are all the same kind: a thing we do not control (a carrier key, a vendor's file format, a July holiday week). None of them moves the cutover date yet. If the scanner slips past April, it does.

Weekly review · every Monday

  1. Move each milestone to its true state; no “almost done”.
  2. Re-date anything that slipped and say why in one line.
  3. Read the risks; add a risk the moment a dependency is outside the team.
  4. Recount staff using the new system daily.
  5. Publish the map; the “you are here” marker is this week's date.

Fares phase · weeks · owner · status

PhaseWeeksOwnerStatus
Foundations1–6Priyadone
Warehouse7–12Marcusin progress
Wholesale + vendors11–16Danaplanned
Cutover17–20Priyaplanned

Service information

basecamp roadmap status          # 5 done · 2 active · 5 planned · week 9/20
basecamp roadmap risks           # 3 open, 0 blocking cutover
basecamp roadmap slip scanner +2w --why "device delivery"
exit