Like most companies we get a lot of feature requests. More often than not these come in from our Idea/Feedback portal. In this post, we pull back the product curtain to give you insight on the stages an idea goes through once it is picked up from the portal. The following is true for not just parts of a product but apply to the whole development process.
- Stage 1, Review: Once an idea is picked from the feedback page it is reviewed to see how it can benefit users.
- Stage 2, Complexity Analysis: After the benefits to users are outlined the next stage is to see the complexity to actually build the feature itself. In this stage similar ideas are reviewed, dependencies are investigated, and a final development complexity is assigned. This complexity is cross-compared to the user benefits from stage 1. If they match or the benefit is higher than the complexity then the feature can go into actual development.
- Stage 3, Pre-Alpha: In this stage the design of the feature as well as integrating and updating dependencies and a road-map are put together with time-based targets for each part of the roadmap being decided. Here is where the development actually begins. In this stage no actual testing takes place.
- Stage 4, Alpha: Alpha is where the feature is semi-built and testing has started. Most companies keep these versions internal for the simple reason that not a single bug has been fixed so it not recommended for day-to-day usage.
- Stage 5, Beta: The beta stage starts when the feature is completely built — but will still have bugs and could have a few things like poor performance. We try to open this up to the user who suggested the idea in the first place so that they can give it a shot. Smaller items are in this stage as well, such as cleaning up the look and feel; but no significant changes to the core functionality take place.
- Stage 6, RC: RC stands for Release Candidate, RC is like a beta with all the known bugs fixed and nothing critical left to be done. It is like a last stage of testing and if nothing is found it turns into a release.
Now that the feature has seen the light of day it is up for anyone to use it on QuestionPro — but it’s not the end of development. There is no such thing as perfection, but careful movement through all these stages ensure the feature comes pretty close. From this point on there will always be fixes and improvements to keep up with the changing times. This will go on till a better feature is made to replace it or the feature is not needed anymore.
Got an idea for a feature that you think should go through all these stages? Tell us right here.