Lessons in This Class
67 Lessons (2h 1m)
- 1. Welcome 1:03
- 2. Scrum basics 1:35
- 3. Agile vs waterfall 1:59
- 4. Strengths and limitations 4:04
- 5. The sprint 2:02
- 6. Sprint length 1:22
- 7. What are artefacts? 0:33
- 8. Product backlog 2:04
- 9. Example product backlog 1:07
- 10. Sprint backlog 1:06
- 11. Example sprint backlog 1:55
- 12. Definition of done 1:10
- 13. What are ceremonies? 0:21
- 14. Daily Scrum 1:34
- 15. Backlog refinement 2:08
- 16. Estimating points 1:52
- 17. Agile poker 1:28
- 18. Velocity 1:16
- 19. Sprint planning 1:32
- 20. Retrospective 1:16
- 21. Ideas for retrospectives 3:22
- 22. Ways of working 1:19
- 23. Sprint review 0:44
- 24. Scrum team 1:24
- 25. Product owner 1:54
- 26. Scrum master 1:47
- 27. Business analysts 1:32
- 28. Engineers 1:38
- 29. Stakeholders 1:03
- 30. A typical scrum team 0:52
- 31. Adding team members 1:05
- 32. Issue types 1:18
- 33. User stories 1:32
- 34. Behaviour-driven development case study 2:18
- 35. Being “good enough” 1:54
- 36. INVEST 1:41
- 37. Prototyping and user labs 2:30
- 38. Functional requirements 0:58
- 39. Non-functional requirements 2:55
- 40. Tech debt 2:01
- 41. Cancelling a sprint 1:00
- 42. What is agile release management? 1:42
- 43. Release management cycle 0:57
- 44. Advantages of agile release management 2:28
- 45. Common release schedules 3:06
- 46. Keys to success 2:48
- 47. Continuous integration 2:12
- 48. Continuous delivery 1:00
- 49. Continuous delivery tools 1:27
- 50. Agile software 0:41
- 51. Jira 5:00
- 52. Burndown chart 1:19
- 53. Trello 1:52
- 54. Mural 0:46
- 55. Building psychological safety 3:07
- 56. Wash-up meetings 2:31
- 57. Selling agile to management 4:42
- 58. Coaching good practice 3:47
- 59. How to scale Scrum 0:50
- 60. Scrum of Scrums 1:39
- 61. Splitting products 1:50
- 62. Sprint alignment 2:06
- 63. Other methodologies 0:22
- 64. Kanban 2:49
- 65. Extreme programming 2:15
- 66. Test-driven development (TDD) 1:11
- 67. Behaviour-driven development (BDD) 2:33
- Beginner
About This Class
Scrum is an agile project management framework designed to reduce failure, get projects in front of the client quickly and cope with changing user requirements. If you are brand new to Scrum, this class will teach you everything you need to know.
It’s suitable for product owners, scrum masters, business analysts, engineers, designers, testers, managers or anyone else who wants to learn the Scrum framework.
We’ll cover each aspect of Scrum in turn:
- Artefacts: product backlogs, sprint backlogs and definition of done documents
- Ceremonies: Daily Scrum (stand-up), backlog refinement, s
- print planning, retrospectives, ways of working meetings, wash-ups and sprint reviews
- Estimating points, velocity and agile poker
- Team roles including product owners, scrum masters and stakeholders
- Team psychology including psychological safety, coaching and best practice
- Agile requirement gathering, user stories, tech debt, prototyping and user labs
- Agile release management, continuous integration and continuous delivery
- Scaling scrum beyond a single team with product splitting and Scrum of Scrums
- We will learn everything from fundamentals, but we’ll also take a look at tools and software we can use such as Jira, Trello, Travis, and other project management and continuous integration platforms. We’ll also look at related fields: Kanban, test-driven development, behaviour-driven development and more.
- We’ll apply it to the real-world by looking at a fiction e-commerce store software project. As part of the class project, you will create your product backlog, write tickets and create all of the documents you need to run your Scrum team.
Related Skills
Technology , Web Development, Agile Project Management, Scrum , Agile, Agile Methodology , Scrum Master
Hands-on Class Project
Your project is to create all of the documents you need for your Scrum project. You can use the e-commerce store we discuss in the lessons, or you can use your own project. Your documents should include the following:
- Product backlog, with issue types and organised into epics
- Definition of done
- At least five tickets with clear acceptance criteria