Help / Workflows / Pipeline / Project Management

Project Management Workflow

Five-phase development lifecycle from planning through monitoring. Covers backlog grooming, sprint execution, code review, staged deployments to production, and continuous health monitoring of the TubeRaker infrastructure.

PLAN BUILD TEST DEPLOY MONITOR Backlog Prioritize Items Sprint Planning 2-week cycles Development Feature Branches Code Review PR + Approval QA Testing Unit + Integration Staging Pre-production Production git pull + rsync systemctl restart Health Check Uptime + Errors Metrics Performance Data PRODUCTION DEPLOYMENT SEQUENCE git pull origin > rsync deploy > systemctl restart otrotl-tuberaker > Nginx reload > Health Check Pass INFRASTRUCTURE TOPOLOGY DNS tuberaker.com AWS Proxy 3.234.160.64 VPS 51.68.198.178 Nginx :8008 App :9008 resolves proxies hosts MONITORING & FEEDBACK LOOP Health Checks HTTP 200 on /health Error Tracking 5xx / Exception logs Performance Latency + Throughput Resource Usage CPU / Memory / Disk Alert if threshold

Step-by-Step Guide

  1. Backlog Grooming

    Maintain a prioritized product backlog of features, bugs, and technical debt items. Each item is estimated, labeled, and ranked by business value and technical urgency.

  2. Sprint Planning

    Select items from the backlog for the upcoming 2-week sprint cycle. Assign story points, break large items into subtasks, and confirm team capacity and sprint goals.

  3. Development

    Engineers implement features on dedicated Git branches. Code follows the project's async FastAPI patterns with AsyncSession and await-based database operations.

  4. Code Review

    All changes go through pull request review. Reviewers check code quality, test coverage, security implications, and adherence to project patterns before approving the merge.

  5. QA Testing

    Merged code is tested with unit tests and integration tests. The QA phase validates functionality, edge cases, and regression against existing features before deployment.

  6. Staged Deployment

    Code is first deployed to staging for a final validation pass. Production deployment follows the sequence: git pull on the VPS, rsync the updated files, systemctl restart otrotl-tuberaker, and Nginx reload to apply changes.

  7. Health Check

    After deployment, automated health checks verify the application is responding correctly on port 9008 behind Nginx on port 8008. The full path is validated: tuberaker.com DNS resolves to AWS 3.234.160.64, which proxies to VPS 51.68.198.178.

  8. Metrics & Monitoring

    Continuous monitoring tracks HTTP response codes, error rates, request latency, throughput, and server resource usage (CPU, memory, disk). Alerts fire when thresholds are breached, feeding issues back into the backlog for the next sprint.