Professional Scrum Developer (PSD) is an 3-day hands-on course for software development teams where they experience how to deliver quality software using Scrum with Agile and DevOps practices. This course teaches you why and how the Scrum Framework should be combined with modern DevOps engineering practices to improve a team’s capability to regularly deliver working software.
During the course, participants work together as a Scrum Team in a series of Sprints to build a realistic product, whereby they deal with real-life challenges in software development. The mechanics, roles, and principles of Scrum are fully leveraged during these exercises. In this way, the entire Scrum Team learns the Scrum Framework through its practical application, which leads to a clear understanding of roles and responsibilities inside and outside the Scrum Team and removes common misunderstandings.
What You Will Learn
Students self-organize in Scrum Teams at the beginning of the course and are presented with a real-life case study. During the course, they practice the Scrum Framework in multiple realistic Sprints, during which they are gradually introduced to Scrum mechanics, roles and principles, and also to selected core engineering and technical patterns and practices that complement Scrum.
The trainer acts as a stakeholder by defining requirements before each Sprint and attending Sprint Reviews. By the end of day 3, teams become familiar with all Scrum components and rules: they define and enact Scrum roles (Product Owner, Scrum Master, Development Team), work with Scrum artifacts (Product Backlog, Sprint Backlog, Increment), run all Scrum events (Sprint Planning, Sprint, Daily Scrum, Sprint Review, Sprint Retrospective), refine their backlog, come up with the team's Definition of Done, learn about Scrum Values and empiricism, and experience common challenges of working in teams. Selected DevOps technical practices, like estimation techniques, code reviews, continuous delivery and automated testing, are incorporated as activities during the Sprints for students to understand why and how they perfectly complement Scrum. A class retrospective is done after each Sprint to enforce learning objectives. Discussions are encouraged throughout the entire duration of the course.
The course case study is available in .NET, .NET Core, Java and Python. Since the goal of the course is to learn about Scrum and its synergy with DevOps practices and tools, the student's possibly unaligned technology background does not impede students to actively participate in team exercises. Besides programmatic tasks, there are plenty of other activities to cover, like acting as a Product Owner or Scrum Master, dealing with user requirements, estimating, testing and triaging bugs, designing a CI/CD pipeline, etc. Public classes have a fixed technology stack and we expect at least part of the students to be comfortable with the case study. For private classes, the trainer works with the team up front to define a specific technology stack that meets their needs.
- Get a clear understanding of foundational elements of Scrum and their coherence
- Learn the different aspects of a Scrum Team and how to collaborate to get work done
- Understand how modern Agile engineering practices and supportive DevOps tools improve a team’s capability to deliver working software
- Walk away with a handful of tips to identify common pitfalls and dysfunctions in Scrum
- Understanding and applying the Scrum Framework (Empiricism, Scrum Values, Roles, Events, Artifacts)
- Developing people and teams (Scrum roles and responsibilities, Self-organizing teams, Team collaboration)
- Managing products with agility (Maximizing product value delivery, Product Backlog management, Estimation techniques, Forecasting and release planning, Managing stakeholders and customers)
- Developing and delivering products professionally (Emergent software development, Managing technical risk, Continuous Integration (CI) / Continuous Delivery (CD), Optimizing flow and reducing waste)
- Continuous quality improvement (Definition Of Done, Managing technical dept, Test driven development, Automated testing, Test shift left, Code reviews)
- Keeping Scrum healthy (Identifying common Scrum missteps and misunderstandings)
- Leveraging DevOps toolsets (Backlogs and boards, Version control, Build and Release management)
Check out further info on Professional Scrum Competencies and different focus areas covered within this class and other Scrum.org classes.