Professional Scrum Developer

Planning Information

The duration of this course is 3 Days. The list price is $2,200.00.

Description

Professional Scrum Developer™ (PSD) is a 3-day hands-on course where you will experience how to deliver quality software using Scrum with Agile and DevOps practices. Students will work as a Scrum Team or multiple Scrum Teams depending on class size, creating real code on a realistic software system. 

Intended Audience

Applied learning intended for technically oriented students working on or with a Scrum Team who need to know how to integrate software craftsmanship into a scrum team. This is the Scrum.org Professional ScrumTM Developer (PSD) certification course for Java and .Net.

At Completion

  • ​Understand the scrum framework in detail
  • Minimize project uncertainty and risk by applying Agile principles 
  • Practice Scrum techniques through actual application in the classroom
  • Learn how to apply Agile by measuring and evaluating status based on the undeniable truth of working, testing software, creating a more accurate visibility into the actual progress of projects. 
  • Know the advantages and importance of a self organizing, cross functional, high performance teams.

Prerequisites

The Professional ScrumTM Developer course is suitable for any member of a software development team, including architects, programmers, database developers, testers, others with some technical knowledge. It is recommended that participants have a basic understanding of project management and business processes and business analysis. Participants will be expected to create and modify code.

Exams & Certifications

As part of this class, students are offered one free attempt of the Professional ScrumTM Developer I online assessment. If they score 85%, they will receive the PSD I certification.

Materials

Scrum.org standardized courseware

Course Outline

This practical classroom experience equips attendees to get started with Scrum, to sustain successful habits, and to avoid common Scrum pitfalls. Students learn the basics of Scrum and how to implement Scrum effectively and keep their team practicing healthy behaviors. The course will cover three main topics: Scrum, tools, and practices.

Scrum -The course simulates being part of a Scrum team to expose students to the core Scrum concepts in action. Students learn how to work as part of a Scrum team, which requires them to understand techniques for self-organization. Through the course students develop skills in identifying and overcoming common Scrum Team dysfunctions

Tools - Tools. PSD courses teach students how to leverage different development tools to employ Scrum practices. PSD and PSD+ courses are taught in the context of Visual Studio for .NET or Eclipse + Open Source tools for Java. Students learn how to map specific tool features and functions to the general Scrum practices they must use to be effective team members.

Practices –PSD courses cover all of the technical practices that team members need to successfully implement and ship functionality. These include coding practices like test-driven development, continuous integration, and refactoring; architecture practices such as emergent architecture and evolutionary database development; release management practices like planning, requirements

Multiple sections of practice are interleaved with the lecture

Section 1: Scrum Fundamentals

  • The case for agile and Scrum
  • Empirical model
  • Defining Scrum
  • Scrum roles
  • Scrum artifacts
  • Scrum activities
  • Complexity and Scrum
  • Waterfall and Scrum

Section 2: Refining the Backlog

  • Evolution of requirements
  • Agile estimation
  • Levels of planning
  • Acceptance Criteria
  • Stories, Epics, Themes
  • Release Planning

Section 3: Application Life Cycle Management 

  • ALM overview
  • Tracking sprints and the backlog
  • Branching strategies
  • Continuous Integration and deployment
  • Release models
  • Tools 

Section 4: Quality and Scrum 

  • Quality management 
  • Technical Debt
  • Pair programming
  • Definition of done
  • Definition of ready
  • Testing automation/naming/coverage
  • BDD and TDD cycles
  • Test management and naming
  • Explorative testing
  • Specification by example

Section 5: Emergent Architecture 

  • Architectural patterns
  • Emergence 
  • Patterns and anti patterns

Section 6: Challenges with Quality and Scrum 

  • Refactoring patterns 
  • Clean code
  • SOLID code
  • Scrum challenges
  • Adoption patterns

Section 7: Additional notes and questions 
 

Pin It on Pinterest