Waterfall Methodology vs Agile
Hi. In today's session let's go over the basics of agile and scrum. Agile methodology teaches to break down work in chunks due to much unknown, done for the first time work. Under the umbrella of agile methodology there are two main types of team work processes: kanban and scrum. When we work in dev support we often times use a kanban board with kanban flow - moving tasks from "to-do" to "done" state. And this flow of tasks doesn't really end or change.

The second and most popular option - scrum. It's a set of tasks connected to functionalities that the team is working on. The work is broken down to sprints/iterations of 1 week to a month (2 week iteration is the most common).

A new Sprint starts immediately after the conclusion of the previous Sprint.
To ensure Sprint success you need to keep in mind the 12 Basic Rules in Scrum:

Every Sprint is Four Weeks or Less in Duration
There are no Breaks Between Sprints
Every Sprint is the Same Length

The Intention of Every Sprint is "Potentially Shippable" Software
Every Sprint includes Sprint Planning

The Sprint Planning Meeting is Time boxed to 2 Hours / Week of Sprint Length. Not all teams and companies follow this rule.

The Daily Scrum occurs every day at the same time of day

The Daily Scrum is time-boxed to 15 minutes. Now, in reality we often set up a 30 min standup to also include anything that is put in a parking lot. This means various topics that need more discussion

Every Sprint includes Sprint Review for stakeholder feedback on the product
Every Sprint includes Sprint Retrospective for the team to inspect and adapt
There is no break between the Sprint Review and Retrospective meetings. Also, not all teams follow this rule.

All photo and video materials belong to their owners and are used for demonstration purposes only. Please do not use them in commercial projects.