Skip to main content


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

Sizing an application development project

Updated on November 15, 2021

Estimate the time and effort that you need to build an application to quickly allocate and schedule resources before you begin development.

Note: To take advantage of low-code solutions that Pega Platform offers, switch to App Studio to estimate your project in a convenient and low-code way. For more information, see Estimating application development.
  1. In the header of Dev Studio, click ConfigureApplicationToolsSizing.
  2. In the Application list, select the name of your application.
  3. In the Implementation methodology list, select an option that describes your process for application development.
    Caution: Ensure that the methodology that you select is correct, because the project sizing tool that you generate is not compatible with other methodology types.
  4. Optional: To control which items are included in the project sizing tool, provide filter criteria.
    • To filter specifications by event:

      1. In the Included specifications list, select a type of action.

        For example, you can find specifications based on the time that they were created.

      2. In the Date field, enter a calendar date that your application evaluates to include specifications in the project sizing tool.

    • To filter specifications by category:

      1. In the Case types and supporting specification categories section, click Make selection.

      2. Select the check box next to a category name to include specifications with this category type in the project sizing tool.

      3. Click Submit.

    • To filter specifications by status:

      1. In the Specification status section, click Make selection.

      2. Select the check box next to a status name to include specifications with this status type in the project sizing tool.

      3. Click Submit.

    • To filter case types by name:

      1. In the Case types and supporting specification categories section, click Make selection.

      2. Clear the check box next to a case type to exclude it from the project sizing tool.

        By default, all case types are selected.

      3. Click Submit.

  5. Save your settings so that you can reuse your filter criteria in future iterations.
    1. Click Save.
    2. In the Save Sizing settings dialog box, enter text in the Name field that distinguishes your settings from other settings for this application.
    3. Click Submit.
  6. Click Create project sizing, to generate and download a Microsoft Excel file that contains the project sizing tool.
  7. Create estimates for your project.
    1. Open the file that contains the project sizing tool.
    2. Provide information about your application in relevant cells, by consulting project stakeholders or the contextual help for each worksheet in the tool.

      For example, you can define specifications, identify the type and complexity of each interface, or override projected hours or productivity rates.

      For more information about the formulas and options that you can use, contact your lead architect or account executive.

    3. In the Sizing wizard, click Attach project sizing to application.
    4. Click Choose File.
    5. Navigate to the directory of the file that contains the project sizing tool, and then click Open.
    6. In the Attach Project Sizing dialog box, click Submit.
  8. Distribute your estimates to stakeholders for review.
Result:

The timeline from your estimates is included in application profile documents that you generate. You can generate and attach new estimates to your application as your project matures.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us