

Official logo of Basque Country's public health care service: Osak

256_cta-background.webp

384_cta-background.webp

640_cta-background.webp

750_cta-background.webp

828_cta-background.webp

thumbnail_cta-background.webp

osakidetza-logo

Daar hebben wij de oplossing voor

Wilt u efficiënter werken? 



Atmosphere of azure electric sky, with water, slope,

1080_background.webp

1200_background.webp

256_background.webp

384_background.webp

640_background.webp

750_background.webp

828_background.webp

thumbnail_background.webp

atmosphere-water-sky-azure-electricity-astronomical-object-slope-electric-blue

INNOVATIE DOOR SOFTWARE: LEAN, CLOUD, DELIVERY

SOFTWARE, CLOUD

1080_zen-logo-white.webp

1200_zen-logo-white.webp

256_zen-logo-white.webp

384_zen-logo-white.webp

640_zen-logo-white.webp

750_zen-logo-white.webp

828_zen-logo-white.webp

thumbnail_zen-logo-white.webp

zen-logo-white.webp

ZEN Software

1080_zen-logo-black.webp

1200_zen-logo-black.webp

256_zen-logo-black.webp

384_zen-logo-black.webp

640_zen-logo-black.webp

750_zen-logo-black.webp

828_zen-logo-black.webp

thumbnail_zen-logo-black.webp

západoslovenská energetika-logo

Agile Analytics

Ontzorgde Softwareontwikkeling

Tech Consultancy

ZEN DevOps Accelerator

Content and Commerce at any scale

ZEN Cloud Landing Zone

Onze Diensten

Over ons

Nieuws

Contact

Succes! Je bent toegevoegd aan onze e-maillijst.

Abonneer u op onze e-maillijst en we houden u op de hoogte van nieuws en publicaties van ZEN Software

Subscribe to ZEN Software's  newsletter



Modern desk, perfect for home office setup with computer, monitor and keyboard

1080_image-20220407-100918.webp

256_image-20220407-100918.webp

384_image-20220407-100918.webp

640_image-20220407-100918.webp

750_image-20220407-100918.webp

828_image-20220407-100918.webp

thumbnail_image-20220407-100918.webp

computer-table-personal-computer-furniture-computer-keyboard-desk-computer-monitor-computer-desk

Gegarandeerd verbeterde prestaties van de softwarelevering en een effectievere softwareorganisatie



Tools of the trade: "AXILO" wrench set for metal

256_unsplash_t5YUoHW6zRo.webp

384_unsplash_t5YUoHW6zRo.webp

thumbnail_unsplash_t5YUoHW6zRo.webp

hand-tool-metalworking-hand-tool-tool-wrench-set-tool-ratchet-service-font

Het ontwikkelen van software vereist een degelijke basis van tools, platformen en omgevingen om veilige builds mogelijk te maken, samenwerking en hosting van de applicaties in productie- en testomgevingen mogelijk te maken.

In de meeste organisaties zijn er echter uitdagingen met de afstemming tussen "traditionele operaties" en "traditionele ontwikkeling" gerichte teams. ZEN Software DevOps Accelerator bevindt zich op het middelpunt van Cloud infrastructuur en softwareontwikkeling. ZEN DevOps Accelerator stelt DevOps-teams in staat zeer productief en autonoom te zijn.

Veel Tools

Tools



Aquatic rect. w/mag. logo & electr. blue

1080_Rectangle-27.webp

1200_Rectangle-27.webp

256_Rectangle-27.webp

384_Rectangle-27.webp

640_Rectangle-27.webp

750_Rectangle-27.webp

828_Rectangle-27.webp

thumbnail_Rectangle-27.webp

rectangle-aqua-font-electric-blue-pattern-magenta-logo-event

ZEN Software DevOps Accelerator zorgt voor een veilige bouwomgeving, leveringspijplijnen en een hyperschaal productieplatform. Als gevolg hiervan zal ZEN DevOps Accelerator de impact van de softwareontwikkeling van uw organisatie verbeteren!

