By: WKFGo Editorial · ·
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.
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
Report slices in WKFGo
Primary references and verification
This list supports further verification; inline links remain the source for a specific claim.