Capacity vs Planned vs Tracked
Workload Distribution
Time Tracked by Ticket
Sprint 65 vs Historical Averages
Retrospective — We Should...
▶ Start
- Buffer SP estimates — Add 1h for deployment + 1h for bug fixes. Code-based tickets: add 3h for bug fixing. Overestimate complex tasks 2-3X.
- Test immediately — Pre-deployment (main) and post-deployment (live). PM creates Jira tickets for bugs on the spot.
- Document ticket resolutions — Comment on each ticket for future reference.
■ Stop
- Letting bugs linger — Prioritize persistent bugs, even if non-critical.
- Waiting on vendors — Escalate sooner using direct contacts or alternatives (e.g., GCP takes 1+ week to respond).
- Chasing bad tools — If it doesn't meet business objectives, drop it. Research costs/risks before committing to new vendors.
- Ignoring feasibility — Consider long-term viability and client feedback early, not after building.
✓ Keep
- Daily Slack updates — Blockers, questions, accomplishments in #app-development. Scope changes communicated immediately.
- Calls for fast alignment — Voice-first for complex discussions. Everyone jumps in to help.
- Team ticket reviews — Discuss tickets when created for alignment and accurate SP estimation.
- Share learnings immediately — Especially AI/coding best practices with the team.
Monthly Cost Overview
Variable Costs (scales with usage)
Anthropic API$120.00
OpenAI API$25.00
Variable Subtotal$145.00/mo
Fixed Overhead (same regardless of scale)
Claude Code$320.00
SendGrid$89.95
Bubble$32.00
HeyGen$29.00
Vercel$20.00
Twilio$12.00
Overhead Subtotal$502.95/mo
Total Paid$647.95/mo
Google Cloud (Covered by Credits)
GCP Credits Remaining: $17,049.15
~53 months at current usage ($320.00/mo)
Cloud Logging$140.00
Video Intelligence API$75.00
Cloud Storage$50.00
Cloud Run$25.00
Gemini API$25.00
Secret Manager$3.00
Speech API$2.00
Total GCP Usage$320.00/mo