Single Pane of Glass

Single Touchpoint

Single Sign On (SSO)

Centralised Developer eXperience (DX)

Een dergelijk geïntegreerd bezorgplatform heeft de volgende aspecten:

ZEN Software is met tientallen jaren ervaring in softwareontwikkeling een toonaangevende expert op het gebied van Software Delivery-oplossingen. Met behulp van ZEN Software DevOps Accelerator kunnen we verbeterde prestaties van de softwarelevering en een effectievere softwareorganisatie garanderen. We onderzochten en ontdekten dat effectieve softwareorganisaties één ding gemeen hebben. Deze organisaties hebben een geïntegreerd software delivery platform om effectief te worden en te blijven.

Effectievere softwareontwikkeling voor alle organisaties



French TV network's official logo: "France 3 Aquitaine".

france 3 aquitaine-logo

**Een Developer Portal centraal voor alle services die uw DevOps-teams nodig hebben**

**Single Sign On integration met Multi-Factor Authenticatie**



**Kant-en-klare softwareleveringspijplijn (CI/CD)**
                                  
      


**Centrale, maandelijkse facturering met een "pay as you go"-service**




ZEN Software DevOps Accelerator bevat:

ZEN, Software, DevOps, Accelerator, bevat:



Fortify Software: Agile Coach to Developer Manager with secure single-

1080_image-20220912-081225.webp

1200_image-20220912-081225.webp

1920_image-20220912-081225.webp

2048_image-20220912-081225.webp

256_image-20220912-081225.webp

384_image-20220912-081225.webp

3840_image-20220912-081225.webp

640_image-20220912-081225.webp

750_image-20220912-081225.webp

828_image-20220912-081225.webp

thumbnail_image-20220912-081225.webp

fortify software-logo

Set up a Blameless Post-Mortem process in 7 steps



Logo of Bellerive Country Club with humorous rhyme: "

256_preview-picture.webp

384_preview-picture.webp

640_preview-picture.webp

thumbnail_preview-picture.webp

bellerive country club-logo

A post-mortem is a retrospective analysis of an incident or outage that occurred in a software system. A post-mortem aims to identify the root cause of the issue, evaluate the response to the incident, and develop a plan for preventing similar incidents from occurring in the future through improvements of the software system or processes.

A post-mortem is a retrospective analysis of an **incident or outage that occurred in a software system**. A post-mortem aims to **identify the root cause of the issue**, evaluate the response to the incident, and develop a plan for preventing similar incidents from occurring in the future through **improvements of the software system or processes**.

Post-mortems should be held as soon as possible after the incident has been resolved while the details of the event are still fresh in the minds of the team members involved. The analysis should involve a diverse set of stakeholders, including developers, operations personnel, and business leaders.

Post-mortems are critical to improving the reliability of software systems for several reasons:
1. **Post-Mortems help to identify the root cause of an issue**: By analysing the incident, the team can identify the root cause of the problem, which may be due to a bug in the code, a misconfiguration of the system, or a failure of a third-party service. Once the root cause has been identified, the team can develop a plan to address it.
2. **Post-Mortems enable continuous improvement**: By analysing incidents and developing plans to prevent similar incidents, the team can continuously improve the reliability of the system. This helps to ensure that the system is more resilient to future failures and that downtime is minimised.
3. **Post-Mortems promote collaboration**: Post-mortems require input from multiple stakeholders, including developers, operations personnel, and business leaders. This encourages collaboration and communication across teams, leading to a better understanding of the system and its dependencies.
4. **Post-Mortems foster a culture of accountability**: By conducting post-mortems, the team takes ownership of the issue and commits to improving the system. This fosters a culture of accountability and encourages team members to take responsibility for the reliability of the system.

