Agile Masterclass: Scrum for Product Owner and Scrum Master!

If you are looking for Scrum certification quick tips, or if you are looking to find a job in one of the Scrum roles or just want to learn more about Scrum and Agile software development, you are at the right place.

Isn't it frustrating that you fail the Scrum certification again and again? Don't you hate when you are getting rejected in a competition for one of the Scrum rolls?

This Masterclass Course saves money, and it is short and clear enough. You will learn:

1. Introduction to Agile and Why Agile?

2. What is Agile in theory?

3. Why Agile Rocks?

4. Agile Mythbusters: 13 Myths in details.

5. (NEW) The Scrum Guide 2020 - What has been changed?

6. (NEW) Product Goal Introduction 2020.

7. You will find out what defines an excellent product, what Product Vision, Product Strategy, and Product Roadmap are,

8. What Scrum framework, Scrum roles, responsibilities are,

9. (NEW) Changes for the Scrum Masters in relation to Scrum Guide 2020

10. Scrum events, purposes, duration, what to pay attention to

11. Scrum artifacts

12. Definition of Done and Acceptance criteria

13. (NEW) Introduction to Evidence-Based Management EBM (2020 Edition)

14. I will present to you my recommendation on Scrum certification, which Certification body is best for you to choose and how to pass the examination - the easy way.

15. (NEW) 100 Carefully Selected Questions and Answers for Scrum certification.

16. YOU GET YOUR FIRST JOB AS A PRODUCT OWNER - THAT IS GREAT. I WILL SHOW YOU WHERE TO START BUILDING AN EXISTING PRODUCT OR WHERE TO START IF YOU ARE GOING TO BUILD A NEW PRODUCT FROM SCRATCH.

17. After all the sections, we will have a short knowledge test - Multiple choice questions.

Hi everyone, my name is Dejan. I am a Professional Scrum Product Owner, Professional Scrum Master, Agile Coach, and Trainer of trainers. Based on my previous experience, I have created this User-friendly Course so I can help individuals and teams to get better results with Agile and Scrum.

You will surely find some essential things in between the lines, too, namely, my love and effort invested into making my communication with you original, useful, and attractive, as well as a promise of continuous improvement.

I promise you that I will not waste your time. We will be very productive and efficient. So let's start your Agile and Scrum Journey right now.

WELCOME TO MY COURSE and don't forget to grab your Certificate of Completion at the end of the Course!!!

Agile is an innovation-friendly approach to product development. But the question is why might you want to learn about this? Well, for example, software development is pretty complex. There's a bunch of great technology out there and there's a lot of great software being produced but there's also a lot of waste.

In this course, we are not going to talk about Waterfall software development, but the waterfall Model illustrates the software development process in a linear sequential flow. In the waterfall model, any phase in the development process begins only if the previous stage is complete. On the other hand, Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.

The key difference between Agile and Scrum is that while Agile is a project management philosophy that utilizes a core set of values or principles, Scrum is a specific Agile methodology that is used to facilitate a project.

Agile allows teams to deliver a prototype and improve it with every cycle. Agile supports regular and collaborative troubleshooting. Agile helps teams and individuals effectively prioritize features and work in general. Teams can make quick-course corrections based on stakeholder feedback.

Now let's see 7 reasons why Agile is different...

With all these Agile myths debunked, I hope that you may reconsider your attitude towards Agile. Or, if you are already doing Agile, but I just showed you some of the cracks in your organization – you will take action and embrace the change.

So let's start with these 13 myths...

Now that you get your chance to learn some basics about Agile, try your luck at a quiz and see how you are doing.

It’s been 25 years since the launch of the Scrum Guide. With contributions from the Scrum community, Dr. Jeff Sutherland and Ken Schwaber have made updates to make it crisper, leaner, easier to access, more straightforward, and more transparent, opening the door to more practitioners in new industries and domains.

Now, let’s walk through the list of the majority of changed elements...

A product is an item offered for sale. A product can be a service or physical or in a virtual or digital form. Now, let's see what defines the value of good products?

The 2020 Scrum Guide introduces the concept of a Product Goal to provide a focus for the Scrum Team toward a larger valuable objective or in other words to make sure that we keep our eyes on the prize.

Each Sprint should bring the product closer to the overall Product Goal. 

Well, let's have a look at the brand new shiny edition of Scrum Guide 2020 to find out...

You can think of a product vision as the mission statement for your product. It's a long-term goal that answers the Question: In X years, what do you want your product to be? When crafting your product vision, make sure it's a stretch, but still realistic.

Product strategy is about imagining the future of your Product: What Product will it become? Who will it benefit? How will it create value?

A product roadmap is a shared source of truth that outlines the vision, direction, priorities, and progress of a product over time. It's a plan of action that aligns the organization around short and long-term goals for the product and how it will be achieving.

OK, now try your luck at a quiz and see how you are doing.

In short, we can learn and improve upon past mistakes and experiences. The three pillars of Scrum that uphold every implementation of empirical process control are Transparency, Inspection, and Adaptation.

Scrum encourages teams to learn through experiences, self-organize while working on a problem, and reflect on their wins and losses to improve continuously. While software development teams most frequently use the Scrum, its principles and lessons can be used to all kinds of NOT IT-related teamwork.

A Scrum Team is a collection of individuals (typically between five and nine members) working together to deliver the required product increments. The Scrum framework encourages a high level of communication among team members so that the Team can follow a common goal and adhere to the same norms and rules.

