Agile & Scrum Project Management Course: Six Figure Salary

You will learn all about what agile actually is.

Terms: Agile, Agile Manifesto & Agile mindset.

In this lecture, you will learn the four agile values that are derived from the Agile manifesto

Attached is an agile term matching activity that will help you familiarize with important agile definitions

In this lecture, you will learn the 12 principles of agile framework with easy examples.

In this lecture, you'll learn the benefits of using agile and how it is better than traditional project management approaches.

In this lecture, we'll explore some of the challenges associated with Agile.

Since scrum is the most popular Agile framework, in this lecture, we'll learn the basics of scrum and some terminologies.

In this lecture, you will learn the five values of scrum: openness, focus, courage, commitment, respect

There are three main roles in scrum: Scrum Master, Product Owner and the Development Team. In this lecture, you'll get an overview of these three roles.

In this lecture, we will explore the scrum master role in depth and talk about responsibilities of a Scrum Master.

In this lecture, we will explore one of the most important roles in a scrum team: The product owner.

In this lecture, we will discuss the development team roles: Developers, Quality Analysts, Business Analyst, UI/UX desginers.

Backlog refinement is like making a to-do list for a big project. Imagine you have a list of tasks you want to complete, but they're not all clear or ready to do just yet. That's your backlog. Refinement is when you take a closer look at each task/user story on your list.

In this lecture, we'll explore the concept of User stories ( A key aspect of scrum)

Let's explore the concept of acceptance criteria for user stories. Think of acceptance criteria as a checklist or a set of requirements. They help you determine if a job is done the right way.

Attached is a downloadable resource to provide you with examples of user stories so you can practice on your own.

In this lecture, we'll explore the 2 keys artifacts in Agile scrum: Product Backlog and Sprint Backlog.

In Scrum, working agreements are a set of guidelines or rules that the Scrum team creates and agrees upon to help them work together effectively and efficiently.

The "Definition of Ready" focuses on ensuring that backlog items are well-prepared and understood before they are brought into a sprint, while the "Definition of Done" sets the quality and completeness standards that must be met for work to be considered finished within the sprint.

In this lecture, you'll learn about what a product increment is and how it's used in Agile Scrum.

In this lecture, you will learn what a sprint is and it's importance in Agile and Scrum.

A Daily Standup Meeting, also known as a Daily Scrum or Daily Standup, is a short and daily meeting designed to keep the Scrum Team aligned, informed, and focused on the current sprint's goals.

A Sprint Planning Meeting is a key event in Scrum, an agile framework for software development. It is a time-boxed meeting where the Scrum team gathers to plan the work they will complete during the upcoming sprint, which is typically a fixed time period, often two to four weeks.

The primary purpose of the Sprint Review is to inspect the work completed during the sprint and gather feedback from stakeholders.

The primary purpose of the Sprint Retrospective is to reflect on the recently completed sprint and identify ways to improve the team's processes, practices, and collaboration.

In this lecture, we explore the concept of estimating how teams estimate their work.

We'll explore the difference between traditional project estimating and agile estimating.

We'll talk about why estimating is important in project management.

We'll talk about the different estimation techniques that can be used in project such as the Fibonacci sequence.

In this lecture, we'll explore the dot sticker estimation technique in Agile Scrum.

In agile methodologies like Scrum, team velocity is a measure of the amount of work a team can complete in a given time frame

In Scrum, a burndown chart is a visual tool used to track the progress of work during a sprint (or iteration).

In this lecture, we will learn the basics of kanban methodology.

In this lecture, we go over the kanban board and it's basics.

In this demo, you'll watch a demo of a free kanban tool called Trello.

In this case study, we'll explore a real world scenario where the scrum master is facing resistance from the team when implementing the scrum framework in an organization.

In this case study, we'll explore a real world situation where scrum team members are underperforming and how to handle this scenario.

In this case study, we'll explore a scenario where the scrum team is repeatedly overestimating the work they can do which is results in missed deadlines. We'll look at the causes and how a scrum master can solve these issues.

In this case study, we'll explore a scenario where the scrum doesn't show any excitement towards a sprint retrospective meeting and how can a scrum master deal with unmotivated team.

In this case study, we'll explore a scenario where a product owner role is frequently changed within the scrum team which results in challenges for the entire team.

In this scenario, the scrum team members are tired and facing burnout due to high volume of work. Let's find out how a scrum master should handle this situation.

In this case study, we'll explore a scenario where an organization is transitioning over from traditional waterfall framework to SCRUM framework.

In this session, we'll explore integrating quality assurance processes into the scrum team.

In this case study, we'll explore a scenario where a scrum team is dealing with conflicting priorities.

In this scenario, a scrum team is facing challenges in delivering consistent results and they need to improve their velocity.

In this case study, the scrum team is facing a scenario where they are faced with unclear requirements and user stories.

In this case study, we'll explore the dynamics between the senior management and the scrum team.

We'll look at the challenges faced by a scrum team where the team members are spread across multiple time zones.

This is a scenario where a scrum team is facing unexpected spikes in their workload and how they utilize kanban to solve it.

In this case study, we cover a scenario where a scrum team is in a time-constrained project where they have to deliver results in a fixed timeframe.