To implement the SRE concept of a Blameless Post-Mortem, you can follow the following steps:
1. **Establish a culture of blamelessness**: It is essential to create a blame-free environment where team members can openly discuss problems without fear of being punished. Encourage team members to take ownership of their mistakes and share their experiences so that everyone can learn from them.
2. **Define the scope and objective of the post-mortem**: Decide what you want to achieve from the post-mortem. Define the scope of the investigation, such as the timeline of the incident, the systems and processes involved, and the impact of the incident on the business.
3. **Collect data and evidence**: Collect all the relevant data and evidence, such as logs, metrics, and incident reports. Use these to create a timeline of the incident and identify the root cause.
4. **Analyse the data and identify the root cause**: Conduct a detailed analysis to identify the incident's root cause. This should involve identifying the contributing factors, such as misconfigured systems, inadequate monitoring, or human error.
5. **Develop a remediation plan**: Based on the analysis, develop a remediation plan that addresses the incident's root cause. This plan should be focused on preventing similar incidents from happening in the future.
6. **Communicate the findings and remediation plan**: Share the findings of the investigation and the remediation plan with all relevant stakeholders. This should include both technical and non-technical team members.
7. **Follow up on the remediation plan**: Monitor the implementation of the remediation plan and track progress over time. This will help you identify any new issues and ensure that the plan is effective.

Before starting with the post-mortems, it is crucial to ensure that the following conditions are met:

1. **Leadership buy-in**: Top-level management should be supportive of the post-mortem process and encourage teams to participate.
2. **Team buy-in**: Team members should understand the benefits of the post-mortem process and be willing to participate.
3. **Resources**: Adequate resources should be allocated to support the post-mortem process, such as  tools, engineer who are trained to use the tools and reserve time for trying out Post Mortems.

To persuade Operations teams to start doing post-mortems after every production outage, you can highlight the following benefits:

1. **Learning from mistakes**: Post-mortems help teams identify and learn from their mistakes, improving their processes and systems.
2. **Preventing** future incidents: By identifying and addressing the root cause of an incident, teams can prevent similar incidents from happening in the future.
3. **Team building**: Post-mortems encourage collaboration and communication between different teams, improving team cohesion and effectiveness.



Hilleberg logo: "Say nothing, they'll blame the dog

hilleberg-logo

To persuade developers to join these post-mortems, you can emphasise that:
1. Developers play a crucial role in ensuring the stability and reliability of the system.
2. Post-mortems provide an opportunity for developers to learn from incidents and improve their code.
3. Developers can contribute to the remediation plan by suggesting improvements to the code or architecture.

Post-mortems are a critical tool for improving the reliability of software systems. By analyzing incidents, identifying the root cause of issues, and developing plans to prevent similar incidents in the future, teams can continuously improve the system's reliability and resilience. By establishing a blame-free culture, defining the scope and objective of the post-mortem, and communicating the benefits of the process to all stakeholders, you can successfully implement the Site Reliability Engineering (SRE) concept of a Blameless Post-Mortem.

Sign up for a free demo

Supercharge your software operation with ZEN Software's Agile Analytics

How to measure Effectiveness of a DevOps Team



"R" marks public space for leisurely admiring world art and

256_image (2).webp

384_image (2).webp

640_image (2).webp

750_image (2).webp

thumbnail_image (2).webp

building-property-world-art-window-paint-leisure-public-space

Do you ever find yourself wondering if your software development team is working as efficiently as possible? Measuring productivity in software development can be daunting, but ensuring your team is working at its full potential is critical. Luckily, we've got you covered. We'll explore concrete ways to measure software development productivity and the various metrics and tools that can be used to do so.

Do you ever find yourself wondering if your software development team is working as efficiently as possible? Measuring productivity in software development can be daunting, but ensuring your team is working at its full potential is critical. Luckily, we've got you covered. We'll explore concrete ways to measure software development productivity and the various metrics and tools that can be used to do so. Get ready to dive into the world of Agile and SCRUM methodologies, DORA metrics developed by Google, Git merging and branching, machine learning, and project management tools like JIRA. And if that's not enough, we'll introduce you to Agile Analytics - a revolutionary software tool that combines all these metrics into one easy-to-read dashboard for organisations to make data-driven decisions and optimise their software development processes. Don't miss out on this game-changing information!

