Teams face many challenges to keep a sustainable and constant pace of refactoring. In many cases, this is due to oversight of some very basic guidelines and ground rules to enable a “refactoring-friendly” environment.

In this session, I’ll build on my 10-year journey doing successful refactoring of poor code and present necessary ground rules and practical guidelines for enabling sustainable refactoring. I’ve clustered these guidelines into three high level categories:

* Team development habits in maintaining old code
* Enabling a configuration management environment
* Making refactoring effort visible and trackable

Whether you’re a technical person working on enhancing poor code or a manager sponsoring this activity, you’ll walk away with a very good background information to enable a sustainable refactoring environment and eventually a high quality product code.

You must be a Member to view this post and you are currently not logged in.

You can either log in below or sign up here.