workingsoftware.dev

Sign in Subscribe

Latest

Technical Debt Scenario #2: Feature factory

Technical Debt Scenario #2: Feature factory

Your stakeholder wants to see features at an impossible speed. Your team's velocity is dropping due to technical debt, so sometimes the product owner or another stakeholder says, "I do not understand why it's taking so long to add a new feature." What do you say then?

Technisches Schulden Szenario 2: Die Feature Fabrik

Technisches Schulden Szenario 2: Die Feature Fabrik

Deine Stakeholder erwarten, dass Du mit deinem Team neue Features in einer unmöglichen Geschwindigkeit entwickelst. Irgendwann kommt ein Stakeholder und sagt Dir: "Ich verstehe nicht warum es so lange dauert dieses eine neue Feature zu entwickeln. Das sollte doch einfach sein." Was sagst Du dann?

Technical Debt Scenario #1: Start without any architectural vision

Technical Debt Scenario #1: Start without any architectural vision

The team is working on a new software product. The only thing the team wants is to start coding. How can technical debt already cause?

How would you describe technical debt to a non-technical person?

How would you describe technical debt to a non-technical person?

If you work on a product team, you'll come into contact with people who don't have a technical background. One day, that person will ask you what technical debt is. That's your opportunity.