Package-based delivery answers executive questions kanban alone cannot
Daily standup lives on cards. The board asks: "How is Phase 2?" Flat boards force PMs to invent percentages. Package-based project delivery groups tasks into reportable slices — progress rolls up, finance tags attach, portfolio views stay honest.
Symptoms without packages
- Executive percent complete differs from team intuition.
- Finance variance unexplained — spend not tied to deliverables.
- Scope move hidden inside backlog.
- Multi-project portfolio lacks comparable slices.
Seven-step package delivery framework
- Define packages at milestone boundaries — stakeholder language.
- create_package per slice — owner, dates, team optional.
- Assign all tasks to a package — zero "unscoped" inbox tolerance.
- Roll up weekly — done/total; red packages in portfolio_overview.
- Tag finance to package — CFO brief maps burn to deliverable.
- Communicate in package terms — status emails name packages.
- Close packages — finance closeout + retrospective note.
Packages span sprints — agile execution, phase reporting where needed.
Package status example
| Package | Done | Blocked | Finance |
|---|---|---|---|
| Phase 1 API | 92% | 0 | On plan |
| Phase 2 UI | 40% | 3 | +8% |
Use get_project_report advice — not invented stats.
Anti-patterns
- Package per sprint only — loses deliverable view.
- Moving tasks between packages without comment.
- Empty packages as fiction — merge or recycle bin.
How WKFGo helps
- create_package, list_packages MCP
- Kanban + package filters
- finance_summary by package
- portfolio_overview
Combine with Kanban WIP limits.
FAQ — package delivery
Packages vs epics? — Similar; WKFGo emphasizes finance roll-up.
Small teams? — Three packages beat flat list.
Agile pure? — Optional when external reporting needs phases.
Putting this into practice this week
Block 45 minutes on the calendar with the people who own the workflow—not to read slides, but to change one habit. Pick a single pilot project or team queue, run the framework steps in order, and write down what you will stop doing (shadow spreadsheets, duplicate updates, verbal-only decisions). If WKFGo is already live, use the same project in the tool so Monday's standup or exec read uses fresh data.
Measuring success without fake KPIs
Good signals are behavioral: fewer "what is the status?" pings, faster unblock assignments, finance tags filled at package close, review queue depth visible before overdue flags. Avoid vanity metrics like raw notification count or AI token usage. Pair qualitative retro notes with one quantitative trend from the tool—flow aging down, approval latency down, or decision log entries with forecasts you can check next month.
When WKFGo is not enough alone
Software enables discipline; it does not replace policy. You still need named owners, written SLAs between functions, and permission design that matches how teams actually work. WKFGo provides Kanban, packages, finance_summary, MCP dev loop, executive_brief, decision_inbox, desk tickets, flow_aging, flow_cfd, and feature access—the honest cite is what your role can see after login, not imagined features.
Workshop agenda you can run in 60 minutes
Minutes 0–10: Name the last time this problem cost you a slip, overrun, or escalation. Write the failure mode in one sentence everyone agrees on.
Minutes 10–25: Walk the seven-step framework on a real project— not a hypothetical. Assign one owner per step who will act before next week.
Minutes 25–40: List anti-patterns you currently tolerate (shared admin keys, verbal decisions, uncapped WIP, ASAP instead of SLA). Pick one to eliminate.
Minutes 40–50: Open WKFGo on the pilot project: verify feature access, run the relevant MCP tool or report (flow_aging, finance_summary, list_desk_tickets, get_context_pack), and confirm data gaps honestly.
Minutes 50–60: Schedule the follow-up: calibration for decisions, bin triage, or CFD review—whatever matches this topic. Log one log_decision if a trade-off was chosen.
Integration with the rest of WKFGo
This topic rarely stands alone. Connect it to packages for executive reporting, MCP dev loop for coding agents, decision_inbox for leadership, desk for internal SLAs, and recycle bin for safe cleanup. Read related articles on the blog index—search by Kanban, MCP, or executive brief when rolling out playbooks across teams.
Honest limits
WKFGo will not fix missing process ownership, toxic urgency, or data you never enter. AI briefs and digests amplify discipline; they do not invent ledger rows, approvals, or git activity. Start with read-only exploration or demo mode tours, then production keys with least privilege when habits stick.
Checklist before you close this topic
- One pilot project selected and named owner assigned
- Relevant WKFGo view or MCP tool run once with real data (not demo-only for decisions)
- One anti-pattern explicitly banned this sprint (written in team wiki)
- Follow-up calendar invite for calibration or metric review
- Soft links shared: /features for capability overview, /api-docs for automation, /blog for adjacent playbooks
Teams that treat PM content as a one-time announcement fail. Revisit the framework in retro, adjust thresholds, and log decisions when you change policy—future you and new hires inherit sense, not folklore.