Engineering Workflow
Welcome to the ttoss engineering workflow documentation. This workflow is specifically focused on technical implementation and software delivery, complementing the product workflow which handles strategy and feature definition.
Overview
Our engineering process is based on agility and velocity principles, as described in First, We Aim for Velocity. We use modern practices like Trunk-Based Development and Continuous Deployment to ensure fast and reliable deliveries.
Workflow Structure
1. Goals
Objectives and principles that guide our technical development process.
2. Development Process
Detailed process from task assignment to production monitoring.
Differences Between Product and Engineering Workflows
| Aspect | Product | Engineering |
|---|---|---|
| Focus | Strategy, discovery, definition | Technical implementation, delivery |
| Responsibilities | What to build, why to build | How to build, when to deliver |
| Tools | ClickUp, user research, analysis | GitHub, CI/CD, monitoring |
| Outputs | User stories, requirements, prioritization | Code, deployments, features |
| Metrics | Product KPIs, user satisfaction | Cycle time, code quality |
Integration Points
The workflows connect at specific moments:
- Task assignment: Engineering receives tasks defined by product
- Technical feedback: Engineering informs about feasibility and effort
- Delivery validation: Confirmation that product criteria were met
- Metrics monitoring: Joint tracking of KPIs
Next Steps
For developers starting the process:
- Read the Goals to understand the principles
- Study the Development Process for the complete process
- Check the onboarding documentation for initial setup
- See the technologies used in our projects
Related Links
- Product Workflow - Product development process
- Engineering Guidelines - Code standards and practices
- Onboarding - Guide for new developers
- Technologies - Technology stack used