Mastering Agile Scrum Workshop
4.0 (154 ratings)
Course Ratings are calculated from individual students’ ratings and a variety of other signals, like age of rating and reliability, to ensure that they reflect course quality fairly and accurately.
25,968 students enrolled

Mastering Agile Scrum Workshop

Learn Agile Scrum Master Concepts for 2020 & 2021
4.0 (156 ratings)
Course Ratings are calculated from individual students’ ratings and a variety of other signals, like age of rating and reliability, to ensure that they reflect course quality fairly and accurately.
25,968 students enrolled
Created by Tanmay Panchal
Last updated 7/2020
Current price: $139.99 Original price: $199.99 Discount: 30% off
23 hours left at this price!
30-Day Money-Back Guarantee
This course includes
  • 3 hours on-demand video
  • 48 downloadable resources
  • Full lifetime access
  • Access on mobile and TV
  • Certificate of Completion
Training 5 or more people?

Get your team access to 4,000+ top Udemy courses anytime, anywhere.

Try Udemy for Business
What you'll learn
  • The Difference between Traditional Waterfall Project Management Methodology and Agile Scrum Project Management Methodology
  • Know Agile Scrum methodology
  • Why Agile Scrum is most powerful?
  • Other Agile Frameworks, best practices, roles, challenges, etc
  • Scrum Concepts, Fundamentals, Artifacts, Roles, Pillars, Values, Lifecycle
  • Agile Estimation, Plan, Monitor and Control
  • Agile on Complex Projects
  • Should have minimum 2 years of project management experience
  • Should know basics of Software Development Life-cycle (SDLC)
  • A Laptop, PC, Tablet, Smartphone or Smart TV
  • A Good Pair of Headphone

UPDATE FOR 2020 & 2021 with Tanmay's latest knowledge on Agile Scrum Certification!

This course is about learning the latest Agile Scrum methodology for the Software development field. In this course, you will learn all other Agile methodologies along with detailed information on Scrum.

By this course, experienced project managers can grow in their careers and get the next level of opportunity as an Agile Scrum Master and the junior team members can learn the process of the Agile Scrum methodology.

The biggest target audience is at any experience level who wants to learn Agile Scrum in detail and apply in the career!!!

Who this course is for:
  • Project Managers who would like to be an Agile Scrum Master
  • Qualifying Agile Scrum Master Certification Exam
  • People who want to learn about Agile Scrum
  • Developers, BAs, Architects, Analysts, Designers, Managers, etc
Course content
Expand all 49 lectures 02:46:46
+ Introduction
2 lectures 08:38

Welcome to the Agile Scrum Master Workshop

My name is Tanmay Panchal and I am the Agile Scrum Master Professional

I have over 22 years of project management experience in the IT sector, the public sector and as an Entrepreneur

What is important for you, I have over 15 years of experience in Exam preparation coaching

Preview 01:09
  • To become an effective Scrum Master

  • and pass the Agile Scrum Master Exam

  • You will acquire the knowledge and insight necessary to lead an Agile and Scrum Adoption efforts in your organization

  • You will learn how to be an effective servant leader who can assist your team to adopt and utilize the best practices of Scrum and become a high performing team

  • You will learn about Agile in terms of project management approach and other methods in addition to Scrum

  • You will also learn the value DevOps processes brings through the Agile transformation and establish the link between Agile project management and the management of business services they enable

Over 50% of Agile project use Scrum making Scrum the most popular Agile method

Agile is a project management approach that is well suited for the projects that are complex and uncertain

You will learn key concepts

This course will also provide guidance about

  • How to apply Scrum concepts to your organization?

  • You will learn how Scrum as value to the development through which you can deliver your high-quality products

  • This course covers the role, ceremonies, and artifacts of Scrum

  • As well as best practices of Scrum methodology

Anybody who is looking to update their knowledge of the software development project management approach will be beneficial from this course.

It is advisable that the participant has some background of the project management but it is not mandatory or compulsory.

Course Value

As a project management professional, you can derive value from this course in multiple ways

  • You learn best practices for Scrum and other Agile methods

  • You will gain deep insight into Scrum and discover new ways of leading project management teams and delivering values to customers

  • You will receive practical guidance on how to implement these practices within your organization and how to maximize their value

  • It positions you well to be an evangelist and champion in the Agile adoption journey for your organization

Topics Covered in this Course

