© 2019 by DevelopAgile.com 🐿️

Website developed through ongoing iterative and agile development.

PSST! Need some help?

You can search for terms in the Search bar above! ;)

The Agile Dictionary

 

Code Refactoring is the process of improving and simplifying the internal structure of an existing source code without changing its external behavior. Agile Teams are adding, modifying and extending their code with every iteration and every addition makes the code more complex. As per the 8th and 9th Agile Principles, the development should be sustainable and the team should aim for technical excellence. Refactoring code allows optimization that ease the implementation of new features in the future, avoiding technical debt.

Refactoring

The role-feature-reason template is meant to help defining user story in a clear, concise and consistent manner. It is the most common user story format and is presented as follow:

“As a [type of user] I want [some feature] so that [some reason]

Role-feature-reason

Rule of Simplicity refers to the simplicity of the code written by the development Team. It is a set of criteria to apply to the written code in order to evaluate if the code is simple enough (easily understandable, testable and modifiable). This should be followed when developing but more importantly controlled when refactoring. These four criteria are evaluationg the code simplicity :

  • Code is verified by automated tests and it passes all tests

  • Code does not contain any duplication

  • Code espresses every distinct idea separately

  • Code is made of the minimum number of components (classes, methods, lines)

Rule of Simplicity