Welcome to the next module. He will start our detailed discussion on Scrum. Scrum is founded on empirical process control theory. empiricism asserts that knowledge comes from experience and making decisions based on what is known. The empirical model of process control provides an exercises control for processes that time perfectly defined and generates unpredictable and unrepeatable outputs. This is done through frequent inspection and adaptation.

There are pillars of empirical control, they are transparency, inspection, and adaption. We do inspect and adapt throughout the duration of the project, formal events defined in Scrum sets the minimum frequency for this Scrum guide days. Scrum users must frequently inspect Scrum artifacts and progress towards a sprint goal to detect undesirable variances. Their inspection should not be so frequent that inspection gets in the way of the work. inspections are most beneficial when diligently performed by skilled inspectors at the point of work. If we go for a definition from the scrum guide, it states Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

Scrum is a lightweight framework, which is simple to understand but difficult to master. Scrum works with iterations or Sprint's of Max one month duration. As we stated before, Scrum emphasis on self managed cross functional teams ensures continuous flow of value to customers through iterative incremental development and delivery. It follows adaptive rather than predictive planning. It promotes collaboration among all parties involved. We can summarize basics of Scrum.

Scrum is an iterative and incremental Agile software development framework for managing software projects and product or application development. Sprint is a time boxed iteration during which a potentially releasable product increment is created. design, build and test activities are performed with Within sprint, Sprint duration is maximum of one month. There are values commitment, courage, focus, openness and respect. People personally commit to achieving the goals of the scrum team. The scrum team members have courage to do the right thing and work on tough problems.

Everyone focuses on the work of the sprint and the goals of the scrum team. The scrum team and its stakeholders agree to be open about all the work and the challenges with performing the work. scrum team members respect each other to be capable, independent people. Let's start with Scrum processes. Every software project is intended to convert a number of requirements into working software and increment or change Scrum follows an iterative and incremental approach. The work is carried out in multiple iterations called sprints.

Sprint is a time boxed to a maximum of one month. The purpose of the sprint is to create a potentially shippable increment of working software. Before getting into the details of this process, let's discuss different roles defined in Scrum. The development team consists of professionals who do the work of delivering a potentially releasable increment of done product at the end of each sprint. Only members of the development team create the increment. development teams are self organizing.

They decide how they're going to create a shippable increment. At the end of the sprint. development teams are cross functional. They have all the skills required to convert the selection requirements into the done shippable increment. The product owner is responsible of maximizing the value of the product resulting from work of the development team. He owns the requirements.

This activity consists of detailing backlog items, ordering or prioritizing it to maximize the value and clearly communicating them to the to the team. He also reviews and accepts or rejects the increment produced by the team. The Scrum Master is a servant leader, a facilitator and a coach. The Scrum Master is responsible for promoting and supporting Scrum. Scrum masters do this by helping everyone understand Scrum theory practices, rules and values. He or she ensures that the scrum is understood and enacted by the team.

He or she facilitates the scrum events as required. Scrum Master make sure that the impediments for the development are removed The product owner, the development team and the Scrum Master, together referred as the scrum team. Product Backlog captures all the requirements needed to be included in the product. This is created and maintained by the product owner. The product backlog is an ordered list of everything that is known to be needed in the product. Sprint start with a sprint planning meeting.

This is time boxed to eight eight hours for one month sprints for shorter Sprint's it's a usually shorter product owner explains the product backlog items and sets the priorities development team select items for upcoming sprint based on their capacity. Team velocity. The size of the work that they have successfully delivered sprint helps as a guideline while deciding their capacity for the next sprint. Together the scrum team agree upon the sprint goal. And the second part of the planning meeting, the team creates an initial plan for converting the selected items to a shippable increment. This may be in the form of technical tasks for each selected item, or may only be four items to start with.

The selected backlog items with a plan for achieving it make the sprint backlog. The development team owns the sprint backlog and keep it updated throughout the sprint. The development team stopped working on the selected backlog items towards creating the increments to achieve the sprint goal. They do design, development and testing all in the same sprint. They will do whatever required to achieve the sprint goal. Every day, the development team does a daily Scrum meeting.

This is a 15 minutes duration. This takes the form of a stand up meeting where the development team collaborate and decide action has to be done before the next daily Scrum. It's this kind of a quick daily planning. Normally it takes a form where every member answers three questions. What I have done since last daily Scrum for achieving the sprint goal, what I'm going to do till next daily Scrum, am I seeing any threats for the sprint goal? At the end of the sprint the scrum team and other stakeholders as invited by the product owner conduct a sprint review.

This is time box to box to a four hours for one month sprints for shorter Sprint's It is usually shorter. During the sprint review, the scrum team and stakeholders collaborate about what was done in the sprint based on that and any changes to the product backlog during the sprint. Attendees collaborate on the next things that can be done. This is an informal meeting, not a status meeting. And the presentation of the increment is intact. to elicit feedback and foster collaboration.

The Sprint Retrospective is an opportunity for the scrum team to inspect itself and create a plan for improvements to be an active sprint. This is time boxed to three hours for one month sprints for shorter Sprint's It is usually shorter. There are different methods use for retrospectives. For example, the team may try to find out what went well. What didn't go well. What are the areas of improvement.

Both sprint review and Sprint Retrospective may have outcome that impact the next sprint planning. A new sprint starts immediately after the previous sprint ends. There is no gap in between Scrum teams conduct sprints one after the other, creating software increments in iterative and interactive Mental way. As mentioned before, the development team create tested and shippable increment at the end of each sprint. It may get deployed as it is or wait for further increments. However, the development team will keep on producing shippable increments.

So, we have discussed different rows, events and artifacts in Scrum. This is a quick visit. We will discuss these in details in coming modules. As we have already seen, there are three rows three artifacts and four ceremonies in Scrum, the Roza product owner, development team and the scrum master. The ceremonies sprint planning daily Scrum, Sprint review, Sprint retrospectives, the artifacts or product backlog, sprint backlog and the increment