workingsoftware.dev

Sign in Subscribe

Patrick Roos

Patrick Roos

Independent Tech Lead, Software Architect and Software Engineer

Do we need a software architect in our agile team?

Do we need a software architect in our agile team?

This question often comes up in agile teams. In this blog post, we look for the answer to this question in the context of the various agile and organisational frameworks like Scrum, LeSS, SAFe, Disciplined Agile and draw a conclusion.

12 Principles of Agile Software Development

12 Principles of Agile Software Development

While preparing for my guest lecture on technology decisions, I stumbled across a slide with the 12 principles from the agile manifesto. It made me realise again how apt these principles from the agile manifesto from 2001 (!), which are often forgotten in practise, are for product development.

What is Infrastructure as Code? And why do you need it?

What is Infrastructure as Code? And why do you need it?

This article describes what Infrastructure as Code is and what problems Infrastructure as Code can solve. We also discuss the benefits and challenges of Infrastructure as Code and which tools are suitable for Infrastructure as Code.

Technical Debt Scenario #5: The code documents the system.

Technical Debt Scenario #5: The code documents the system.

Unfortunately, several long-time developers have left the product team. In addition, there is virtually no technical documentation for the system. Even the architectural decisions are no longer traceable. What would you do to eliminate this kind of technical debt?

Technisches Schulden Szenario #5: Der Code dokumentiert das System.

Technisches Schulden Szenario #5: Der Code dokumentiert das System.

Leider haben einige langjährige Entwickler das Produktteam verlassen. Zusätzlich gibt es praktisch keine technische Dokumentation zum System. Auch die Architekturentscheide sind nicht mehr nachvollziehbar. Wie würdest Du vorgehen eine solche Art von technischen Schulden zu adressieren?

Technical Debt Scenario #4: Hype Driven Development

Technical Debt Scenario #4: Hype Driven Development

The development team is always on the hunt for the latest technology hype. Currently, there are more than two front-end frameworks used for the product and the time to launch new features is getting longer and longer. What would you do?

Technisches Schulden Szenario #4: Hype Driven Development

Technisches Schulden Szenario #4: Hype Driven Development

Das Entwickler Team ist ständig auf der Jagd nach den neusten Technologie-Hypes. Aktuell werden im Team bereits zwei unterschiedliche Frontend-Frameworks gleichzeitig eingesetzt und die Geschwindigkeit des Teams wird dadurch ausgebremst. Was würdest Du tun?