A Scrum master is like a leg in the tripod of the Scrum team, with the other two being the product owner and the development team. The relationship of the product owner with the business representative is balanced out by the Scrum master’s relationship with the development team. The role of the Scrum master is to support the team in becoming self-organized, to remove any obstacles the team might be facing and to ensure that the Scrum methodology is being followed. However, unlike the product owner, the Scrum master does not play a management or supervisory role for the team.
Agile has not been warmly embraced by large organizations.
One of the obvious reasons for this is that large organizations do not undertake major changes unless absolutely necessary. Another reason is related to the fact that Agile is different from traditional project management philosophies from the roots to the leaves. Large organizations are quite orthodox when it comes to their organizational structures and management.
During Release Planning, the Scrum Core Team reviews the User Stories in the Prioritized Product Backlog to develop a Release Planning Schedule, which is essentially a phased deployment schedule that can be shared with the project stakeholders. Length of Sprint is also determined in this process.
Introduced by Alistair Cockburn, Crystal Methods, which is a collection of Agile software development approaches, focuses primarily on people and the interaction among them while they work on a software development project. There is also a focus on business-criticality and business-priority of the system under development. Unlike traditional development methods, Crystal doesn’t fix the tools and techniques of development, but keeps people and processes at the core of the development process. However, it is not only the people or the processes that are important, rather the interaction between the two that is most important.