XebiaLabs Licenses

Daysha DevOps are XebiaLabs Implementation Partners

Xebialabs Licenses

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.

Partner Selection


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

Tools Evaluations


Our Automated Pipeline solution is the optimal way to determine if a XebiaLabs investment can offer value beyond your current investments in release and deployment automation. We focus on two areas to augment the XebiaLabs feature-set: process and team organisation.

As you evolve, your DevOps teams need pipelines they can support at Level 1, in order to ensure code deploys. Your Site Reliability Engineering (SRE) teams are now tasked with Level 2 and 3 fixes. Who builds these pipelines in the first instance is of course a key decision, which the Automated Pipeline solution can help you identify.

Scaling


It is important to look beyond a first implementation and how your organisation will integrate with existing tools, such as Jenkins, Jira and Git, or whichever source control tools are in use. You may have addressed some of these during your pilot but as the number of pipelines grows the integrations may require further engineering effort.

Your organisation may also need to skill up SRE teams or Operations teams in a broader context. We recommend training on both core product functionality and best practice.

If you are forming and storming your teams our DevOps Foundation or DevOps Simulation can be a good start.

Take Action

Initiate tool changes with our with Automated Pipeline

Establish your tools strategy in conjunction with process, team organisation and new ways of working.

SCHEDULE CALL