Join us at Jax DevOps 2018
We are excited to announce that our Senior Agile Delivery Consultant, Antonio Cobo will be speaking at Jax DevOps 2018; the four-day conference for Continuous Delivery, Microservices, Docker & Clouds.
Click here to find out more about the conference and register!
Failed and successful stories with Technical Debt
The concept of Technical Debt is always different when you ask a developer or a sponsor. Why is it that complicated to understand for the sponsors? why do developers struggle to explain it? I’m sharing my failed and successful attempts with Technical Debt in three different countries and different contexts. Each time I was on a different role and my perspective was different, but in every case, I needed to deal with technical debt.
Agenda of the talk:
– what’s technical debt?
Definition. What does the developer mean with technical debt? What does the sponsor understand with technical debt?
– I tried, but I failed
Several examples trying to add technical debt to the backlog and why I think I failed
– We tried, and it worked!
Some examples of success stories adding technical debt to the backlog. Key factors: team decision, trade of, conversation.
One size does not fit all – Agnostic Agile Oath
Since the introduction of Agile lot of companies have tried to impose the same framework at a big scale without suiting the framework to customer context and to a wider strategic vision. Agile has never been about frameworks or locking your customers into one way of doing things. I will show examples of bad Agile practices and why the Agnostic Agile Oath is needed – One size does not fit all!
I will introduce the Agnostic Agile Oath, the creators of it and the reasons it was created.
I will then review the twelve agreements of the oath citing real life examples for them.
Agile is not the final goal, it is only the mean to reach the real goal.