Agile and SCRUM methodologies are widely used in software development, and they emphasise continuous improvement and customer satisfaction. Organisations can use metrics such as velocity, burn-down charts, and cycle time to measure software development productivity using Agile and SCRUM. Velocity is the rate at which the team completes user stories or tasks, and it is measured in story points or hours. Burn-down charts show the progress of the team over time, and cycle time measures the time it takes to complete a user story or task from start to finish.



"Parallel Logo Graphics Diagram showing Prod. Owner, Team

product-font-circle-brand-parallel-logo-graphics-diagram

The DevOps Research and Assessment (or DORA) organisation is a research organization backed by Google that helps organisations improve their software development and delivery processes. DORA's research has identified four key metrics that organisations can use to measure software development productivity: **lead time**, **deployment frequency**, **mean time to recover** (MTTR) and **change failure rate** (CFR). Lead time measures the time it takes to go from code committed to code successfully deployed. Deployment frequency measures how often code is deployed to production. MTTR measures the time it takes to restore service when a failure occurs, and CFR measures the percentage of changes that result in a failure.



A screenshot of a rectangle plot with parallel font patterns, outlining metrics &

product-rectangle-slope-font-plot-parallel-screenshot-pattern

Merging and branching are critical aspects of software development, and Git (By Linux creator Linus Torvalds) is the most popular version control system that supports merging and branching. Organisations can measure software development productivity by measuring merge frequency and branch age. Merge frequency measures how often code changes are merged, and branch age measures how long branches remain open before merging or closing. Next to these base metrics: Agile Analytics supports the measurement of ‘software stock’: these are the changes and their risk category that are still ‘in progress’ and have yet to be delivered. Like ‘normal’ stock, software stock can be costly if not managed. Agile Analytics provides real-time insight into the current state of your software stock!

Machine learning is a technology already shaping many industries' future. ML can help your organisations optimize their software development productivity. By analyzing software development data, machine learning algorithms can identify patterns and make predictions about software development outcomes. For example, machine learning algorithms can predict which software development tasks are likely to take longer to complete or are more likely to result in failure.

In this example, Agile Analytics uses machine learning to determine whether a ticket is labelled Feature or Non-feature.



Rectangle, Font, Parallel, Screenshot, Numbers, Pattern,

rectangle-font-parallel-screenshot-number-pattern-software-circle

Project management tools such as JIRA can also help organisations measure and optimize their software development productivity. JIRA provides a range of metrics, such as burndown charts, velocity, and cycle time, that can help teams monitor their progress and identify areas for improvement.

Measuring software development productivity is essential for optimizing software development. Organisations can use a range of metrics and tools such as Agile, SCRUM, DORA, Metrics, DevOps, Merging, branching, GIT, Machine Learning, Project Management, and JIRA to measure and optimize their software development productivity. By using these metrics and tools, organisations can identify areas for improvement and continuously improve their software development processes.

Agile Analytics is a software tool that combines all these metrics into one clear dashboard to help organizations address their data-related challenges. By leveraging Agile Analytics, organizations can improve their ability to make data-driven decisions, increase their agility, and optimize their software development process.

Overall, Agile Analytics is a powerful approach that can help organizations optimize their software development process and improve their data-related decision-making by embracing this methodology.

To learn more about how Agile Analytics works, watch our explainer video below.

Contact us to get a demo of Agile Analytics

Embracing Error Budgets: A Guide to Implementing SRE in Your Organisation




A screenshot of a product's magenta-tinted rectangles

1080_658be661-a89f-4028-9c00-1be05fec9230.webp

1200_658be661-a89f-4028-9c00-1be05fec9230.webp

256_658be661-a89f-4028-9c00-1be05fec9230.webp

384_658be661-a89f-4028-9c00-1be05fec9230.webp

640_658be661-a89f-4028-9c00-1be05fec9230.webp

750_658be661-a89f-4028-9c00-1be05fec9230.webp

828_658be661-a89f-4028-9c00-1be05fec9230.webp

