What is technical debt and why is it important for the business and the Product Owner to know this?
@sasukesarutobi38624 жыл бұрын
Very clear, thank you. The way you describe developers being constrained by time constraints reminds me of the iron triangle.
@muchammadnurwibowo82554 жыл бұрын
dependency yg ga setransparan itu jadi banyak yg ((cutting corners)) gitu ya, coach. Financial debt lead to compunding interest & bubble bikin langsung ngerti. Plumber & dentist analogy made it even more understandable! Btw makin cocok sama aston spirit kyknya nih
@scrummasterinblack4 жыл бұрын
Ada beberapa jenis technical debt, misal tidak nulis unit test, tidak refactor code, pakai teknologi yang tidak sesuai, dsb.
@scrummasterinblack4 жыл бұрын
Sejauh ini lagi suka sama karakter Aston Spirit :D Lagi nabung buat Austrian Audio. LoL :P
@muchammadnurwibowo82554 жыл бұрын
@@scrummasterinblack company founded by AKG ENGINEERS!
@scrummasterinblack4 жыл бұрын
Muchammad Nurwibowo Wibi I know. That’s why I am saving up my money 😂
@Sina-sd6qp2 жыл бұрын
Thank you for your very helpful videos . I learn a lot! Just feedback about this video: you are standing too close to the curtains behind you 😉
@scrummasterinblack2 жыл бұрын
Yeah. I made this video when I didn't have a proper space. Thanks for the feedback.
@Sina-sd6qp2 жыл бұрын
Thank you again! How do you handle or manage or discover technical depth? You mentioned Sonar. Are there any official ways to do it?
@scrummasterinblack2 жыл бұрын
Manage: this needs to be part of the conversation at least every Review, Retro and Planning. During Sprint Planning the team needs to take some Technical debt they want to pay. Every Sprint should involve paying technical debts not only adding features. Discover: usually teams know when they make technical debt. Most technical debt are made under conscious decision. Otherwise tools like Sonar [ www.sonarqube.org/ ] can give insights about the technical debt at code level - eventhough it won't tell you technical debt at architectural level.