5
2 Comments

Looking for best tools and advice for managing a saas product roadmap

We recently launched did.app, we think we need a roadmap.

We need a roadmap is it worth using a tool.

I found canny.io, which looks interesting. It seams nice but I wonder if it is perhaps overkill. We already have a github organisation and potentially could just use issues on one of those repo.

  • Have you used canny.io or another service?
  • Would you recommend it.

Should issues be separated from new features

We have some fairly long horizon features that we think would be valuable. For example:

Offer the same log in experience without any data being sent to our servers. The crypto capabilities in the browser make this possible and it would allow people to verify that we have no possibility of aggregating user actions.

This is obviously very different from supporting a new hashing algorithm or even just bug reports.

  • Should bugs and features be kept separate, internally we have one dev team (me) who will be working through both item?
  • Should bug trackers be made public at all.
on March 10, 2020
  1. 1

    We recently launched https://noorahq.com, which plays in the same space as Canny and other tools at the moment (our next phase we will be shifting a bit away from them...).

    However, I think the main benefit of using either Noora or Canny is that you can both communicate your roadmap, but also actually get a lot of valuable feedback from your users on what they think is most important to them - either through them voting on your posts or them making their own.

  2. 1

    I am working on the same tool (https://feedfront.me) as canny and already separated bug reports, suggestions, roadmap and changelog.

    Can you tell me what exactly you want to see in the roadmap (as in features)