I'm not sure what you mean by setting a strategy and summary, but it sounds like you mean writing something. Strategies (and other common test artifacts) don't have to be heavy things that drag you down. If they aren't helping you do a good job testing, or release more often, I would encourage you to abandon them.
Regarding CD, not to be dismissive of your point, but releasing every two weeks isn't close to continuous delivery. This is the standard compressed waterfall interpretation of agile that many companies take. The more often you want to release software, the more crucual it becomes to have useful quality percieving activities like pairing, layering of automation, build pipeline automation, and monitoring. It also means your testers must be technical for some definition of the word technical.
To start with though, I'd encourage you to reevaluate what strategy and summaries are, and why you need to create them every two weeks.