Adopting feature-driven development
Develop capabilities in the context of a feature to maintain functional requirements and project status directly in your application.
- 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 meet your specific business needs and customer expectations, by creating features. When you create features, you communicate what elements your development team needs to implement to deliver a complete application, so that you can appropriately plan your work and inform stakeholders about your application design.
- 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.
- 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.
- 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.
- Collaborating with development teams
Improve and accelerate your project delivery by collaborating with development teams by using Pulse. When you post Pulse messages, you ensure that team members have up-to-date and relevant information about the features that they implement.
- 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.
Previous topic Engaging with stakeholders to define a Microjourney Next topic Feature order