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.

Adopting feature-driven development

Updated on April 5, 2022

Develop capabilities in the context of a feature to maintain functional requirements and project status directly in your application.

Before you begin: Ensure that you have the PegaRULES:AgileWorkbench access role and the pxAgileWorkbench privilege.
As a best practice, use Agile Workbench to manage feature-driven development because work items provide traceability from features to the rules that support them.
  • Learning about feature order

    To understand the importance of the features in your application, look at the order in which your application lists features. Your application lists features in order of relevance to the current implementation, with the oldest features at the top by default.

  • Creating features

    Ensure that your application supports capabilities that meets your specific business needs and customer expectations, by creating features. When you create features, you communicate a design of your application to stakeholders and development teams.

  • Creating subfeatures

    Provide more advanced and varied solutions in your application by enhancing application features with subfeatures. Create a subfeature to define a capability that extends another capability.

  • Tracking feature-driven development

    Create and manage stories to track the progress of your feature-driven development.

  • Collaborating with development teams

    Improve and accelerate your project delivery by collaborating with development teams. When you post Pulse messages, you ensure that team members have up-to-date and relevant information about the features that they work on.

  • Integrating Agile Workbench with Jira in Pega Platform from 8.3.x

    Capture real-time feedback about an application development project directly in the application with the Agile Workbench tool. By using the Atlassian Jira component that is available from Marketplace, you can continue to use a real-time Agile methodology and integrate Agile Workbench with Jira to take advantage of its project management features, such as project and issue tracking, Scrum and Kanban support, backlog prioritization, and sprint planning.

  • Integrating Agile Workbench with Jira in Pega Platform 8.1.x to 8.2.x

    Capture real-time feedback about an application development project directly in the application with the Agile Workbench tool. By using the Atlassian Jira component that is available from Marketplace, you can continue to use a real-time Agile methodology and integrate Agile Workbench with Jira to take advantage of its project management features, such as project and issue tracking, Scrum and Kanban support, backlog prioritization, and sprint planning.

  • Integrating Agile Workbench with Jira in Pega Platform 7.3.x to 7.4.x

    Capture real-time feedback about an application development project directly in the application with the Agile Workbench tool. By using the Atlassian Jira component that is available from Marketplace, you can continue to use a real-time Agile methodology and integrate Agile Workbench with Jira to take advantage of its project management features, such as project and issue tracking, Scrum and Kanban support, backlog prioritization, and sprint planning.

  • Creating a specification

    Defining and creating specifications for an application is an iterative process that requires input from all stakeholders. If the information about a specification is detailed and up-to-date, the specification is more useful during the application development process.

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