Certified Scrum Developer Training
This Certified Scrum Developer training course is aimed at software developers (programmers) who are building software in an Agile environment. The goal is to expose students to the most important tools and techniques that need to be applied in order to build good software in the iterative and incremental way. These ideas are central to Agile software development and DevOps.
By the completion of the Certified Scrum Developer training technical practices course, the student will be able to perform test-driven development, refactoring, and continuous integration in a course-provided sandbox situation. The student will be familiar with the terms and practices involved, and why these practices are important. They will have taken the first steps toward becoming expert in iterative and incremental development.
By the completion of the Certified Scrum Developer training technical practices course, the student will be able to…
– Understand why highly-effective developers write their own tests
– Understand assertions
– Understand the full spectrum of testing options
– Identify various types of tests (unit tests, integration tests, functional tests, acceptance tests, etc)
– Know how to write automated tests
– Define pair programming and mob programming
– Define “collective code ownership”
– Describe “working together as one team.”
Test-Driven Development :
– Describe Test-Driven Development (TDD) as a design approach.
– Review the steps of the red-green-refactor cycle.
– Explain, using examples, at least three unit testing principles and practices.
– Outline five qualities of a good test.
– Describe how to measure test effectiveness.
– Describe what “legacy code” is
– Develop a strategy for working effectively with legacy code
– Define refactoring
– Describe when to refactor.
– Understand SOLID principles
– Outline refactoring for maintainability.
– Define refactoring to patterns.
– Understand—and recognize—code smells
– Describe what Technical Debt is
– Understand the influences for technical debt
– Match the benefits of various technical practices to influencers of technical debt
– Understand what test doubles are (e.g. mock, stub, fake, spy, etc)
– Understand when to use a test double
– Understand how to balance the trade-offs in using mocks
– Understand the key practices of continuous integration
– Define a single command build.
– Summarize how to create a build that is automated, self-verifying, and fast.
– Describe the importance of a single-source repository.
– Define increasing visibility and automating deployment.
Location: Fairfield Inn and Suites, Tustin, Orange County 15011 Newport Ave. Tustin, CA 92780