How do you track changes to your product?
Reliable and Agile

Category Archives:software development

How do you track changes to your product?


Working with a global teams and partners which are not co-located has become a trend these days. This poses a challenge to the product owners / managers to keep control on the changes being made to the product. The key here is to track every change happening to your code, so that a rollback can be opted if required. Sounds ideal right? Is it really possible?

Well many will argue that its no longer a big challenge, and easily possible. I agree to this, provided your partners who works on your code are aware of the tools and practices to support it. I have seen many companies with whom I have worked at different capacities, that there is a lack of basic processes. There is no meaningful connection between their ISO or CMM certifications to the actual processes they follow. Sometimes these things run completely independent of each other, whereas they are intended to reflect each other.

@iConnect our focus was always building a lean development methodology. Our people are still put first to processes, but these processes are their top priority. We picked up only the ones which gave us a significant value . We use processes that give a completely transparent view of whats going on to our customers. And believe me its hard to do, as there is no where to hide.

So how do we do it?

  • We use code repository like git | subversion for each of the project. Thats pretty standard.
  • We use TRAC as our User story & Defect management system. It generates a unique number for each User Story and defect.
  • This instance of TRAC is connected to our code repository.
  • Whenever a developer commits changes to the repo they put a #id in their comment. This is a User story or defect number for which they are trying to commit these changes
  • TRAC is intelligent and connected to our code repo. It can then let us click on the comment #id link and shows us a change set details
  • This way every change committed links back to a defect or User story. So it is easy to understand these changes in a context.

This gives our customers great control over their product and confidence in our team.