2.X.1 Professional Project Management for All
Crafting the MVC – Minimum Viable Company
- “A temporary endeavor undertaken to create a unique product, service, or result.”
Why Project Management at Level 2?
Because you’re building your operational backbone — for the first time.
You’ve entered the Craftsman Era — not unlike the early days of human innovation. Nothing is standardized yet. You’re hand-building everything. One project at a time. One decision at a time. You’re shaping your company the same way an artisan once shaped tools from stone: with intent, grit, and raw focus.
In Level 1, your product was the obsession — built in your image, through sleepless nights, chaos, and sheer force of will.
But the product isn’t the only thing. Now, the company is your focus.
It’s time to build your MVC — Minimum Viable Company — with the same intentionality and pride.
Project Management is your structure for figuring things out professionally. It teaches you how to plan, test, adapt, and finish what you start — while keeping your team aligned and your costs under control.
The skills and execution discipline you and your team learn here will carry forward into every phase of your company — and every company you ever build again.
If you can’t build the company with this level of care and clarity… no one else will.
Project Management Components (minimum)
The 5 Phases of Every Project
Each component above should be monitored and adjusted like a good financial forecast — original plan → actuals → updated forecast → variance.
You used projects to build your MVP. Now use them to build your MVC — the Minimum Viable Company.
Choosing Your Product Methodology
Waterfall vs. Agile – Two Paths, Same Core Disciplines.
The fundamentals of project management — scope, schedule, budget, quality, risk — apply regardless of method. What changes is how you structure the work and learn along the way.
Waterfall Project Methodology
(follows the basic PMI playbook above)
- Complete the requirements
- Then the design
- Then implementation
- Then verification/testing
- Then final delivery
Agile Project Methodology
Iterative approach where each phase is part of a sprint.
2.X.1.16 Agile Method
2.X.1.17 Base PMI Method compared to Agile by Component
Agile breaks the work into short sprints (usually 2–4 weeks), with a cross-functional team delivering a working component at the end of each sprint. After each sprint, the team holds a retrospective to reflect and improve the next sprint. Future sprints pull the work from a prioritized backlog of all features/tasks. It can be modified as new insights emerge.
This is ideal for fast-moving markets (like software, DTC, or SaaS), where customer needs evolve and learning quickly is the advantage.
Connecting Project KPIs to your Dashboard
(this works the same with EOS Scorecards and Level 10 Meetings)
Why It Matters
Execution should produce insight. Don’t just finish tasks — harvest operational intelligence that feeds the business.
KPI Mapping Example
| Project KPI | MVC Metric | EOS Scorecard |
|---|---|---|
| % On-Time Tasks | Schedule Reliability | On-Time % |
| Budget vs Actual | Burn Rate | Weekly Spend Variance |
| Bugs per Sprint | Quality Signal | Defects Escaped to Prod |
| Velocity | Throughput | Story Points per Sprint |
| Open Risks | Risk Register | # Active Risks |
| Stakeholder Feedback | NPS / Customer Score | Issues Raised / Resolved |
How to Use This
- Pick 8–10 MVC metrics that matter most
- Map your project-level KPIs to dashboard fields
- Update management at the weekly management or Level 10 EOS meeting
- Use visuals to track variance and trends
If your execution KPIs are off... your projects are warning you. This is how small teams become great companies — by learning from the work they’re doing in real time.
Bottom Line:
Agile is often the better fit for startups — but both methods are valid. What matters most is that your team learns to document and manage work, time, and outcomes with intent.
Whether you’re sprinting or stair-stepping, project management teaches you how to plan, execute, and adjust — so deliverables meet expectations.