22 April 2024

Naming Conventions Principle

Naming Conventions Principle

Naming Conventions Principle purpose

  • Name Standards / Code Conventions make it significantly easier for Developers and analysts to understand what the system is doing and how to fix or extend the source code to apply for new needs.

Scrum approach

  • Every Sprint an Increment with at least one Functionality need to be produced, otherwise the Product Owner and Stakeholders won’t be able to inspect the increment accurately.

Naming Convention benefits

  • To reduce the effort needed to read and understand source code;
  • To enable code reviews to focus on more important issues than arguing over syntax and naming standards;
  • To enable code quality review tools to focus their reporting mainly on significant issues other than syntax and style preferences;
  • To help formalize expectations and promote consistency within Developers;
  • To enable the use of automated refactoring or search and replace tools with minimal potential for error;
  • To enhance clarity in cases of potential ambiguity;
  • To enhance the aesthetic and professional appearance of work product (for example, by disallowing overly long names, comical or “cute” names, or abbreviations);
  • To help avoid “naming collisions or frictions” that might occur when the work product of different organizations is combined;
  • To provide meaningful data to be used in project handovers which require submission of program source code and all relevant documentation;
  • To provide a better understanding in case of code reuse after a long interval of time.

More informations for Scrum Testing

More informations for the Scrum PSD certification here.

Leave a Reply

Your email address will not be published. Required fields are marked *