Test automation is usually lagging behind development of new functionality. The tools that are used to automate are dependent on the UI and this causes automation of the functionality to start only after the environment and the UI are stable.
The question is should there be a separate product backlog item (PBI)/ User story for test automation in each sprint.
Automation is an integral part of a scrum development environment. Selenium is an automation tool that can be used to test the functionality in a web based project.
The ScrumMaster is a new management role introduced by Scrum. The ScrumMaster is responsible for the success of Scrum. Given that explanation, there really is no analog of the ScrumMaster in traditionally managed projects. Further, “The ScrumMaster is responsible for ensuring that Scrum values, practices and rules are enacted and enforced. The ScrumMaster is the driving force behind all of the Scrum practices.” Thus most of the ScrumMaster’s responsibilities fall entirely within the purview of Scrum itself.
Agile methodology is an approach to project management, typically used in software development. It helps teams respond to the unpredictability of building software through incremental, iterative work cadences, known as sprints.