Coding Standards Blog Art.png
source: Drupal Coding Standards

[[@[eng_website_id]_[eng_sub_id]|Get the Full Story of Playing Cards (VegasMaster)]][[@[eng_website_id]_[eng_sub_id]|Discover Las Vegas Pawn Shops (VegasMaster)]][[@[eng_sub_id]&eng_source=[eng_website_id]&x=x&subid=ad01|New 'Skinny' Pill Takes UK by Storm (Healthy Mum Daily)]][[@[eng_website_id]_[eng_sub_id]|Get a List of Famous Gambling Quotes (VegasMaster)]]A Peek Into Jennifer Lopez’s Massive Walk-In Closet (The Daily Western)What Would Happen If Humans Ceased To Exist? (Buzzwok)Man Climbs On Dead Whale As ‘SHARKS Swarm Around Him In Feeding Frenzy! (Buzzwok)[[@[eng_website_id]_[eng_sub_id]|Single Mom From London Makes £7.650/Month (SearchingProfits)]]Single Mom From London Makes £7.650/Month From Home (EZ trader)Coding Standards


XP Beck (2000)


Coding standards means a defined set of standards which needs to be followed to develop a project which fulfil all project requirements. This practice helps in pair programming practice of XP. Because the predefined set of rules and standards for code leave no room for arguments and give easy path to programmers to develop code set for software (Beck, 2000)
Martin (2002) explains that it is very important to have set of standards for code sets to make this code clear to everyone. He adds that this factor is helps to modify the project as well because if there is some code standards in any project than it becomes easy to modify that project for programmers because the ease to understand the project code due to knowledge of pre-defined code standards.
Alistaire (2000) describes that coding standard is very important practice in XP so that all the code in the system looks as if it was written by a single individual.


Coding standard practice is always defined as best XP practice for making code more understandable. Coding Standards are rules that emphasize communication throughout the code. The purpose of this practice is to make the code more consistent and independent so any authorized programmer can re code it when needed (Baired, 2002). The idea behind defining the coding standards is that all developers write code for any program in consistent and common language (Beck, 2000).
Stewart (2002) describes some benefits of coding standard practice. One of the key factor which makes this practice more valuable is that it provide helps in other practices and also make code so untestable and consistent.

Links to other agile principles and practices

Refactoring is a process to rewrite the existing internal code while keeping the external structure. This practice is related to coding standards because it also make the code more clear, easily readable and understandable.

Simple rules is related to coding standard practice because simple rule means make the process, methodology, service and procedures simple for agile teams. Simply defined rules and procedures makes agile teams more productive and they deliver the business value in time without compromising the quality (Augustine, 2005).

Guiding vision is agile practice to make the project life cycle visible at every stage. When the project vision is clear to project teams then they become more dedicated and productive to ensure the project success. This is not possible without defining the rules and communicating the ideas in simple ways (Augustine, 2005).

Links to PMO knowledge areas (KAs)

Ambiguity Management Coding standard is practice to make sure that all code is written by single person which removes ambiguity about the expertise and technicalities which provides a comfortable environment to everyone work on that project.
Project Communication Management defined set of rules and standards make communication management so easy. Standards and rules make communication between team more clear and untestable.

Examples of use outside to IT domain

All companies use standards to make things easy and understable. Standards provide guideline to make process more clear. So many automotive and avionic industries are using this technique to provide guidelines and to set standards in their safety related processes. DO-178C standard by MISRA one example.


Augustine, S. (2005) Managing Agile Projects. 1st ed. Prentice Hall.

Auer, Ken & Roy Miller. (2002), Extreme programming applied. Indianapolis, Indiana: Addison-Wesley.

Beck K (2000) Extreme Programming Explained. Addison-Wesley, Reading, MA.

Baird, Stewart (2002), Sams teach yourself extreme programming in 24 hours. Sams publishing.

Cockburn, Alistair, and Laurie Williams. (2000), "The costs and benefits of pair programming." Extreme programming examined: 223-247.

Martin RC (2002) Agile Software Development, Principles, Patterns, and Practices. Prentice-Hall, Englewood Cliffs, NJ.

Maruping, L. M., Zhang, X., & Venkatesh, V. (2009) 'Role of collective ownership and coding standards in coordinating expertise in software project teams'. European Journal of Information Systems. 18(4). 355-371.

Mark Pitchford & Bill St. Clair. (2013) Adopting aerospace development and verification standards: Part 1 – A coding standards survey. [Online]. Available at: [Accessed 7th March 2015].

Fowler, M., Beck, K. & Brant, J. (1999). Refactoring: Improving the Design of Existing Code 1st ed., United States: Addison-Wesley Educational Publishers Inc.

External links

Java Coding Standards
Microsoft .NET Coding Standards

Read in another language