In this course, you will learn :
- The Difference Between an Adaptive and a Predictive Development Approach
- Scrum Values Explained and Demonstrated.
- The Agile Scrum Master's Characteristics
- How to Handle Conflicts in a Scrum Team.
- Servant-Leadership Is At The Heart Of The SM Role And Accountability.
- The Agile Product Owner's Characteristics
- The Developers' Characteristics
- "Timeboxing" is an Agile concept.
- Iterative and incremental development concepts
- The Scrum Events' Characteristics
- Scrum Artifacts and Commitments Have Specific Characteristics.
- The Distinction Between the Definitions of Done and Ready
- Recognize Story Points as a Relative Unit of Measurement.
- The Planning Poker Activity Is Used To Remove Anchoring Bias.
- Explanation of Burnup and Burndown Charts
- The Uncertainty Cone and What It Reveals
- The Idea of Technical Debt and Code Refactoring
- The Idea of "Feedback Loops."
- The Distinction Between Definitions of Done and Acceptance Criteria
1. The Scrum Team - Scrum Master, Product Owner, and Developers
- Introduction to the Scrum Team
- The Scrum Master
- The Product Owner
- The Developers
- Skills Within A Scrum Team
- Scrum Accountabilities (Formerly Known As Roles)
2. The Scrum Events
- Introduction to Scrum Events
- Timeboxing: Simple Yet Powerful Concept Behind Scrum Events
- The Sprint - The Heart Of Scrum!
- The Sprint Planning Event - Let's Answer “Why”, "What" & "How"
- The Daily Scrum Event - Who Is Required To Participate?
- The Sprint Review Event - Let's Show What We've Built!
- The Sprint Retrospective Event - Let's Inspect Not The Product But The Team
- The Length Of The Scrum Events - Clarifications
3. Scrum Artifacts & Their Commitments
- The Product Backlog (The Single Source Of Work!)
- The Product Goal (The Long-Term Objective)
- The Sprint Backlog & The Sprint Goal
- The Increment - "Let's Build Some Of It Before We Build All Of It"
- The Definition Of Done (It's Mandatory)
- Recap Of The Key Concepts (Watch A Few Times)
- Scrum Artifacts & Commitments
4. Practices & Charts That Are Not Mandatory In Scrum But Often Used
- Story Points - (Let's Use Effort-Based Units)
- Planning Poker - Eliminate The Anchoring Effect (A Cognitive Bias)
- Burndown Chart - How Much Work Is Left?
- Burnup Chart - (Complete Work & Total Work)
- The Cone Of Uncertainty - What Exactly Does It Show?
- Technical Debt - Can We Afford To Pay It Back?
5. Scrum Example - A Solution For A Chiropractic Clinic
- Introduction - Apply The Scrum Theory Into Practice
- The Chiropractor Faces A Major Problem (They Might Need To Close The Clinic...)
- The First Meeting With The Chiropractor (Let's Write Some User Stories..)
- Crafting a Product Goal & Vision
- Create A Project In JIRA (Overview Of The Issue Tracking Tool)
- Sprint Planning With The Team
- Daily Scrums During The Sprint (Definition Of Done vs Acceptance Criteria)
- Sprint Review - The Client Didn't Want To Attend....
- Sprint Retrospective - Let's Find At Least One High Priority Process Improvement
- Sprint Planning For The Second Sprint
- Project Progress
6. The Examination
- The Main Reasons Why People Fail The Exam
- Scrum Rules That NEVER Change
- Scaling Scrum
- The Definition Of Ready
- Recommended Resources To Help You Pass The Exam
- Scaling Scrum