How Do You Balance QA and Development Speed?

Your approach sounds solid! I've worked with several models across different teams, and I've found that prioritizing a design-first strategy often leads to better outcomes. It's crucial for QA to engage early to catch issues before dev starts. Just remember to push back against the folks who insist on being 'agile' for the sake of it; they might overlook the foundational work that QA provides.

That's an interesting question! For greenfield projects, whether building everything from scratch or just launching a new feature within an existing setup, our model remains flexible. We focus on getting QA involved early to prevent rework later. I'd love to know more about what you're defining as 'greenfield'—are you talking about new infrastructure, or just new features?

I appreciate you asking that! In my experience, we not only write test plans during our research phase but our QA team also gets involved before the devs release anything. They create test runs and cases, plus identify what can be automated. Sure, it leads to some inefficiencies—like being out of sync for a sprint—but those last couple of sprints are crucial for getting everything lined up for the next version.