Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Associating project specifications with business impact and complexity

Updated on June 10, 2020

Business impact and complexity can be associated with specifications to more successfully define the scope of your project and track implementation progress against specific business objectives.

Business impact indicates the relative value achieved by implementing a specification; complexity indicates the estimated level of effort to implement the specification. You assign these criteria a value of high, medium, or low.

The Add/Edit Specification modal dialog

New fields for specifying the business impact and complexity of a specification

The Business impact optimization dashboard on the Analysis tab of the Application Profile landing page provides a visual representation of the following information:

  • Specification counts by complexity and business impact
  • Implementation progress of specifications that are linked to business objectives

You can filter the information by release and iteration.

Grid detailing counts of specifications

Specification counts by complexity and business impact

For more information, see Viewing specifications by complexity, impact, and business objective and Pega 7.1.9 Update: What's New in Project Delivery.

  • Previous topic How to manage specifications and requirements from the Application Profile landing page
  • Next topic Application specifications and requirements

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