Embedded Files
It's been almost a quarter of a century since Mike Cannon-Brookes and Scott Farquhar released Jira 1.0 into the world, and the world has changed dramatically in that time. Ways of working have matured, the nature of most business has changed dramatically, and the Atlassian stack itself is a completely different beast.
With Atlassian tooling having such a long and storied history, it's fairly typical for companies to have Atlassian suites which were founded years, or even decades, ago. These platforms will have been originally designed to support a completely different business to that which exists today, and in many cases the various reconfigurations over those years have built up extreme technical debt and resulted in a system which gets in the way of operations, rather than supports them.
The team at Echidna Solutions have decades of experience in helping businesses to take a step back from their current implementations, review their systems as a holistic whole, and refresh their platforms to truly support today's need. If you find yourself in a similar situation, contact Echidna Solutions to discuss your current estate, and help to plan your next steps.
How did this all start?
How did this all start?
A few years ago, when the deprecation of Server was first announced, and people started to migrate from Server to Cloud en masse, the team at Echidna Solutions realised that many of our customers were working with systems that were no longer truly fit-for-purpose. Many platforms at this point had a decade of history and technical debt, and were as often worked around as worked on. With this realisation, the team helped our customers to clean up this history, and focus on supporting the business practices of today rather than those of a decade ago, as part of their Atlassian Cloud Migration process.
Many customers, however, were suffering from the same issue, but didn't have a migration process to hang the cleanup onto. This presents an interesting challenge, as a migration process provides the unique opportunity to leave behind elements of techincal debt, while remaining on the same platform requires careful extraction of these elements.
How does Echidna Solutions approach this then?
How does Echidna Solutions approach this then?
Similarly to other engagement types, and as detailed in the Atlassian Implementation section of the site, it is imperative that one builds up a deep understanding of the current business and technical state of the customer prior to designing an ideal future state. An Analysis and Design engagement is typically used to facilitate this process, ensuring full understanding of the situation at-hand, as well as reducing change management overhead through engaging with teams and encouraging early buy-in on the process.
As for the technical approach used - this can vary from case to case. In some cases, impementation of new plugins, automations or integrations is performed prior to migration of existing processes onto them, deprecating old methods. In others, taking a cue from the success of migration processes is ideal, resulting in a fresh platform build being produced, that teams are migrated across to. In any case, the customer is involved every step of the way, and the costs and benefits of all options are fully discussed prior to proceeding.
If you'd like to discuss your own unique situation, please contact Echidna Solutions today.
Page updated
Report abuse