How to roll out new software release?

The delivery team (current lead: Youssef) is responsible for rollout planning, testing, and rollout. Customer Success team (current lead: Julian) is responsible for reseller/customer announcement and rollout to Customer teams.

Software Release Roadmap

The roadmap is for INTERNAL use only. Please do not share any release dates nor content with customers/resellers.

If you need to communicate content from the roadmap, always check back with your team lead. If jointly agreed, you may use a formulation like "This new feature is currently in active development". In rare cases, you might even agree to communicate a rough release date, i.e. something like "Release of this new feature likely will happen within this year".

You find the current R&D roadmap under this link. Login with password "wingtra.one". Page 1 shows the hardware roadmap, page 2 show the next software release.

Release Announcement and Rollout

4 weeks before release

Team leads Delivery team and Customer Success team discuss exact content of new release and implications for customers. Go through the internal release notes.

2 weeks before release

  • Announcement in KB with release notes
  • Newsletter to resellers and customers with release notes and what this means for customers
  • KB iteration
  • Share release notes with Customer teams

Release week

  • If significant changes for users: do a field handover day
  • Update lending shop directly after Release
  • Expect higher ticket volume for 2 weeks

Release Planning / Feature Inputs

Feature inputs from resellers and customers are tracked currently in the Product Backlog sheet (Wizard tab). This is only one source of input which will be used for prioritisation (active customer surveys, Sales inputs, partnership considerations, etc are other sources).

If you get a feature request, check the Product Backlog for a similar already present request and add the requestor to the list, which will give the feature an upvote.