CAPacity ALlocation & DIagrams
Note: allocation categories are generic, but generally thought of as areas like: product enhancements, reactive work, complexity management, etc)
Capaldi aims to be able to quickly answer these questions:
- Individual
- How is the individuals time committed across allocation categories?
- Team
- How are the team's resources distributed across allocation categories?
- How are the team's resources distributed across projects and releases?
- Org
- How are the org's resources distributed across allocation categories?
- How are the org's resources distributed across projects and releases?
- How are the org's resources distributed over various time intervals (e.g. quarters)?
- How are the org's resources distributed w.r.t. resource attributes such as role or FTE status?
Config:
- Jira epic query
Install sqlite, just, cargo-watch, and sqlx (w/ sqlite feature)
apt install sqlite3 libsqlite-dev
cargo install just cargo-watch
cargo install sqlx --no-default-features --features sqlite
# First time:
just db-setup
# To reset database:
just db-reset
Build
# source .env to set DATABASE_URL (used by compile time schema type checking)
source .env
cargo c
Starting capaldi dev server:
just dev-server
# in a separate console
just login
just curl /teams
Starting capaldi frontend:
cd frontend
pnpm install
cd ..
just dev-client
# Open localhost:8000 in browser
Backend (Rust):
Frontend (TypeScript):
- Svelte - Web Framework
- Bulma - CSS Framework
- Ionicons - Icons
- Svelte-query - Data Syncronization
- Axios - HTTP Client
Tool:
Design decisions are guided by a few principles:
- Outcomes before features
- Opinionated before flexible
- Simple before feature-rich
- Fast before shiny
- Delightful before powerful
While the things on the right are desirable, the things on the left take precedence.