My boss and I had a meeting today and the topic was concerned with downtime for dev or QA. We currently work in an Agile environment. My boss wants to start working on dev for the next cycle while QA is going on for the previous sprint. His concern is that this goes against Agile convention. The compromise would be that the branches of development for the current sprint and future sprint would be kept separate. We agreed that it would behove us to reach out to the community and get feedback on the issue.

1 Answer 1


Actually, we're doing this exact thing you mention.

Testing in the same three weeks as development is nefarious for testing time and quality overall, as you seem to have experienced. So, we're testing for two or three weeks after the development sprint has finished.

By delaying testing for a few weeks, you'll be working on a fully delivered sprint contract. This is beneficial in multiple ways:

  • no useless defects are logged (as would be when the stories are only partly developed)
  • and the inverse is true: stories might impact each other. Once they're all developed, testing becomes much more interesting in terms of quality control.

Also, have a tester (or analyst) sit next to a developer and walk through the new screens or changes, before the dev sprint is done. It only takes an hour or two but gives the dev an opportunity to fix some easily spotted bugs before the actual testing round begins.

Of course, it might go against the Agile spirit, but just like the V-Model or Waterfall, it is a theory. You need to modify it to make it work in your IT department. If you all feel that the change would improve the general development and testing process, don't hesitate.

  • How do you deal with issues found during testing, are they put on the backlog? What if they block testing at all? Apr 8, 2015 at 7:02
  • Good remark. At my current client, the development team is committed to a week or two of bugfixing before they start a new sprint. And even if they've started one, higher priority bugs on new features are resolved immediately (before it's moved to production after a business acceptance test, which is the third week after development has delivered the sprint). Also, we've now started testing a bit earlier (during the development phase) due to an improved build-deploy process.
    – FDM
    Apr 8, 2015 at 7:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.