News & Events About Xebia
India > Our Offering > Software Development > Agile Offshore > Control

Control

Key Performance and Quality Indicators for Project Control

Print
RSS feeds
Agile Model provides regular feedback on the project progress, performance of the team and quality of deliverable produced.  The primary measure of a Agile software project’s success is the delivery of functioning software.

At the end of each iteration, Offshore team delivers working software, at least into a demo or testing environment, so their stakeholders can clearly determine whether progress is being made and money is being spent wisely.

Project Status Report


Project Status Report provides information on resources, consumed budget and project risks. Xebia and the customer will agree upon the exact contents of this report and the reporting frequency.


Burn Down Chart


In Agile model, software requirements are managed as a prioritized stack, and each item in the stack includes an up-to-date estimate of the amount of effort necessary for implementation to occur. An effective burn-down chart tracks both the amount of work required to implement a particular iteration and the work needed to complete the entire project. With these metrics, you can better determine a more accurate estimate of your project's end date.


Defect Trend Graph


Defect trend graph
provide information on found defects classified into three categories:
  • High Impact
  • Low Impact
  • Medium Impact
You should not deploy your system until you see a clear downward trend in defects.

Code Quality


Development team and you as a customer have access to the following information about the code quality.
  • Coding standard compliance
  • Undocumented code
  • Source Lines of Code (SLOC)
  • Class, Package and File counts
  • PMD report for potential problems possible bugs, unused and suboptimal code, over-complicated expressions and duplicate code.
  • Dependencies and couplings

Offshore and onsite teams share the same common source code repository and the same continuous integration environment. It provides the report about the following:
  • Broken builds
  • Junit test results
  • Test coverage report

Click the picture to enlarge it in a new window.

Configuration Management Report


The configuration management system provides reports on the activity in the source code repository. These reports cover:
  • Source code lines committed by the developers
  • Revision, tagging and branching history