A strategy defines the approach and steps to be taken in order to deliver the set objectives. In other words, whereas the objectives define the what, the strategy defines the how. The scope of the strategy should go well beyond technology and also cover architectural (for example, overarching architectural principles, reference architectures, and capability models), organizational (people, roles, and responsibilities) and process-related (software development life cycle, continuous delivery, and so on.) concerns. It should also aim to align with other initiatives and identify key dependencies that may alter the timelines and/or order of delivery.
As with everything, there are no silver bullets, so there are no exceptions ...
