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

Submitted Conference Content

Full name

Raja Bavani

Job Chief Architect
email raja_bavani [at] mindtree [dot] com
Company MindTree
City (Country) Pune
Time 45'
Type of Conference Conference > 100 attendees
Level Everybody

Code Quality: An Issue of Mindset, not Toolset!


Raja Bavani is Chief Architect of MindTree’s Product Engineering Services (PES) and IT Services (ITS) groups and plays the role of Agile Evangelist. He has more than 20 years of experience in the IT industry and has presented at international conferences on topics related to code quality, distributed Agile, customer value management and software estimation. He is a member of IEEE and IEEE Computer Society. He regularly interfaces with educational institutions to offer guest lectures and writes for technical conferences. He writes for magazines such as Agile Record, Cutter IT Journal and SD Times. His distributed agile blog posts, articles and white papers are available at and He can be reached at .


Software quality has two primary dimensions: Internal Quality and External Quality. External Quality is an attribute that relates the end-user experience. External Quality can be assessed and improved through defect prevention as well as black box testing. Internal Quality is visible to various groups in the development team such as designers, developers, maintainers and technical reviewers. Great focus on acceptance testing or black box testing by means of well-documented test cases, multiple rounds of rigorous testing, defect fixing and defect verification is mandatory for successful deliveries. However, lack of focus on Internal Quality could pose serious consequences in the form of unexpected naive defects, technical issues and maintenance nightmares. Poor Internal Quality encompasses the root causes for issues related to External Quality. Thus, in order to improve Software Quality, Internal Quality must be improved. Planning and conducting code reviews in software projects is vital to assuring code quality. Code quality improves with the usage of the right constructs, programming style and principles. Systematic focus on code quality is the way to make the end product adaptable, maintainable, and extensible. This not only saves efforts expended in defect detection, defect analysis, defect fixing and defect verification during various levels and types of testing in the project, but also reduces maintenance overheads during the rest of the project life. One of the twelve practices of extreme programming (XP) is ‘Coding Standards’. The objective of this session is 1) to present the current state of code quality in the industry and discuss about the importance of mindset in focusing on code quality, 2) to discuss reasons for why toolsets fail and 3) to discuss an approach that can help agile teams nurture the culture of writing good quality code.

Benefits for the attendees

Attendees will understand 1) The significance of Code Quality 2) ‘Coding Standards’ – One of the 12 XP Principles 3) How Scrum teams can implement engineering practices to ensure code quality 4) The initial steps to nurture the culture of writing quality code

Go to the submission page!