Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Implementation methodologies

Updated on January 14, 2022

An implementation methodology is an adaptable process framework for managing an application development project. When you align the approach taken by your organization to the approach taken by project management with an implementation methodology, you can quickly define and implement the objectives of your application.

You reference an implementation methodology in various functionalities related to your application development, such as an estimator to size application development project, or application documentation.


The Scrum methodology takes an agile approach to development that accomplishes iterations in short cycles called sprints. When you follow this methodology, you create a product backlog that captures the planned functionality, corresponding business value, and sprint timelines for your application.

You can use Pega Agile Studio and the Agile Workbench tool to synchronize your product backlog with the bugs and stories that your team creates during application development. By using Agile Workbench, you can quickly view and analyze user stories, bugs, and feedback items that your team works on. For greater convenience, you can apply filters, and, for example, display only those items that correspond to a specific case type that you develop. You can also quickly mark items that meet acceptance criteria, to communicate project progress to other team members. To provide more information, you can conveniently take a screenshot or record a video, and then attach it to a user story, bug, or feedback item in the Agile Workbench.

Agile Workbench
A Stories tab of Agile Workbench.

Iterative Waterfall

The Iterative Waterfall methodology takes an iterative approach to development that uses the following phases: Business Value Assessment (BVA), Conception, Elaboration, Construction, and Transition.

Because the phases in this methodology are flexible, you can adapt Iterative Waterfall to fit projects of any size.

Specifications in Iterative Waterfall are commonly called use cases.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us