Agile Coding & Programming Standards

If programmers all adhere to a single agile coding standard (including everything from tabs vs. spaces and curly bracket placement to naming conventions for things like classes, methods, and interfaces), everything just works better. It's easier to maintain and extend code, to refactor it, and to reconcile integration conflicts, if a common standard is applied consistently throughout. The standard itself matters much less than adherence to it. Fortunately, modern IDEs make it trivial to apply many kinds of formatting, even after the fact.

Previous Article
Sprint Burndown Chart for Agile Development Tracking

Learn how to use a sprint burndown chart to measure iteration or release progress in your agile software de...

Next Article
Agile Pair Programming & Common Codebase Use

Benefits of a common codebase and other best practices in agile pair programming that make agile software d...