Skip to main content

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

Designing and tracking Microjourneys development

Updated on January 3, 2022

Application development often requires the cooperation of multiple participants, such as the members of a development team and business stakeholders. A development road map and tracking system that all involved parties can understand help you deliver software that meets business requirements in the most efficient and suitable way.

Consider the following factors when you plan application development and search for the method of tracking progress:

Implementation methodology

Implementation methodology dictates how a development team plans and tracks work. The methodology also affects how the development team communicates progress to other stakeholders and how often stakeholders provide feedback on the development process. Pega Platform supports the scrum methodology as an agile approach that promotes an iterative and flexible development process.

Application development estimates

In App Studio, you can quickly and conveniently estimate the resources that the development process requires and how different factors affect the duration of the process. For shared understanding, you can export the estimates to an .xls file to share offline with stakeholders that do not have access to Pega Platform.

Feature-based application development

For more granular, scalable, and flexible application development, Pega Platform supports a development process based on features. Each feature represents a functionality that a development team needs to implement to deliver results defined with stakeholders, such as actions that users perform in a business process or elements of user interface. When you implement feature-based development, you can easily track progress by not only checking which features are done, but also by requesting a feature enhancement or a bug. Feature-driven application development is compatible with scrum and helps your development team plan and track work even more efficiently.

For example: The following figure shows a sample banking application that consists of four features:
  • case types
  • UI portals
  • language packs
  • data objects
Before the development process starts, a development team can estimate resources that implementing each feature requires. Then the team can track progress by checking which features are ready for production. Finally, feature-based development provides an option to raise issues or feedback items regarding each feature.
Application features
A figure that shows the relationship between an application and its

Start designing and tracking your application development by performing the following tasks:

  • Estimating application development

    For more accurate project planning and enhanced communication with your stakeholders, create application development time estimates. When you estimate the duration of your project, you clearly state how much time and effort your development team needs to deliver an application that reflects its specific design and required elements.

  • Adopting feature-driven development

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

  • Managing application inventory

    Plan the development of your application, manage the workload in your team, and prioritize your work accordingly by following the application backlog on your Inventory landing page. The Inventory landing page lists features, personas, and draft data associations across your Microjourney, so that your team can map items to specific releases.

  • Feature-driven development tracking

    With feature-driven development, you can create and manage stories that you associate with features to track the progress of your team. As a result, you ensure that you deliver results in a timely manner, within service-level agreements that you agree upon with stakeholders.

  • Previous topic The Microjourney in the Pega Express delivery approach FAQ
  • Next topic Estimating application development

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