Writing automated tests is more than just a luxury for any agile software development team. It is a need, and is an essential tool to find bugs quickly during early phases of software development cycles. Although writing automated tests may seem like an easy task for engineers, there is still the possibility of ending up with poorly implemented tests, and the high cost of code maintenance in any agile process. ROI, Maintenance & Reusability is on the high priority in every Feasibility study of Automation. In this article, we will take a look at one such maintenance problem and how to overcome it using the much-famous Page Object Model. Nowadays, the page object model is a new Test automation buzz word being asked during Testing Job interviews as well.