Audience

This course is suitable for any member of a Development Team, including architects, programmers, database developers, testers, and others with some technical knowledge.

Product Owners, Scrum Masters, and other stakeholders are welcome to attend this class as long as they keep in mind that this is a technical course and involves programming in pairs.

Prior knowledge

Basic Scrum knowledge such as ScrumMaster (+certifiering) or Introduktion till agila metoder, some Object Oriented programming skills, basic knowledge about JUnit and unit tests. Plus an open mind.

Preparations

Read the Scrum Guide Prepare by taking the Professional Scrum Developer Open Assessment

Certification

PSD I assessment (the price includes one attempt to pass the certification)

This course is also available for .NET developers

Please note that the participants are required to bring their own laptop. with:

– Eclipse (or IntelliJ IDEA),
– Git (or Mercurial client), 
– Maven (or Ant or Gradle)*

* To verify your setup, clone, run and import this basic TDD+OO kata.

What will a developer learn from this course?

The short answer: a repeatable process for turning a Product Backlog item into something that is done and potentially shippable. You will learn how to do this using tools (like Eclipse, Jenkins, Sonar & Git), Scrum, and Agile software engineering practices.

What will the individual and the team learn from this course?

Individuals will learn how to form themselves into a self-organizing, cross-functional development team to develop an increment of software. They will also learn how to optimize their individual skills, self-manage their own work during a Sprint, and resolve conflicts more effectively, in order to better operate as a team. Teams will work on a common project in a parallel development environment.

In this course, a Development Team will learn how to self-organize and turn Product Backlog items into a done product Increment using Scrum, proper tooling, and contemporary software development practices.

Course Outline

Scrum

This three days course expects participants to have basic understanding of Scrum, so that focus can

• Run several complete sprints
• Practice planning with Sprint planning meetings
• Keep Product backlog in good shape with continuous refinement/grooming
• Focus on delivering value from Daily Scrums
• Inspect, adapt and improve with effective Retrospectives
• Learn how Definition of Done impacts your software development process

Software Engineering Practices

During the three days, a lot of material from the Professional Scrum Developer Objective Domain is covered, including:

• Track progress with burn down charts
• Apply Test-Driven Development and a test-first approach
• Continuous Integration (and possibly Delivery and Deployment)
• Pair programming
• User stories and acceptance criteria
• Estimation techniques, including planning poker
• Refactoring, Clean Code and code smells
• Participants are required to bring a laptop with
• Eclipse (or IntelliJ IDEA)
• Git (or Mercurial client)
• Maven (or Ant or Gradle)
• Some Object Oriented programming skills
• Basic knowledge about JUnit and unit tests
• An open mind

Details

Included in the price is Scrum.org licenses, course material, refreshments, lunches and an individual password for taking the PSD I assessment.