How do software developers organise updates for their law firm software? And how do they communicate new features to clients and internally? These were two of the topics covered in the latest TaxTech roundtable, which the hosts Paul Liese from hsp and Philip Hellmig from kanzlei.land discussed yesterday during the Wednesday Talk. They also addressed the question of who tests the features and how this is done before they are rolled out.

Although all six participants in the roundtable use different methods to organise software updates, they agreed that standardisation is absolutely essential to optimise the processes. Software manufacturers use the Scrum approach, organised into sprints, to manage releases. Updates are released at intervals ranging from two weeks to three months.

The panellists identified key differences in how the new version is communicated. Whilst some use newsletters to reach out to partners, customers and consultants, others also rely on release notes via the support portal, app notifications, pop-up windows when logging into the software, and weekly or monthly Q&A sessions streamed online. Work is also already underway on push notifications that inform users of new updates on their smartphones.

Technical jargon must be conveyed in a way that everyone can understand

The group also agreed that communication with their own staff must not be neglected. The benefits of the new features must be conveyed in a way that is understandable to everyone, translating them from developer jargon. After all, it is ultimately the sales team that has to convey this message to customers. Most rely on internal channels such as the intranet – often with the help of in-house video tutorials.

The taxtech.online logo

When asked about the testing process prior to the roll-out of the update, it became clear that two- or three-stage testing procedures are used. At all the software manufacturers in the group, software developers carry out module tests, which are then checked manually once more. By employing additional staff who focus solely on testing, the time taken to approve a release can be significantly reduced.

Updates involving test customers are also an option. This allows the features to be used in real-world conditions and developed specifically to meet customer requirements. The advantage of this is that users with a specific need contribute to the funding of the development. As these are genuine enquiries, it also reduces the risk of developing a product that ends up gathering dust on the shelf.

However, with this approach, some of the participants fear that niche products will emerge and that the company’s visionary strategy will be curtailed. It is also worth going against the grain for a change, even if securing funding is more difficult.

Another point of discussion during the meeting was which features should actually be implemented. In this regard, the software manufacturers rely on an internal evaluation system in which all product requirements are collated and categorised. Priorities are then set in collaboration with the sales department, depending on the potential of each feature.

At the end of the discussion, everyone agreed that processes for software updates should be standardised as far as possible in order to facilitate both external and internal communication.

Software development isn’t something that just happens overnight; a great deal goes into ensuring that users can benefit from high-quality software. A lot is being set in motion to achieve this. You can help shape this development first-hand. Join us as a guest at the next TaxTech session on 28 April 2021 at 5 pm.
Bookmark this link now: www.taxtech.de