As a Product Owner, you are responsible for Product Backlog Management to maximize the value of the product. It's a one-person role, not a committee that brings the customer perspective of the product to a Scrum Team. He is the one who takes care of the product throughout the product life cycle. So as long as there is a product - there is a Product Owner (as opposed to traditional project management).

Scrum Master is an expert on Scrum and agility and is a champion of process improvement. He helps teams to apply Scrum, to work and train the team on the agile process, velocity, quality, impediment removal, etc.

Many Scrum Masters fill their entire week with the facilitation of Scrum events for their various Scrum Teams and nothing more.

(NEW) Changes for the Scrum Masters in relation to Scrum Guide 2020, emphasize what it is that Scrum Masters should be spending their time on.

The Development Team in Scrum does the work of turning business goals into value by delivering a potentially releasable Increment of "Done" product at the end of each Sprint.

Short Quiz about Scrum framework and Scrum Roles.

The Scrum events are time-boxed events. That means, in a project, every scrum event has a predefined maximum duration. These events enable transparency on the project progress to all who are involved in the project.

Scrum Sprint is a repeatable fixed a time-box of one month or less during which a "Done," useable, and potentially releasable product Increment is created.

The Sprint Goal helps the Scrum team to focus on the Sprint. That is the Goal that the Team will achieve within the Sprint through the implementation of the forecasted Product Backlog items. Sprint's goal also guides the Development Team on why it is building the Product Increment.

What Happens in a Sprint Planning? Who attends Sprint Planning? How long should Sprint Planning Last?

What Happens in a Daily Scrum? Who Attends the Daily Scrum? How long should Daily Scrum Last?

What Happens in a Sprint Review? Who Attends a Sprint Review? How Long Should Sprint Reviews Last? What is Important to remember...

What Happens in a Sprint Retrospective? What Is the Difference between Sprint Reviews & Sprint Retrospectives? Who Should Attend a Sprint Retrospective? How Long Should Sprint Retrospectives Last?

Continually refining and restructuring your product backlog reflects changes in shifting priorities, including customer requests and process optimization, and is a vital technique to deliver a valuable product to customers and users successfully.

Short knowledge test about Sprint, Sprint Goal, Scrum Events Questions, and Backlog refinement

Theme groups together separate epics and stories that fall under the same category.

An Epic is a big chunk of Work that has one common objective. It could be a feature, customer request, or business requirement. Key attributes and Examples.

User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. Key attributes, examples and technique for time estimation.

We use Tasks to break down user stories even further. Tasks are the smallest unit of  Work. Example of User story decomposition into tasks and Examples of Tasks.

Scrum Artifacts are information radiators, and they serve to capture the shared understanding of the Team at a particular point in time.

Scrum Artifacts play a vital role in the Team to reflect on how they are doing with the sprint goal. The development team use artefacts to maximize the transparency of essential information so that everybody has the same understanding of the artefact.

A product backlog is a list of all the things that the Team needs to create for that product. It is a dynamic and best-understood requirement for any changes to the product.

The Sprint Backlog is the set of Product Backlog items (Tasks) selected for the Sprint plus a plan for delivering the product Increment and realizing the Sprint Goal. Sprint Backlog Example...

A Scrum Board is a tool that helps Teams make Sprint Backlog items visible. The board can take many physical and virtual forms. You will see a DEMO of one of these free tools you can use.

The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.

A short quiz on understanding of scrum artefacts

The Definition of Done is an agreed-upon list of the activities necessary to get a product increment to a done state by the end of a sprint.

Acceptance criteria are a set of predefined requirements to mark a user story complete.

Short Quiz of Understanding Definition of Done and Acceptance criteria

Students will get the knowledge about EBM and how it strengthens decision-making and practice in business and organization and how to appraise evidence quality before applying it to support decisions and actions and also how to use evidence and their position to improve on their learning experience.

Which Is The Best Scrum Certification Body? How to pass the Scrum Master and Scrum Product Owner examination from the first attempt. Which exam should you take first? Here is my recommendation.

Here you can find great tips and knowledge sources for all those who want to prepare for the Scrum.org exam on their own.

This Class Consist of 100 Carefully Selected Questions and Answers that are not copy-protected by the official Scrum certification bodies.

Instructions:

1. Take your seat and concentrate,

2. Start the video,

3. View the Question,

4. Hit Pause and think about the answer,

5. Hit Resume and read the answer.

6. ...

What are the requirements, how much it costs, difficulty level, number of questions...

Imagine the following situation, there is an open position for the Product Owner because the previous one left the company. So you have your certificate ready, you have applied for this position. You are selected. What do you think, how to start? Please pause the video and think about it for a couple of seconds. You can be in two different situations that you should consider. You will work on an existing product, or you are building a new product from scratch.

How can I continue where the previous Product owner left off this product, e.g., at the end of the third sprint? What are your next steps?

If you can’t ask customers, because you are building a new super cool (non-existing) product then what are you supposed to do? Just build something and hope for the best?

Agile testing is a software testing that follows the best practices of Agile development. So, take your seat, relax with this background music, and read the most common questions followed by answers for Agile testing.

This is a product ownership course compressed into a short animated presentation. Special thanks to Henrik Kniberg creator, Alistair Cockburn, Tom & Mary Poppendieck, Jeff Patton, Ron Jeffries, Jeff Sutherland, and Michael Dubakov for providing many of the models, metaphors, and ideas for this presentation.