thumbnail_658be661-a89f-4028-9c00-1be05fec9230.webp

product-rectangle-slope-font-line-parallel-magenta-screenshot

Error budgets are an essential tool for Site Reliability Engineering (SRE) that allow organisations to balance reliability and innovation. In this post, we will discuss how to introduce the practice of Error Budgets in your organisation and make the necessary changes to support it.

Error Budgets are a budget for a service's availability that determines the amount of downtime it can have before it becomes a problem. In addition, this budget sets the boundaries for how much work teams can do to keep the service reliable while still allowing the team to work on new features and improvements.

Error Budgets provide organisations with a clear understanding of their service's reliability goals and a framework for deciding when to prioritize innovation over reliability. By giving teams a clear target to work towards, Error Budgets help ensure that teams are focused on delivering reliable services while also giving them the freedom to innovate.

How to Implement Error Budgets in Your organisation:

1. **Define your service's reliability goals**: Before you can start implementing Error Budgets, you must clearly understand your service goals. This will allow you to set an appropriate budget and make informed decisions about how much downtime or non-performance is acceptable.
2. **Communicate your goals and expectations**: Once you have defined your reliability goals, you need to communicate them to your teams. This will help ensure everyone is working towards the same goals and understanding their expectations.
3. **Measure and track your progress**: It is essential to regularly track and measure your service's reliability to ensure that you stay within your Error Budget. This will allow you to make informed decisions about improving your service and ensuring that you meet your reliability goals.
4. **Empower teams to make decisions**: Error Budgets allow teams to decide how to balance reliability and innovation. Empowering teams to make these decisions is important, and providing them with the resources and support they need to do so effectively is important.
5. **Foster a continuous improvement culture**: Finally, fostering a culture of continuous improvement is essential. This means encouraging teams to experiment, learn from their mistakes, and continuously improve their services.

Error Budgets are an essential tool for Site Reliability Engineering (SRE) that allow organisations to balance reliability and innovation. Following these steps, you can successfully implement Error Budgets in your organisation and make the necessary changes to support SRE. By doing so, you will be able to deliver reliable services while allowing your teams to focus on innovation and improvement.

Error Budgets allow feature teams to be alerted by ZEN Software’s Agile Analytics when reliability becomes a risk to the team. Since the team is responsible for the software in production, “you build it, you run it” the team is also accountable for the feature development, stability, and performance.

Using SLI, SLO, and Error Budgets neatly combines powerful concepts from Site Reliability Engineering (SRE) to give your teams the tools to be autonomous, responsible and accountable.

We can help your organisation achieve these goals. Let’s get in touch!

At ZEN Software, we have Agile Analytics that helps you manage your Error Budgets, the knowledge and experience with implementing SRE, SLIs, SLOs and Error Budgets. 

Meer artikelen

Meer over DevOps

DevOps



Creative logo: "Praxis", for innovative solutions.

256_praxis-logo

384_praxis-logo

640_praxis-logo

750_praxis-logo

thumbnail_praxis-logo

praxis-logo

Praxis



Text: "Brico" - Logo representing a major DIY chain

256_e9c56f0e-4012-4b31-a31e-e5fe0e377411.webp

384_e9c56f0e-4012-4b31-a31e-e5fe0e377411.webp

640_e9c56f0e-4012-4b31-a31e-e5fe0e377411.webp

750_e9c56f0e-4012-4b31-a31e-e5fe0e377411.webp

828_e9c56f0e-4012-4b31-a31e-e5fe0e377411.webp

thumbnail_e9c56f0e-4012-4b31-a31e-e5fe0e377411.webp

brico-logo

Onze klanten

Afspraak Maken

ZEN Software kan uw organisatie in staat stellen om zodanig te presteren.
Laten we contact opnemen!

ZEN DevOps Accelerator

VeelTools

Effectievere softwareontwikkeling voor alle organisaties

ZEN Software DevOps Accelerator bevat:

Meer over DevOps

Onze klanten

Wil je software ontwikkelen met hypersnelheden en toch veilig blijven?

Veel
Tools