#technical debt #agile

Dealing with technical debt in an agile environment

How many times have you experienced software engineering teams that, regardless of the reasons, opted for quick solutions, resulting in poor code quality and created problems that accumulated over time? Where did this lead? Eventually, the product resembles an iceberg. The stakeholders can only see the end result, the behavior of the system, the part of the iceberg that lies above the surface, unaware of what lies underneath it. However, the software engineers have the full picture. ...

#agile #scrum

Technical background: the extra mile on scrum mastery

Among other things, scrum is very “trendy” lately. Virtually any company that I know of has either adopted it or attempted to do so or at least considered it. The software industry needs change rapidly, evolving the scrum master in one of the most sought after roles. However, the inability of the offer to meet the demand and the absence of required technical skills to become a scrum master has made the role appealing to a number of people outside the industry, giving birth to an ongoing debate. ...

#agile #xp

Agile code

During Christmas, just a few days before I decided to take up blogging, I was reading Sandro Mancuso’s excellent book Software Craftsmanship. I couldn’t help but agree (sometimes even out loud) when reading what Sandro describes as the Agile Hangover. How many companies decide to become agile only to find their projects failing for the very same reasons that urged them to become agile in the first place? What are the common characteristics of so many failed attempts? ...