As a dedicated Everbridge user, you may have thought of a way we can improve our product to better suit your needs. Or perhaps you’ve thought of a new direction that we could take a feature that would help a wide portion of our user base. But what happens after you submit an enhancement request?
Enhancement request evaluation process
- When a request is received, our Product Managers review it carefully while taking multiple factors into consideration. If they decide that the idea has merit and believe it will provide an improvement, they mark it as “In Consideration”.
- All accepted product enhancements are added to a backlog, where we organize features and tasks into a priority order so we can evaluate how and when to assign each task to our development teams.
- Organizing the backlog is a constant give and take where Product Managers and Engineering teams carefully evaluate tasks and features to plan product releases based on what’s happening in the market, technical innovation, customer interest, the level of effort required, concurrent development streams, and many other factors. This effort leads to the creation of a roadmap where we plan out all upcoming themes and releases.
- When an accepted enhancement request fits into a theme or aligns with our development priorities and available resources, we add the feature to a release where it becomes part of the regular product development cycle. Sometimes, even the best idea might not fit a theme or requires too much work to do properly, and it must wait for the right opening.
It’s also worth noting that accepted requests may not have the same name as the feature that makes it into the final product
Our release documentation summarizes the new features and functionality in the product but doesn’t call out specific enhancement requests or details.
Article Feedback
While we can’t respond to you directly, we’d love to know how we can improve the article.
Please sign in to leave a comment.