Master Scrum and Unleash The Leader In You! I Mastered Scrum

In this lecture we will cover Meeting Facilitation

• What is Facilitation?

• Understanding Roles and Task

• Common Facilitation Challenges

• Biggest Mistakes to Avoid

• Best Practices for Meetings

• The 3 R’s of a Successful Meeting

• Bring ELMO to every meeting

Once you understand the role and task requirements of a facilitator, that does not mean you will not face challenges.  In this section we will take a look at those challenges, as well as, mistakes to avoid.

In this section of the lecture we will look at best practices for facilitating in-person and virtual meetings.

In this lecture we will cover Active Listening

• Levels of Listening

• Benefits of Active Listening

• Common Listening Problems

• Best Practices of A Good Listener

• Improve Your Listening Improve Your Life

In this lecture we will cover Self-Organizing Teams (SOT)

• What is a Self-Organizing Team

• Traditional Team vs. Self-Organizing Team

• Attributes of A SOT

• Benefits of a SOT

• How to Create a SOT

In this lecture we will cover Team Agreements

What When and Why of Team Agreements

In this lecture we will cover Team Agreements

• How Are Team Agreements Created

• Who Enforces Team Agreements

In this lecture we will cover Relationship Building

• How to build relationships

• Conflict resolution

• Resources for Success

In this lecture we will cover Scrum Artifacts

• Understanding Scrum Artifacts

Scrum artifacts are key components that provide transparency and opportunities for inspection and adaptation within the Scrum framework. They help teams manage their work and ensure that everyone involved has a clear understanding of the project status. The main Scrum artifacts include

1. Product Backlog: - A prioritized list of all the work that needs to be done on the project. - It includes features, enhancements, bug fixes, and other requirements. - The Product Owner is responsible for maintaining and prioritizing the Product Backlog to ensure that the most valuable items are worked on first

2. Sprint Backlog: - A subset of the Product Backlog that the team commits to completing during a specific Sprint (usually a 2-4 week iteration). - It includes the selected Product Backlog items along with a plan for delivering them. - The Development Team owns and manages the Sprint Backlog, and it can be adjusted as needed throughout the Sprint

3. Increment: - The sum of all completed Product Backlog items at the end of a Sprint, representing the current state of the product. - An Increment must be in a usable condition, meaning it should be potentially shippable, even if the team decides not to release it. - This artifact showcases the progress made and the functional product that stakeholders can review

4. Burndown Charts (optional artifact): - While not officially defined as a Scrum artifact, burndown charts are commonly used to visualize the work remaining in a Sprint or the entire project. - They help track progress and can indicate whether the team is on track to complete the planned work within the Sprint or release timeline These artifacts are crucial for promoting transparency, facilitating communication, and ensuring that the Scrum Team stays aligned with their goals.

In this lecture we will also cover Scrum Ceremonies, I will share with you my personal experience for success as well as industry best practices to ensure you are equipped to get the best out of your scrum ceremonies.

• Keys for Successful Ceremonies

In this lecture we will cover Capacity VS. Velocity

• Understanding Key Terms

• Factors affecting capacity

• How to calculate capacity - Activity

• Using Capacity and Velocity together

• Sprint Planning Simulation - Activity

In this lecture we will cover Capacity VS. Velocity

• Please make sure you print the downloadable resources in this section.

Understanding Capacity vs. Velocity in Scrum

Objective: By the end of this lesson, participants will understand the concepts of the metrics capacity and velocity in Scrum and how to use them for effective sprint planning and workload management

What do these Key Terms mean?

**Capacity:** The total amount of work a team can handle in a given sprint based on availability and working hours. -

**Velocity:** The amount of work a team completes in a sprint, usually measured in story points or completed user stories

Why do we need to understand Capacity and Velocity?

Understanding capacity and velocity is crucial for successful Scrum implementation because it helps teams plan sprints better, set realistic goals, and improve predictability

Factors Affecting Capacity:

• Team size - Individual availability (vacations, public holidays, etc.)

• Skill levels and experience

• Other commitments (meetings, training)

Complete Activity for Calculating Capacity and Velocity - downloadable resource

Now that you have an understanding of what these metrics are and how to calculate them, let's look at using Capacity and Velocity Together for Sprint Planning. During sprint planning, teams should use their capacity to avoid overcommitting and their velocity to inform what they can realistically achieve.

Complete the following Sprint Planning Simulation to Test Your knowledge - downloadable resource

Understanding both helps teams set achievable goals and improve their delivery process. Congratulations! You now have a practical understanding of how to use capacity and velocity effectively within the Scrum framework.

In this lecture we will cover Requirements

We will discuss the importance of accepting and managing changing requirements.