Become a

Certified Scrum Developer ®

On-Site Classes

 

Congratulations!  You've begun your transition to Agile software development.  Your Scrum Masters and your Product Owners have been trained for their new roles.  But how about your Development Team?  Are they using the Agile Engineering practices necessary to get the most benefits from Scrum?

​

Help your team achieve the full benefits of software development with Scrum by scheduling an on-site Certified Scrum Developer class today.

​

Upcoming Public Classes

 

 

In addition to training for our corporate and government clients, we also offer public classes.  

We currently have the following public classes scheduled:

​

 

Columbus, OH

 

May 15 - 19

​

San Jose, CA

June 12 - 16

​

Olympia, WA

June 19 - 23

​

Vancouver, BC

June 26 - 30

​

Jersey City, NJ

July 10 - 14

​

San Diego, CA

July 24 - 28

The Certified Scrum Developer Program

CSD Credential

The Scrum Alliance created the Certified Scrum Developer program to allow developers to:

  • Learn the foundations of Scrum
     

  • Understand Agile Engineering practices
     

  • Demonstrate to employers and peers your attainment of core Scrum knowledge.
     

  • Expand your career opportunities by staying relevant and marketable across all industry sectors adopting Agile practices.
     

  • Engage with a community of recognized Scrum experts who are committed to continuous improvement.

​

 
CSD Requirements

There are two possible tracks to obtain a CSD.  Our CSD curriculum is designed to fulfill all of the requirements of the second track.

​

Track 1

  • CSM course (2 days)

  • CSD technical course (must include coding) (3 days)

​

Track 2

  • Intro to Scrum CSD course (1 day)

  • CSD technical course (must include coding) (3 days)

  • CSD technical elective course (1 day)

​

 
CSD Curriculum
Day 1: Scrum Fundamentals
​

  1. Waterfall

  2. Philosophical underpinnings

  3. Introduction to Scrum

  4. Core Concepts

  5. Agile Principles

  6. Sprints

  7. Requirements and User Stories

  8. Product Backlog

  9. Velocity

  10. Roles – Product Owner

  11. Roles – Scrum Master

  12. Roles – Dev Team

  13. Planning in Agile

  14. Sprint Meetings

  15. Agile Game – applying the lessons learned

 

Day 2: Agile Technical Practices
​
I. Programming by Intention

  1. Visualizing the code you wish you had

  2. Using helper methods

  3. Delegating

  4. Preview of Extract Method and Extract Interface refactoring techniques

  5. Single Responsibility principle

  6. Open / Closed principle

  7. Liskov Substitution principle

  8. Interface Segregation principle

  9. Dependency Inversion principle

  10. Onion Architectures

  11. Evolving Architectures

  12. Code smells

  13. Refactoring Techniques

  14. Refactoring Case Study

​

II. SOLID Design Principles

  1. Single Responsibility principle

  2. Open / Closed principle

  3. Liskov Substitution principle

  4. Interface Segregation principle

  5. Dependency Inversion principle

​

III. Architecture and Agile

  1. Onion Architectures

  2. Evolving Architectures

​

IV. Refactoring

  1. Code smells

  2. Refactoring Techniques

  3. Refactoring Case Study

 

Day 3 - 5: Acceptance Test Driven Development (ATDD) / Test Driven Development (TDD)
​
I. Introduction: What is ATDD/BDD/TDD?

  1. What is ATDD – Acceptance tests

  2. What is BDD

  3. What is TDD

  4. Red – Green - Clean

  5. How will ATDD/BDD really help?

  6. Understanding Roles & Responsibilities

  7. ATDD/BDD work process Flow

  8. ATDD best practices

​

II. Cucumber and Gherkin

  1. What is Cucumber

  2. Arrange – Act – Assert

  3. Gherkin Syntax – Keywords

  4. Features and Feature files

  5. Creating scenarios – using Given/When/Then/And/But

  6. Creating multiple scenarios for a single feature

  7. Background key word

  8. Scenario Outlines

  9. Regular expressions

  10. Good/Bad Practices – DSL

  11. ATDD Best Practices

  12. Tags

​

III. Tools and web driver

  1. Selenium and Selenium web driver

  2. Practice – Case study number 1

​

IV. Programming the tests (step definitions) in Java

  1. Case Study number 2

  2. Case Study number 3

​

V. Testing an API

  1. Interfacing with an API

  2. Case Study 1: Testing Git Hub

  3. Parsing the response

  4. Case Study 2: Testing Google Maps

​

VI. Advanced topics

  1. Folder Structure - Configuration, Feature files, and step definition files

  2. Libraries and Logging

  3. Refactoring test code – the DRY principal

  4. Creating a DSL of steps

  5. Refactoring with the Page Object pattern

  6. Case Study number 4

​

​

© 2015 - 16 by Victoria Fairfield. Proudly created by wix

  • c-facebook
  • Twitter Classic
  • Google Classic