These are the topics covered in the course

  • We will define what Agile is. Review the Agile manifesto, 12 supporting principles in Agile. We will also explore the journey as a successful Agile and Scrum adoption.

  • We will cover the Waterfall project management approach as well as becoming familiar with a number of other agile frameworks including Lean, XP, Kanban, Crystal, and DSDM. We will also cover how DevOps as an engineering discipline compliments Agile by accelerating the delivery and deployment of valuable software. Furthermore, we will review how agile should be linked with IT service management.

  • We will cover scrum value, scrum pillar, scrum lifecycle, and scrum ceremony including sprint planning, daily scrum, sprint reviews, and spring retrospectives. We will also cover various scrum artifacts including the product backlog, sprint backlog, and release backlog.

  • We will cover scrum roles. A product owner, the scrum master, and the development team. We will focus more on the scrum master role including some of the dos and don’ts.

  • We will cover the user stories, epics, and user story part. We will talk about the product roadmap as well as the release and sprint plan. We will also cover the estimation techniques including story points and ideal time. We discuss planning poker and affinity estimates. Will talk about information radiator and communicating project progress and status including burndown chart, burn-up charts, and other information radiators. We will also talk about a scrum team that stays in control of the project work by making form decisions in a collaborative way with key stakeholders.

  • We are going to explore some of the common challenges and counters while scaling agile for use in large projects. To explain the scrum of scrum works and as well how product co-ordination teams and feature teams co-ordinate the work of multiple teams working on a single project. Will explain how scrum is implemented in a distributed environment. We will talk about the SAFe framework and how to scale agile. Will talk about system thinking and determining when agile should be used and when it should not be. Will cover how tools can be used in Scrum to improve performance.

  • Will deal with how to achieve Agile adoption in our organization. Will learn about different approaches to conduct the transition. We cover the changes necessary to the organization's culture and ecosystem to enable agile for the try. Specifically, we discover how to empower the self-organizing team, a foundational concept in Agile.

Preview 07:29
+ Agile - Thinking
4 lectures 17:06

Welcome to this session of Agile Scrum Master Workshop

The purpose of this session is to introduce you to Agile as a Project Management Approach & Scrum as an Agile method.

After completing this session,

  • You will be able to define what both Agile and Scrum is

  • You will be able to articulate the benefits of being Agile

  • You will be familiar with the Agile Manifesto and its supporting 12 guiding principles

  • Also, you will understand the concept of continuous improvement within the concept of Scrum adoption

There are two main approaches to managing project – There is the Waterfall Approach and the Agile approach.

Will talk about the Waterfall approach later in the workshop but to summarize, it involves the big planning upfront in order to determine the detail scope of the project and establish the project’s performance base lines.

Once executing begins, actual results are compare to the base lines in order to determine the health of the project.

The Agile approach is for the projects that are more complex and uncertain. In Agile, there is no heavy detail planning upfront. Rather in Agile project evolves as short increments are completed.

One of the top leaders in the Agile world – Scott Ambler defines Agile this way:

“Agile is an iterative and incremental evolutionary approach to project development which is performed in highly collaborative manner by self-organizing teams with just enough ceremony that produces high-quality software in a cost effective and a timely manner which meets the changing needs of its stakeholders.”

- Scott Ambler

Agile Definition – Agile software development describes an approach to software development under which requirements and solutions evolve through the collaborative effort of self-organizing and cross-functional teams and their customer(s)/end users(s).

It advocates adaptive planning, evolutionary development, early delivery, and continual improvement, and it encourages rapid and flexible response to change.

SCRUM Definition – Scrum is a framework for project management that emphasizes teamwork, accountability and iterative progress toward a well-defined goal. The framework begins with a simple premise: Start with what can be seen or known. After that, track the progress and tweak as necessary. The three pillars of Scrum are transparency, inspection and adaptation.

Agile is a family of light weight, quality-driven approaches to software development which evolved in the late 1990’s and response to the burden of heavy documentation and frequent change

In Feb’ 2001, 17 leading software developers signed the Agile Manifesto.

Preview 04:32

The Agile Manifesto is a foundational document of all Agile methods and it reads like this.

We are in covering better ways of developing software by doing it and helping others do it.

Through this work we have come to value:

  1. Individuals and interactions over processes and tools

  2. Working software over comprehensive documentation

  3. Customer collaboration over contract negotiation

  4. Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Let’s take a look at the four main points in the Manifesto

1. Individuals and interactions over processes and tools – Means valuing people more highly than processes or tools is easy to understand because it is the people who respond to business needs and drive the development process.

2. Working software over comprehensive documentation – Agile does not eliminate documentation, but it streamlines it in a form that gives the developer what is needed to do the work without getting bogged down in details.

3. Customer collaboration over contract negotiation – Agile has the value of customer collaboration throughout the development process. This meant the customer will be involved at regular intervals for periodic demos, daily part of the team, and attending all meetings.

