Daysha DevOps Tools Strategy
Daysha’s tools strategy is based on the DevOps Foundational model so called CALMS. Culture – agile tools vendors release features regularly and their products support flatter organisational structures that bring IT closer to the business. Jira is a good example. Automation – many tools can automate tasks but the better ones will identify opportunities to automate. XebiaLabs is a good example. Lean – tools are not bloated with useless features but do a small number of things well. Measure – tools measure as you do. If you have to stop and measure you’re losing productivity.
Share – tools have open APIs, webhooks and marketplaces. The DevOps benefit is that as data is shared all team members are aligned on the current status of work in progress.
Our partners share common characteristics of ‘download, try and buy’. The objectives with any new tools you are evaluating are: ✓ To see the value in days ✓ To be easy to learn and use ✓ To start simple and expand tool usage as required ✓ To keep workflows and automations clean and easy for others to amend ✓ To avoid automating poor process – apply lean techniques before automation ✓ To automate where a task is repeated 3 or more times per day and takes 2 or 3 minutes to perform.
✓ To integrate existing tools where possible or replace them if not
Our Atlassian Fastrack solution brings your team on a journey from current processes and tools to well implemented Jira-centric alternatives. Whether you have already downloaded and evaluated the tools or not, it is likely that you will run into the Jira Dilemma!
Jira has been designed for engineers, by engineers, which leads to: ✓ Several possible ways to implement a particular workflow ✓ Early configuration decisions which have far reaching consequences Identifying the optimal configuration is the Jira Dilemma.
Our Atlassian Certified experts apply their long years of experience to fully utilise the power of Jira, as well as recommending suitable Atlassian marketplace add-ons.
The Jira Dilemma can manifest itself at any point during your implementation and our Atlassian Fastrack is designed to set you on the right path, no matter your starting point. We work frequently with clients who encounter the Jira Dilemma after they have gone live. It is important to remember that agile teams need to be delivering features for your customers rather than learning how to be Jira experts.
Our Fastrack is designed to help you strike the right balance between knowing when to call us, and transferring just the right amount of learning to your admins.
Post Pilot Scaling
After the initial pilot it is time to consider the implementation of DevOps tools at scale.
Our Pipeline Automation provides a blueprint for the future, taking standard pipeline tools, such as our partners’ tools and CALMS compliant tools (e.g. Jenkins, Chef, Puppet Hashicorp), into account as well as your own existing tooling.
Today, many of our clients will start with a SaaS instance of Jira or Confluence. Server editions of the Atlassian products are approaching end of life and we will not be offering these products except as upgrades from Feb 1st 2021. Some Jira customisations or add-ons are available only in a server edition. If you are planning to migrate from server to cloud, contact us as we have expertise in this area.
Data Centre editions are aimed at the Enterprise, typically in excess of 2,000 users, and incorporate advanced features such as database mirroring and hot switching capability.
Local Atlassian Support
Atlassian Tools are designed to empower teams to reach their potential. They do, however, require investment in administrative overhead. At Daysha DevOps we realise that the biggest challenges Atlassian JIRA customers encounter is that they often don’t have the time, the training or the resources to perform even the smallest jobs to keep systems up-to-date and optimised for their needs. These include: ✓ Adding fields ✓ Making changes to workflows ✓ Tightening up security ✓ Managing users ✓Product Upgrades We offer a support package that has been designed to simplify the integration of Atlassian into your Software Development Lifecycle.
This means a local presence is required onsite or at the end of the phone to supplement Atlassian’s community.