I have formed a new QA team in a company that has been developing code for several years. We now have members of QA in all teams. The problem we seem to be having is that tickets from the developers are coming over late in the sprint and not giving the testers enough time to test. The long term goal would be bolster the automation tests we have and have QA test stuff before it gets merged in to develop and deployed to staging so we know the stuff deployed to staging has at least had some testing but for now we need a solution for the time being.
In previous projects I made sure that high risk tickets came over early in the sprint and no big tickets came through on the last day of the sprint and only minor changes happened on the last day so QA can close off the sprint. This seemed to work quite well
My feeling is that in my current company the development team is not used to having a tester in their team and are used to developing till the absolute deadline.
Is there anything else the QA team could do to limit the spike at the end of the sprint?