Agile Values In Scrum: The Important Principles And Values Of Scrum Explained

By Author: Mrugesh Panchal
Total Articles: 48
Comment this article

Scrum is perhaps the best known Agile method of implementing successful projects. Scrum projects complete on time, and result into higher ROI for the stakeholders. This makes Scrum an ideal, and the most preferred choice while implementing projects, in which the product definition is liable to change with the changing market conditions. The Agile values and principles apply to scrum.

Individuals and interactions more important than processes
Scrum, just like other Agile frameworks, relies much upon putting trust in teams and individuals connected with the project. The manner in which the team interacts is important. The team should take a proactive interest in determining what is to be done, and figure out how to achieve the aims and objectives associated with the project. Self correction and self learning is an integral part of scrum methodology, and the team should put in efforts to identify potential issues and problems which can act as impediments and hamper the project. The individuals should also take the responsibility to resolve the issues – they can take the help of the scrum master or the ...
... product owner as and when required, since these individuals are usually senior members, and have the required knowledge, as we as the expertise to find a way out and solve the problematic issues. For issues concerning the stakeholders and the investors, the product owner should take a proactive approach in availing the clarifications regarding the acceptance criteria, and guide the team in proceeding with the user stories. In scrum, it is essential that the team feels responsible, and undertake the responsibilities in a proactive manner.

Working and shippable software takes precedence over documentation and marketing concerns
The main purpose and objective of scrum is to produce shippable products through iterations know as sprints. The entire development of the product occurs in sprints. At the end of each sprint, the product owner verifies the quality of the development carried out by the team, and adjudges the completed user stories, whether they comply with the acceptance criteria. It is imperative that sprints deliver shippable products which fulfill the stakeholder’s vision of a successful marketable product. The documentation required to “manufacture” the product, such as the project analysis report, project design, testing and documentation of the results, creating user manuals and technical specifications etc. are important too, but the actual development through the sprints, and churning out shippable products at the end of sprints is more important and precedes the documentation associated with the development.

Collaborating with the customers more important than contracts and legal documentations
The product owner is the main entity which functions as the main point of contact between the team and the stakeholders, as well as the end users of the product. The product owner collaborates with the team, and determines what needs to be done next to make the project a distinct success. A primary responsibility is to ensure that the product maintains the highest possible market value at all times, even while it is being developed. This is the most critical aspect of scrum.

Transparency and taking proper decisions at the right time and the right manner
Scrum stresses heavily upon transparency and sharing information. The entire scrum process is designed to facilitate the flow of information and increase the transparency. Each team member should have access to the required information. They should have access to proper data and important information, so they can make informed decisions and fulfill their responsibilities in a proper and effective manner. Each aspect associated with the scrum process – including the product backlog and user stories – should be made available at all times so that the product increment through sprints is availed as per production plan and schedule.