In this talk, I will speak about Lean projects only:
The business goal is clear, but the ways of achieving it aren’t. Some hypotheses can only be tested practically.
Requirements change frequently. A feature added last week can be removed this week.
The more often the releases, the better.
How is this kind of project different for a tester? Why are frequent releases a feature too? Why can’t a team of 4 developers and 1 tester go without autotests?
Our company has implemented dozens of such projects, and here’s what we found. If you want to release more often, you have to pay. The price is either increasing the testing team, or loss of quality, or investing in test automation.