Organizing a product roadmap

Cutting-edge software!

The process objective: Improve your product with new features and quickly escalate bugs.

This process covers the procedure for designing new features and improvements as well as effective bug correction in your software or on an internal application.

Requests for new features can come from:

• A specific development need
• Feature/improvement proposals
• Bug escalation

By integrating this process into Iterop, you secure the integration and prioritization of future developments. Plus, you give your non-R&D teams quick visibility of what’s happening next. For example, at Iterop, we’ve connected Iterop BPM to Slack, Jira, and Trello in order to streamline information exchange.

This process involves other subprocesses such as:

• Ticket management : It is possible to connect Iterop to other applications such as Jira. This way, your support team has its own business tool, but you and the rest of the employees have direct visibility from tracking in Iterop.
• A service request : This is a specific development request. These developments are initiated by the customer and recorded in Iterop via the consultants.
• Release process : Not launched directly, the what’s new process populates the release process with the different validated features.