Agile Services - Part 6: The Long Term
This is the sixth post in the series about how to apply Agile methods to run services based on existing software, and I think this will be the conclusion of the series.
The first post describing the problem at some length is here, but the TL;DR; is
I don't think there are great resources on how to apply agile . . .
Agile Services - Part 5: Team Processes
This is the fifth(!) post in the series about how to apply Agile methods to run services based on existing software.
The first post describing the problem at some length is here, but the TL;DR; is
I don't think there are great resources on how to apply agile methods to run and develop services based on existing . . .
Agile Services - Part 4: The Agile team
This is the fourth post in the series about how to apply Agile methods to run services based on existing software.
The first post describing the problem at some length is here, but the TL;DR; is
I don't think there are great resources on how to apply agile methods to run and develop services based on existing (open . . .
Agile Services - Part 3: The Work We Do
This is the third post in the series about how to apply Agile methods to run services based on existing software.
The first post describing the problem at some length is here, but the TL;DR; is
I don't think there are great resources on how to apply agile methods to run and develop services based on existing (open . . .
Agile services - Part 2: Horizons
This is the second post in the series about how to apply Agile methods to run services based on existing software.
The previous post describing the problem at some length is here, but the TL;DR; is
I don't think there are great resources on how to apply agile methods to run and develop services based on existing . . .
Agile services - Part 1: Background
When I started this blog, the goal was to make a writeup of any problem I couldn't easily duckduckgo the answer to.
Well, now I have gone quite far down the rabbit hole, as the goal apparently changed to a problem that I can't find a good answer to in dudckduckgo, several books, courses etc.. This time the topic is not . . .
Git compliance management
Or: Now when I'm a manager my blog topics are boring
Most people in the modern software defined infrastructure space have at least stumbled upon the term GitOps.
In short - at least in the head of your's truly - GitOps is an evolution from infrastructure as code. Basically it means consistent, controlled automatic deployments and updates of your infrastructure based on git . . .
