The development team are constantly working to evolve Mercury, keeping it relevant and up to date with the latest features, integrations and enhancements.
So how do you stay up to date with the latest in Mercury Development?
Monthly 30/30 Mercury Update
In today's world, technology is constantly evolving and at a steadily increasing rate. This means that Development pipelines must be agile in order to be flexible when change occurs.
The Monthly 30/30 provides that much needed insight into the future development plans of Mercury, whilst still maintaining the flexibility required to remain relevant with the ever changing face of technology.
Introduced in early 2018, the concept of the 30/30 is simple:
A recap of what the Development team have been working on in the last 30 days, followed by a rundown of what the team is planning to focus on in the next 30 days.
The development team work on fortnightly sprints, and some features can take multiple sprints to complete. Whilst we provide a run down of the smaller features and improvements we have delivered, the major features, integrations and improvements will often span over multiple installments of the 30/30 update.
All 30/30 Updates are kept on the wiki under Mercury>30/30 Mercury Updates.
The development team run on a fortnightly sprint. This means that they commit to an amount of work they are going to produce over a 2 week period. At the end of that period, the work is released into the production (live) version of Mercury.
This means that releases also occur every two weeks, on a Monday, and release notes are published on the wiki under Mercury>Release notes on the same day.
The Mercury Release notes provide an update on the latest features and improvements released at the end of the previous sprint.