Engineering Org Structures— The QRF Team Model
Take control of engineering team interruptions and prevent them from happening ever again
As an engineering leader, I’ve found many products and engineering teams at startups struggle with being agile.
The shortcuts the startup took early on getting to the point where they could grow had benefits, but also costs. At some point, enough technical, capability, knowledge, and organizational debt has been created such that there is a constant stream of bugs, internal asks, interruptions that only the engineering team can handle.
These ask come in at a rapid pace, sometimes several days, greatly disrupting the work of an engineer. Even if each interruption only takes a few minutes, the context switch alone can destroy any hope of productivity for that afternoon.
How can an organization handle these in a way that makes sense?
Enter the QRF Team
The QRF model works incredibly well in certain contexts without the negative drawbacks of other approaches.
What is it?
You split your engineering organizational unit into two discrete, independent teams:
- Team 1, designated as the Main Effort
