• Português
  • 简体中文
  • 繁體中文
  • Deutsch
  • English
  • Español
  • Français
  • 日本語
  • Latviešu
  • Lietuvių
  • Русский

Submitted Conference Content

Full name

Vinay Krishna

Job Agile Transformation Consultant / Agile Technical Coach
email vinaykris [at] gmail [dot] com
Skypeid agilevinay
Phone number +919886382983
Company Xebia
City (Country) Bangalore
Time 1h
Type of Conference Conference < 100 attendees
Level Everybody

9 Practices to minimize Technical Debt


Vinay is having 14 years of experience in Software Development and Management. He is flourished in a fast-paced environment requiring excellent problem solving skills, multiple project completion under short deadlines and ability to connect with clients and end-users. He helps team to adopt agile, scrum, XP and lean practices past 7 years. Vinay is doing research, pursuing PhD, in the field of Software Architecture. So far his 12 papers have been published in various international journals and conference proceedings. Two of his papers are translated in Chinese language by Scrum network at China. Vinay is managing Agile Bangalore User group and also elected as a Secretary of Computer Society of India, Bangalore chapter for 2014-2016. He has been part of organizing team of several international conferences and also invited as a speaker or panelist at various international/national conferences. He delivers guest lecture on request at various prestigious engineering college/universities and various organizations.


Often we find it difficult to incorporate any changes in a software project during later phases of its development, or during post-delivery maintenance. Primary reason for this is inflexibility in design and code which makes it difficult for changes to be incorporated. This inflexibility substantially increases the cost of making changes and this metaphor has been termed as Technical Debt. While Technical Debt cannot be eliminated completely, its burden needs to be reduced. Many agile practitioners have suggested some practices to avoid or eliminate Technical Debt. In this session we would discuss about a method to get relief from Technical Debt and talks about nine proven practices that a developer can follow to minimize Technical Debt. These practices have been used and found to be effective when implemented in projects which will be used as a case study.

Benefits for the attendees

Key questions which would be covered in the session: •What is technical debt? •Why is it difficult to incorporate any changes in a software project during later phases of its development, or during post-delivery maintenance? •Why is it difficult to maintain the code along with quality in longer run? •Why do we need technical debt? •Why cannot we eliminate it completely? •How can we minimize the technical debt? •What are some practices to minimize technical debt?

Go to the submission page!