Created in the early 1990s by co-creators Ken Schwaber and Jeff Sutherland. It is the most known framework as Agile Software Management for project management.
A lot of companies adopt Scrum, as having a great result in the market, and provides services to adapt the better product which fits with customers.
What is Scrum
The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules.Definition in the Scrum guide : “Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.”
Scrum theory :
“Scrum is founded on Empirical Process control Theory, or Empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known.”Scrum Guide
In an empirical process, information is gained by observation, rather than prediction. We also know empirical processes are best for complex problems, where there is more that we do not know than we do know.
As framework Agile, Scrum is the courage to be honest to admit that building software is complex and it can’t be perfectly planned since required change .
It all begins by getting the goal right : the purpose is to satisfy clients.
In fact, the Scrum Framework is made up of time-boxed events , roles , and rules. The framework is very simple to understand, but hard to implement.
Let’s go through each its component:
Artifacts
Artifacts are tools that are made for solving a problem. In Scrum there are three artifacts are a product backlog, a sprint backlog, and an increment with the definition of done.
Product Backlog is an ordered list of work that needs to get done to create and maintain a sustainable product , managed by the Product Owner. It is the team’s “to do list” .
The product backlog consist by
Sprint Backlog is the list of items, user stories or beg fixes, selected by developers for implementation in the current sprint.
Increment is the sum of all the product backlog items completed during the sprint and the value of the increments of all previous sprint. It is the end- product from a sprint.
Roles :
Three roles are Scrum Master, Product Owner, Developers. Three of them consist of the Scrum team.
Scrum Master : A person who is responsible for Scrum application.
Product Owner : A person not a committee responsible for
Developers : group 3 to 9 of professionals responsible for creating the project deliverables, together with the rest of the Scrum team.
Rules
Events
Scrum defines four events(sometimes called ceremonies) that occur inside each Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
Sprint planning : is a time-boxed event of 8 hours or less. During this event, the entire Scrum Team collaborates and discusses the desired high-priority work for the Sprint and defines the sprint Goal. The Scrum Master’s role is fundamentally to facilitate the meeting . The product Owner describes the objective of the Sprint and as well as answers questions from the Development Team(or Developers ) execution and acceptance criteria. The developers (or developers team) has the final say in how much of the high-priority work it can accomplish during the Sprint. The sprint Planning is attended by the entire Scrum team.The Scrum Team consists of the developers, the Scrum Master, and the Product Owner.
Daily Scrum : 15minutes time-boxed event for the development team. The Daily is held every day during the sprint, at the same time and place each day to reduce complexity.
Sprint Review : 4hours Time-boxed event or less, to conclude the development work of Sprint. It is attended by the Scrum team and the stakeholders. It serves to inspect the increment of product resulting from the sprint and update the product backlog in order to maximize the value of the next period.
Sprint Retrospective : 3 hours time-boxed for a sprint of 4 weeks, to end a sprint. It serves for the Scrum team to inspect the past Sprint and plan for the improvements to be approved during the next sprint.
Why is it used
Reason why Scrum is awesome, is
Scrum
- offers freedom of implementation
- is easy to learn and use
- embrace the change
- reduces the risk building the product by increments
- optimized the team’s efficiency and efficacy
- lets the customer to use the product
How does it work
The Scrum started by the Product Owner who represents customers and others stakeholders has an idea.The Product Owner drives the backlog, prioritised dynamics list of all the work may be needed for the product. The work is done by a self-organizing development team during the sprint. The sprint is a period one to four weeks.
During the sprint planning based on the sprint goal the sprint backlog is created.
With the definition of done is in place the development team works together to deliver values. One the day the development team meets for 15 minutes for the Daily Scrum to inspect and adopt the progress toward the sprint goal and to surface dependencies or impediments.
Who makes sure the Scrm is understood and acted is the Scrum Master. Is the servant leader of the Scrum team and helps everyone understand Scrum theory, practices and rules.
As the team works towards the Sprint goal the increment grows iteratively allowing the team to inspect and adopt empirically based on progress.
To improve transparency the increment can be released continuously during the sprint.
At the end of the sprint, the scream invites the stakeholders to the sprint review where they collectively inspect the results.
After the sprint review, the team runs the sprint retrospective where they evaluate how they worked and build the plan for how to improve.
The Scrum provides an empirical foundation for teams enabling them to deliver more frequently with higher value and better outcomes to customers.
Vestibulum lacinia arcu
Scrum is founded on Empirical Process control Theory, or Empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known.
Aenean lectus elit, fermentum non, convallis id, sagittis at, neque. Nullam