Table of Contents

Continuous Build and Test Sprints

Continuous Build and Test Sprints

Scrum and Agile are both incremental and iterative. They are iterative in that they plan for the work of one iteration to be improved upon in subsequent iterations. They are incremental because completed work is delivered throughout the project. Iterative development is a way of breaking down the software development of a large application into smaller chunks. In iterative development, feature code is designed, developed and tested in repeated cycles.


The basic idea behind this method is to develop a system through repeated iterative cycles and in smaller incremental portions. We plan a Sprint, develop the Sprint Backlog from the Product Backlog, and develop, test, and integrate according to the Definition of Done.

Our rigorous testing practices are tailored to optimize developer and tester times:

  • We don’t need to test everything due to model driven development with Pega.
  • We test configured content; it’s not necessary for Out of Box functionality.
  • We weight testing plans by type and overall % of construction time spent in concurrent design/build/test.
  • We involve you as building happens, so you are active in defining user stories and acceptance criteria, and are truly co-producing the solution.
  • We involve testers in DCO and ‘Show and Tell’ sessions to avoid opinion based defects during latter testing stages.
  • We use Show and Tell sessions to catch errors, and have the project team run unit test and nightly regression tests to catch and fix errors as early as they occur.
  • During the build phase, we conduct different levels of regression testing and do performance testing throughout.
  • We leverage the appropriate environments depending on the nature of the test.



Traditional testing methods can take as long as or longer than the actual development cycle, and testing is usually done after development is completed. Additionally, the testing window often gets crunched or time is not allotted to fix defects so lower quality software is released. In Pega’s approach, you build working software faster, in less time and for less cost, by providing complete testing coverage, as testing is executed in every Sprint as part of the Sprint’s Definition of Done.


The Scrum team starts with a simple implementation of a subset of the software requirements and iteratively enhances the evolving versions until the full system is implemented. At each iteration, design modifications are made and new functional capabilities are added.

Suggest Edit

61% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.