This post originated from an RSS feed registered with .NET Buzz by Maruis Marais. Original Post: Code Metrics, Code smells and Refactoring in Practice Feed Title: exceptionz Feed URL: http://feeds.feedburner.com/Exceptionz Feed Description: I am an XP, TDD, OO and .NET enthusiast. Things like Design Patterns makes my pulse race, I love learning exciting new things and to share my thoughts and techniques with the world. So join me and together we can explore the awesome world of software development Latest .NET Buzz Posts Latest .NET Buzz Posts by Maruis Marais Latest Posts From exceptionz

Our team uses eXtreme programming practices to manage development on a mission critical system for a large retail chain. We have not adopted all the practices, but use the majority of the practices.

Here is a list of the practices we use:

• Test-Driven Development (VSTS Testing Tools)
• Collective Code Ownership
• Coding Standards (FxCop, Code Metrics)
• Continuous Integration (Daily builds, but we are looking to implement a CI environment soon.)
• Planning Game ( Iteration planning and daily standup meetings )
• Customer Test (Fit, VSTS Web Tests)
• Small Releases (Fortnightly UAT Releases)

Every morning at the standup meeting the team lead will report on the nightly integration build.

This report includes the following metrics:

• Unit tests passed, failed, ignored
• Fit test passed, failed, ignored, exceptions
• Test Coverage (Should be more than 80%)
• Cyclomatic complexity (Should be less than 10)
• Code Instructions (Should be less than a 100)
• FxCop rule validations

Each day metrics are compared to the previous day and overall the project manager tracks these metrics to get an overall feel for the health of the project.