Agile Scrum Fundamentals

All project management methods do have their own values that are accepted and respected by the team that follows the rules of that methodology. The same thing will be applied for Scrum, as well: As a candidate who wants to learn this technique in detail, you have to understand the Scrum values. This lecture aims to cover:

• The own values of Scrum;

• The definition of Commitment and Respect and

• The definition of Focus, Openness and Courage

After learning about the Scrum values, we can give a turn to the roles and responsibilities for each member in management of project with Scrum. In this lesson, we will go over:

• Scrum Roles;

• Team members and their responsibilities, Product Owner, Scrum Master, Development Team and

• The internal and external Scrum project

You are almost ready to become a member of Scrum team, because you know all roles and their responsibilities, but what about the famous Scrum events? Here in this lecture, you will learn the importance of Scrum events by looking through:

• How Scrum project works;

• Nature of Scrum events and

• Time Box concept

As this section is dedicated to the Scrum events, you will get into the details of all necessary contributors. The first you start with is the Sprint which is the basis of project and holds organization of all Scrum events. This session aims to go over:

• The question of "What is Sprint?"' and

• Important notes about Sprint

After defining the length of your Sprint for the project, you will have to organize the meetings or events. The first and most important one will be Sprint Planning where the planning of what will be done during the Sprint is made and Development Team gets into the details of what is required. In this lesson, you will learn about:

• What is Sprint Planning?;

• Scope of Sprint and

• The order of items in the backlog

Another necessary event is called Daily Scrum that is normally held by Development Team and as can be seen from its name, it should be followed daily by team members. The purpose of this meeting is to inform all development team members that who works on what. So, are you ready to get into the following topics in this lesson?

• What is Daily Scrum?;

• Daily Scrum as an effective tool and

• How to hold this event

Let's consider that you and your team did complete all the things during the sprint. So, then which step should be followed to check whether the work is over not. This time, organization of Sprint Review will help the team members that whether they have satisfied the requirements or not. Then, to increase the quality of team work another meeting, Retrospective can be followed by entire team. In this session, we will go through:

• What is Sprint Review/Retrospective and

• The purpose of Sprint Review/Retrospective

Scrum is more than the specific iterative development. Scrum artifacts are the results or products of our management activities which are designed to increase transparency of information related to the delivery of the project, and provide opportunities for inspection and adaptation. This lecture aims to deliver the helpful information about:

• Necessity of Scrum Artifacts;

• Product and Sprint Backlog;

• Definition of "Done" and

• Progress towards a Goal

Till now, you have obtained comprehensive information about Scrum Values, Events, Team and member responsibilities, now it is time to go for the one of Scrum artifacts called "Product Backlog" which mainly keeps the items will be delivered by development team. In this lesson, you will be aware of:

• Elements of Product Backlog;

• Sample set of Product Backlog;

• Product Backlog Grooming and

• How to start a Product Backlog

As Product Backlog is the place for the items to deliver throughout entire project, Sprint Backlog will be subset of that comprising the items that have to be delivered by Development Team only during the current Sprint. This is another essential Scrum Artifact so that, get into its details provided in this session:

• Creating Sprint Planning;

• Iterative Planning on Spring Backlog and

• Its implementation on specific project

Now, we move on the part where the items are completed and waiting for being checked or reviewed by Product Owner and even stakeholder. This time, we will have to understand meaning of an Increment which is a sum of all completed Product Backlog items at the end of a Sprint. This lesson covers the fundamental knowledge about:

• What is Increment?;

• Definition of Done;

• Burn-down Chart and its derivation and

• Monitoring Sprint Progress

Cool! You have almost completed the course, but here you have a course overview video that includes the most significant parts of Agile Scrum Fundamentals training and can be helpful for you get prepared for Self-Assessment test provided by our trainers team. Watch it and come for the Self-Assessment journey!