Scrum is a rather popular approach nowadays, and its main feature is so-called sprints. Sprints are equal time periods, and usually, they last from one to four weeks. By the end of each sprint, a project team should complete a certain list of tasks.
This method looks logical, but something goes wrong in case you decide to apply it in the realities of QA automation services. The problem is that at the end of a sprint your team will have some time on manual testing, but not on developing automated tests. However, there are two ways to deal with this challenge.
