Clip from our Intra solution menu shows you the processes. A service request is entered to our Ticket portfolio (unless we have agreed to use some other method, like your internal solution for ticket handling).
RD prioritization board members scan through these requests and information from Sales (quite often we are getting valuable hints during our discussions in webinars and demo sessions) and brings these to our biweekly meetings for evaluation. In the meeting a solution to configure the requested feature or change might be identified to resolve the issue immediately or the item might be added to RD iteration backlog for development.
RD team performs their work in 2-week Sprints, producing new Platform Release Candidates at minimum at the end of the Sprint, quite often upon request from a Customer Project Manager or Account responsible. These RC:s are tested by Product Management and Account responsible requesting the feature. A successful RC version might then be used for Customer’s proto/dev or test solution, so that the desired performance can be validated for next production upgrade.
In the next issue, I will continue to tell you a bit about how the customer solution upgrades are managed with an automated build tool and how your customer specific parts are managed during the upgrades, till next time!