4. Responding to change over following a plan – With Agile, the shortness of an iteration means priorities can be shifted from iteration to iteration and new features can be added into the next iteration. Agile’s view is that changes always improve a project; changes provide additional value.

There are also 12 guiding principles that support Agile Manifesto:

  1. Highest priority is to satisfy the customer through early and continuous delivery of valuable software.

  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter time scale.

  4. Business people and developers must work together daily throughout the project.

  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

  7. Working software is the primary measure of progress.

  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

  9. Continuous attention to technical excellence and good design enhances agility.

  10. Simplicity – the art of maximizing the amount of work not done – is essential.

  11. The best architectures, requirements, and designs emerge from self-organizing teams.

  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Agile - Manifesto and 12 Guiding Principles
  • In 1986, the scrum was first introduced by Hirotaka Takeuchi and Ikujiro Nonaka.

  • They described it as a new approach to commercial product development that will increase speed and flexibility. They actually called it a rugby approach.

And then in early 1990, this method was first referred to the single word – SCRUM

SCRUM is approved as an Agile software development method providing significant benefits over the traditional waterfall approach.

For example,

  1. Higher productivity and lower development costs – this is accomplished by reducing waste and irregularities by only developing what is absolutely essential for the customer.

  2. Improved stakeholder satisfaction – a collaboration between the developers and the customer results in clarity about what is to develop and the ability to respond to changing needs and priorities which leads to actually delivering the value the customer wants.

  3. Higher quality software – using techniques like test-driven development, continuous integration, acceptance test-driven development, and refactoring can lead to nearly defect-free software.

  4. Improved employee engagement and job satisfaction – by empowering a team to be self-organizing, the team is able to determine how it is going to deliver the value to the customer and establish a sustainable pace forever.

  5. Faster time to market and early ROI – By incrementally delivering value or working software to the customer in short iterations, working software can be deployed sooner and the customer can realize an early return on investment.

Scrum is now the leading agile method with more than 50% of agile projects using SCRUM.

Features that make scrum so popular:

  • It offers simplicity and proven results

  • Other agile engineering techniques

  • It emphasize small teams and team empowerment

  • It welcomes changes to requirements

  • It allows working from a single source of prioritizing work items

  • It includes daily status meetings

  • It offers team commitment to the potentially shippable software at the end of each sprint

The chart illustrates how the agile method delivers value faster. In the traditional approach, the chart on the right - you can see that the customer has to wait until the end of the project for the delivery of the working software and the realization of the return on investment.

Scrum: Delivers value at the end of each Sprint.

Looking at the chart on the left, you can see how value is delivered clearly and incrementally at the beginning of the project.

Adopting Scrum can be an effort that takes some time. There is likely to be some organizational gravity that resists the adoption of Scrum. So it is going to be helpful to ask some key questions:

  • Has the investment in scrum paid off?

  • What is our next area of improvement?

  • Should we continue with Scrum?

  • Are we better off than before?

  • Are we reproducing better products?

  • Do our products have fewer defects?

  • Are we able to ship faster than before?

    The answers to these questions do not need to be necessarily arrived at through a precise or scientific effort. However, testing and measuring the results of any effort is necessary to discover whether or not we have been successful.

Advantages of SCRUM
  • Agile is an iterative, incremental method for developing products

  • Scrum is the most popular Agile methodology

  • Scrum provides value to the organization in the form of higher productivity, reduced cost, better quality, and more engaged and satisfied employees

  • Scrum relies on frequent feedback and experimentation resulting in better predictability and flexibility

  • The actual results of SCRUM adoption should be tested and measured

Preview 01:17
4 questions
+ Agile - Other Frameworks
10 lectures 28:19

Welcome to this session.

  • After completing this session, you will be able to explain the features, strengths, and limitations of software development using approaches including the traditional Waterfall as well as various Agile methods including Lean, Extreme programming, Crystal, and DSDM.

  • You will also be able to describe the role of DevOps as a discipline that is critical to the success of Agile teams

  • You will also understand how to apply agile methods to IT service management

Any method which is incremental & iterative is inherently Agile. Under the Agile umbrella, is a family of methods including:

  1. Scrum

  2. Extreme Programming

  3. Crystal

  4. Kanban

  5. Lean

  6. Feature-Driven Development

  7. Dynamic System Development Methodology (DSDM)

All of these methods Share Agile practices and values, like

  1. Embracing change

  2. Lightweight or lean documentation

  3. Daily Stakeholder collaboration

  4. Incremental Delivery and

  5. Continuous improvement

Agile - Other Frameworks

Before we talk about some agile methods, let’s review the traditional software development life cycle when using a Waterfall approach. This approach is called waterfall because of the series of steps to create the final product.

