When should you engage with the testing team on waterfall projects?
I appreciate that most software development these days is done using the 'agile methodology' or a variation thereof. With agile, the testing team is (or at least should be) heavily involved with every sprint.
However, many organisations also deliver other types of projects that don’t have a continuous development path. These are one-and-done projects like bringing in or patching a 3rd party’s software; upgrading or replacing hardware or a whole range of changes that can impact your user base.