
What will we cover in this course. Why you would want to take this course.
In this class, we will refer to the 2020 Scrum Guide. If your goal is to pass the Scrum Master Certification then I absolutely recommend you reading the Scrum Guide , regardless if you've watched tons of Scrum videos: https://www.scrumguides.org/.
PLEASE NOTE that starting Jan 10th 2021, the Scrum assessments will be based on the 2020 Scrum Guide.
Listen to this course in order, don't skip a lesson. The course is presented in a chronological way and some lectures refer to previous ones.
The only exception is if you want to only know how to use JIRA then you can go straight to any lectures that start with "JIRA: ".
Sign up for JIRA and Confluence Cloud free version . The screen recordings used the JIRA & Confluence cloud version published in Nov 2020.
Create a dedicated Confluence space for your project by clicking the Confluence icon, naming the space after the project (same as Jira), and start documenting in the new space.
Ann shares her journey as a certified Scrum Master since 2013, coaching diverse teams across industries and organization sizes to help you start strong in Jira-driven Scrum.
Start strong as a scrum master by confirming laptop access and device tests, then setting up JIRA and Confluence. Gather documentation and essential tools like planning poker cards and markers.
Revised lecture after Jira updates: Apr 2021
Explore Jira's project overview by navigating the left panel to active sprints, backlog, and reports, and learn how to configure components, releases, issues, Bitbucket, Confluence, shortcuts, and project settings.
What is considered "Sprint Zero" and an example of activities to do.
As a PO, I will present the product's goals and roadmap.
We will present the Budget feature using mockups of design. This is a good example of how a Product Owner can describe the features to the team without having it fully detailed. In this example, only Google Slides was used to create. Check out the Resources to see other tools that can be used.
This is the precursor for the user story mapping.
Now that we saw the mockup of our product, let's break it up into Epics and User Stories.
We will have our final set of MVP user stories.
Scrum is a lightweight, simple framework in which the product owner manages the backlog and developers select high-priority items to deliver an increment, inspect it, and cycle back.
Scrum theory, through empiricism and lean thinking, emphasizes observing outcomes, adapting decisions, and reducing waste by aligning scope with the product owner and teams through sprints and testing.
A trick to remember the Scrum values.
Explore the three scrum artifacts—the product backlog, the sprint backlog, and the increment—and their commitments to transparency. See how product goal, sprint goal, and definition of done reinforce empiricism.
Explain the roles of business analysts, product owners, QA, front-end, back-end, and full-stack developers, and how they collaborate on research, user stories, and APIs.
Here are some tips on when to schedule the Scrum Events. As always, it is up to you to see if it makes sense to apply to your situation.
Begin with a team building activity before the first sprint to build connections. Make it interactive, share interests, and adapt your scrum or agile presentation to engage everyone.
What is a Product Backlog, how do you order the items, what are things to watch out for.
Different methods on how-to create Epics in JIRA , including the new ROADMAP feature in JIRA.
Edit and review a Jira user story in the backlog, updating description, summary, status, assignee, priority, labels, epic, sprint, and fix versions while tracking activity and workflow.
Learn to add users to a Jira project by using the gear icon to access user management, invite by email, and track pending invitations on Jira cloud's free plan.
Learn to estimate user stories without bias by keeping opinions private and using planning poker cards, or remote tools, to reveal votes and ensure unbiased Scrum planning.
Create and manage sprints in Jira from the backlog view using the create sprint button, edit names, delete empty sprints, and reorder with move up or down before sprint planning.
Learn how to add user stories to a sprint in Jira, move multiple tickets with drag-and-drop or right-click, set sprint duration and goal, and start the sprint.
Learn how to break down a user story into subtasks in Jira, assign UI design, frontend and backend API, and QA test cases, and view subtasks in active sprints.
Overview of the daily scrum as per the 2020 Scrum Guide.
Learn to change a Jira subtask status by dragging it in the active sprints view to the end progress column or by updating the status directly.
Let's look at how the team have been progressing in their user stories after a few days.
Explore a Jira user story in progress (FinApp14) within sprint one, noting story points, epic, and subtasks. Observe color coding and progress indicators showing completion at a glance.
Let's look at the burndown chart when a user story is closed.
One day left in the sprint, how is the team moving along? What does the burndown chart look like now?
Master Jira versioning by creating versions in backlog or releases, assigning user stories to MVP, V1, or V2, and tracking progress with story points and completion status.
Close sprint in Jira after completing all user stories, demo completion, and updating parent issues, then review the sprint report and burndown chart showing zero by the due date.
Explore how a sprint review inspects completed increments and adapts the product backlog, featuring a demo and a working session with the PO and stakeholders.
Explore the Jira structure by viewing projects and their issues, including epics, stories, and subtasks, with fields like summary, description, epic link, and story points.
Explore Jira issues, including epic, story, task, bug, and subtask, and learn how to create, edit, move, or delete them while mapping default statuses to columns.
EVERY Scrum Master should know how to do this!!
Here is an example of an improved workflow design followed by a description of the main steps to implement this in Jira.
Add a new subtask type in Jira, named dev subtask, and associate it with the FinApp issue type scheme. Understand how workflow schemes determine default processes.
Create a new workflow with new statuses and transitions.
At the end of this lecture, we will see that our project has the new issuetype associated to the new workflow.
Configure Jira active sprints columns to display new statuses and map each status to a column. Use the simplified workflow to reflect ready for qa, review, and done progress.
Master Jira keyboard shortcuts to navigate the backlog, active sprint, and reports, assign issues to yourself or others, add comments, create issues, and quickly search.
You have no experience as a Scrum Master? You are new to the job market and you wonder how to start? Then this is THE class for you!! You will gain the confidence to go for an interview or start working since you will feel like you already have some experience. It's not just about the knowledge of Scrum but the knowledge of working as a Scrum Master.
Throughout this beginner's class, I will be your personal mentor. I will coach you into your role of a Scrum Master by looking at the practical aspects of the job, using basic JIRA.
With this starter kit, I will also present the product so if you are a new Product Owner, this will be a helpful example for you.
JIRA, being one of the most commonly used tool in Scrum, is the one that we will use to manage the backlog, user stories and to track the team's progress towards their Sprint Goal.
As a BONUS, I will also be showing you how to use Confluence as a documentation tool.
Whenever I mention the Scrum Guide, rest assured that I am referring to the latest 2020 Scrum Guide.
For an experienced Scrum Master, stay tuned for upcoming advanced lesson.