You can see that the initial step is to collect all of the requirements necessary. That’s followed by Design phase which is where the software structure determines then in the Implementation phase the software is actually developed

In the Verification phase, the software is tested both for correctness and acceptance. And then once the software is being deployed, there is the Maintenance phase.

This traditional approach is perfectly suitable and logical for project management. However, when it comes to software development where there is a high level of complexity, uncertainty, challenges

  • Dealing with change

  • Change is not only difficult. It’s very expensive. For example, if you discover critical design flow during verification or get the requirements to change during implementation,

  • The amount of rework needed to correct this can be probative.

The result is a tendency to resist change which intern compromises the spirit of customer collaboration.

If you have a project that is very clear in terms of its requirements and is unlikely to experience too many changes.

The waterfall can be a reasonable and effective approach for projects to simply migrate features or products from one platform to another. Keep in mind that both the problem and the solution must be clear for this approach to be a good choice.

Let’s look at some Agile methods and see how they are likely a better fit for projects that are complex and uncertain. Like software development.

Waterfall Approach Challenges

XP was developed primarily to

  • Respond to the high cost of changing requirements and

  • Establish strong engineering practices to improve the quality of software and then take them to the extreme. For example

  1. If testing is good, let’s do unit testing, integration testing, and acceptance testing

  2. If the design is good, let’s do design all the time and make sure we do a retrospective at the end of each iteration

  3. If simplicity is good, let’s eliminate anything that does not add value and make sure we always do the simplest thing.

  4. If the review is good, let’s continuously improve by making sure we do reviews and retrospectives at the end of each iteration.

  5. If communication is good, let’s make sure our team space and tools encourage face to face osmotic communication.

  6. If iterations are good, let’s make sure we give regular stakeholder feedback in order to improve the quality of software and make sure we deliver the value the customer wants by doing the shortest possible iterations.

XP introduces the number of revolutionary concepts to software development and many have become standard practices:

  • Continuous Integration – this is the practice of regularly integrating new code into the system and using the automated testing to determine the status of the integration

  • Test-Driven Development – this is where the team writes the test before developing the code

  • On-site Customer – XP essentially makes the customer part of the team. The customer is expected to be on-site and participate with the team on a daily basis

  • User Stories – this practice is a quick and effective way to capture customer requirements and make sure there is an agreement between the customer and the developers regarding what should be developed.

Other XP practices include,

  • Collective Code Ownership

  • Creating a coding standard for the project

  • Creating a system metaphor to increase communication effectiveness

  • Pair programming

  • Establishing sustainable pace forever

XP team has the following characteristics:

  1. They are self-organizing - Team are empowered to decide for themselves how they are going to execute the project without top-down management and control

  2. They are cross-functional - The idea is to have generalizing specialists as team members. These are team members who specialize in one area but have enough knowledge to participate in the other roles that are part of the XP team.

  3. They compromise and collaborate – Team members including the customer, the coach, the programmers, the trackers, and the testers collaborate in order to reach an agreement on what exactly needs to be developed.

XP roles fall into 3 different categories – Customers, Programmers, and Testers

Customer – Customers are the business experts and can include

  • Product Managers

  • Domain Experts

  • Business Analysts

  • Interaction Designers

Programmers – Programmers are the

  • Implementation experts

  • As we said they are generalizing specialists, meaning programmers can exchange roles as necessary during the execution of the project

  • Ideally, there are 6 to 10 on a team

Testers – Testers are the

  • Quality experts and

  • Focus on Unit testing

  • Integration testing

  • Acceptance and

  • Exploratory testing

Preview 04:56
Agile - Crystal
Agile - Lean
Agile - Kanban
Integration of Agile and ITIL Roles
Points Covered in this Section
4 questions
+ Scrum - Events and Artifacts
6 lectures 19:01

This section will have detailed information about the following:

1. Scrum Pillars and Values

2. Scrum Lifecycle

3. Scrum Ceremonies

4. Definition of "Done"

Preview 01:03
Scrum - Pillars and Values
Scrum - Ceremonies
Points Covered in this Section
4 questions
+ Scrum Roles
4 lectures 14:11
Role of Scrum Master
Points Covered in this Section
4 questions
+ Agile – Estimation, Plan, Monitor and Control
13 lectures 37:15
User Stories and Epics
Story Cards and Splitting Stories
Planning - Levels
Ideal Time
Planning Poker
Affinity Estimation
Points Covered in this Section
4 questions
+ Agile on Complex Projects
9 lectures 38:05
Agile - Scale is Challenging
Scrum of Scrums & Scrum Events
Organizational and Project Related Factors
Agile Tools and Testing Pyramid
Points Covered in this Section
3 questions