Scrum
Scrum is an agile framework for the development of products and services. This approach defines a flexible strategy for the development of products and services. This framework has a very flexible and easy-to-implement nature. Consequently, most people use the framework turning her into the most commonly used agile framework in the world.
People can distinguish Scrum by:
- Firstly, instead of a sequential approach, the team used progressive development to deliver products or services. The team will then improve iteratively and incrementally the products and services.
- Secondly, instead of a top-down hierarchy, teams organize themselves
- Finally, instead of hierarchical, written, and formal communication, the teams work physically in the same physical space. As a result, communication is daily and face-to-face between all team members.
Scrum Framework Key Principles
A key principle is a recognition that the client can and will change their mind. In other words, they will change their minds about what they want, how they want, and when they want it. Consequently, no one can expect that the team will manage requirements in the traditional way. In other words, in a predictive and planned way.
As such, the methodology adopts an empirical evidence-based approach. In other words, it accepts that the problem cannot be fully understood or defined entirely.
Finally, the idea is to maximize the team’s capacity to deliver quickly. The team must also respond quickly to new needs and changes.
Scrum Methodology Bases
Scrum is based on the fundamentals and principles of the agile methodology. Moreover, the approach is based on a set of values and principles. That set is documented in the agile manifesto, written in 2001 and signed by 17 signatories.
To assure that the approach works is essential that the team and all stakeholders understand and respect it. To ensure that the approach works, it is essential that the team and all stakeholders understand and respect it, including the way it approaches problems and solutions. For this, the work of the scrummasters is essential. His responsibility is to explain to the team, organization, and other stakeholders how they can behave and how scrum works.
Why do we name this framework Scrum?
When Jeff Sutherland created the Scrum process in 1993, he used the term “Scrum” after seeing an analogy in a 1986 study by Takeuchi and Nonaka published in the Harvard Business Review. In that study, Takeuchi and Nonaka compared the high performance of cross-functional teams with the scrum formation used by Rugby teams.
Scrum History
The founders of this Scrum framework created it to manage software development projects. Later, practitioners gradually adopted the framework in multiple contexts of iterative and incremental product development. They used scrum to develop components in small increments (incremental approach), that can be refined in future iterations (iterative approach).
The framework assumes that the project teams’ environment is uncertain and volatile and that, therefore, they should not define the product requirements or work processes upfront in detail. Instead, project teams must embrace constant changes to the products, in order to maximize the value delivered by the project. They must also adopt empirical processes, which can be easily and continuously inspected and adapted based on practical experience.
This framework adopts a set of events (e.g., sprint, sprint planning, daily scrum, sprint review, and sprint retrospective), artifacts (e.g., product backlog, sprint backlog, and increment), roles (e.g., scrum master, product owner, and development team), values (e.g., commitment, courage, focus, openness, and respect) and concepts (e.g., the definition of done, the definition of ready, sprint goals, product backlog grooming, story points, scrum of scrums, transparency, inspection, and adaptation).