With emergence of DevOps(CI,CD), Releasing Software to production takes matter of hours or even minutes. Everything is scaling up and down (vertically), to the right and to the left (horizontally). Therefore having a good monitoring system is a must. However, monitoring is still being implemented by OPS team only. i.e teams who dont write applications. Why is that so? How can it be changed to achive better results?

We all heard about a widely known practice TDD - test-driven development, or about the less known BDD - behaviour-driven development, or about the least known ADD. However, Metrics Driven Development (MDD) is mentioned nowhere.

So what is MDD? My definition of MDD is a practice where metrics are used to drive the entire application development. In a company which uses MDD, everything from performance and usage patterns to revenue is measured. Moreover, every single decision taken by developers, operations or even business people is based on metrics. Metrics are used to monitor team performance, solve performance bottlenecks, estimate hardware needs or to accomplish other purposes at any stage of development life-cycle.
MDD brings visibility to the whole development process, so decisions are taken quickly and accurately and mistakes are spotted as they happen and fixed immediately.MDD stacks up well with other established practices such as TDD, BDD or Scrum, by using metrics to set the goals for the sprint. Metrics also uncover problems and usage patterns (in production) which are hard to notice during acceptance testing.

In this session i will share my thoughts and experience gathered while working with DEV teams trying to makes sence of metrics and MDD