The traditional waterfall approach to software development is a methodology wherein developers follow eight sequential steps (conception, initiation, analysis, design, construction, testing, implementation, and maintenance). A better alternative is the agile scrum methodology. Herein, agile teams understand customer requirements and subsequently build solutions around that. These teams, often referred as scrum teams, consist of peoples who possess sound knowledge of tackling unpredictability during rigorous development processes. These teams require constant empirical feedback, self-management within the group, and adequately tested product increments within short time iterations of three to five weeks during the development process.
There are three primary stake holders in this approach: product owner, developer/tester, and ScrumMaster. The product owner provides constant feedback and influences team decisions by understanding what is best for the customer. Developers do programming and test their work and of others, if required. Lastly, ScrumMaster’s job closely relates to that of project managers, but without the baggage of processes and procedures imposed by a traditional methodology. In a nutshell, ScrumMasters are expected to adhere to any role that can facilitate teamwork and move the project forward.
