align-your-frontend-team-with-architecture Blog Related Topics 
Dynatrace
APRIL 5, 2024
This blog post is for both novice and seasoned audiences alike. The first part of this blog post briefly explores the integration of SLO events with AI. Further in this article, we will explore which empirical approach to adopt in order to best align with the Service Level Objectives (SLOs). Which approach should you take?
Dynatrace
AUGUST 16, 2023
SLOs are pivotal for development, DevOps, and SRE teams because they provide a common language for discussing system reliability. Without implementing robust SLO monitoring, anomaly detection, and alerting on SLOs, teams can miss issues that breach defined quality targets. But just establishing SLOs isn’t enough.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Strategic Tech
DECEMBER 20, 2020
Team Topologies has significantly advanced the discussion on organisation design for technology companies. The next step is to determine what Team Topology boundaries align to…what should Stream-aligned (and other) teams own? Should teams be frontend, backend, full stack or something else?
Strategic Tech
AUGUST 10, 2020
If every significant architecture decision has business consequences, then knowing the business model and which trade-offs to choose is maybe the most important skill of architects. But what is the actual relationship between a business model and a software architecture? It’s not just about business models and architecture, though.
Strategic Tech
JULY 21, 2020
Most organisations go through an architecture modernisation effort at some point as their systems drift into a state of intolerable maintenance costs and they diverge too far from modern technological advances. What architecture will be optimal for enabling that business vision? How are we going to deliver the new architecture?
Abhishek Tiwari
JULY 20, 2019
When it comes to organising engineering teams, a popular view has been to organise your teams based on either Spotify's agile model (i.e. squads, chapters, tribes, and guilds) or simply follow Amazon's two-pizza team model. Secondly, you need flexibility and room for error when iterating with organisational structure.
Strategic Tech
JULY 18, 2018
There are thousands of ways we can shape the software systems we build and organise our teams around them. Heuristics help you to build rich mental models and make decisions that offer the best solutions in your context. Yet there is no flowchart we can simply follow to find the optimal design.
Expert insights. Personalized for you.
230 
Let's personalize your content