Share Product Roadmap In-app

[engineering-issue-sync-app[bot]]

Value Proposition Statement

Provide our user an easy way to interact with us on product issues and influence our product roadmap.

User Problem

Today, users have to visit Github in order to get an idea of what feature requests Camunda is working on. This mean two things:

1. Users have to leave our platform in order to see the roadmap
2. Users need to have a GitHub account in order to see and interact with us3.

This creates barriers for our users to freely interact with us on product issues and decrease the potential for feedback.

User Stories

• As a user, I can see the list of features coming in the next alpha and minor releases
• As a user I can provide feedback on individual feature/epic by leaving a comment and/or voting
• As a user, I receive a notification when a feature/epic I am following or I have participated in (voted or commented) is registering new activities (vote, comment, response from PM)
• As a Product Manager, I can publish my product roadmap within my application and update it when needed
• As a Product Manager, I can see the comments left by users and answer them
• As a Product Manager, I can easily rank the most popular features based on the votes from users

Implementation Notes

• Having a link to the GitHub board of camunda/issues is an easy way to measure how many users are interested by the product roadmap
• Using a tool like Beamer would make the implementation of this initiative relatively simple. They provide a JS snippet that can be embedded within our SaaS app to quickly and conveniently test their functionalities.
• The limitation of this implementation and service is its unavailability in Self Managed deployments.

Validation Criteria

At least 30 users have interacted with our release note or roadmap within the first month.

Breakdown

This section links to various sub-issues / -tasks contributing to respective epic phase or phase results where appropriate.

Discovery phase

Define phase

Design Planning

• Reviewed by design: {date}
• Designer assigned: {Yes, No Design Necessary, or No Designer Available}
• Assignee:
• Design Brief - {link to design brief }
• Research Brief - {link to research brief }

Design Deliverables

• {Deliverable Name} {Link to GH Issue}

Documentation Planning

Risk Management

• Assessment:
• Risk Class:

Implement phase

Validate phase

Links to additional collateral

^{:robot: This issue is automatically synced from: source}

[meyerdan]

I wonder whether we can split this in 2 parts:

• Publishing the roadmap in GH and establishing the governance processes around it
• Providing the roadmap in-app

[quentinleroy]

I have created another epic to publish Camunda Roadmap on GitHub and will be working with the Product Management team to bring it live. Thank you for the feedback @meyerdan 👍