Introduction to Agile Development using Scrum

Target Audience: Project Managers/Team Leaders, Support and Test Engineers, Software Developers,

Prerequisites: No preparation required

Objectives:

• Understand the drivers behind Scrum
• Understand all Scrum terms, how the different roles interact, what artifacts are used how, importance of timeboxing meetings, etc.
• Appreciate the value in "Less is More", when it comes to requirements.
• Understand how to implement Scrum in practice.

Duration: Two days

 

The Waterfall and other variants of the "Big Design Up Front" models work under the assumption, that software development is a predictive process like that of building a car. But it is not! Software development is highly complex and influenced by a myriad of factors – which even change over time – such that the outcome cannot be defined by controlling the input.
In this course you will learn the basics of Agile software development and how to use Scrum to develop software in small steps (Sprints) and let the customer confirm on a regular basis that we are headed in the right direction. You will learn the Scrum Roles, Ceremonies and Artifacts and how Scrum sets free creative resources and motivates everybody involved.
After covering the basics we will move on to discuss relevant practices and tools related to Scrum and Agile development including: User Stories, Product Visions, Continuous improvement and how to apply Scrum in a Distributed context.
After the course you will be able to take the first steps to apply Agile and Scrum in your own context and get the economic and personal benefits of using the right methods for the domain of product development.

 

Course Contents


  • Motivation for agile software development
  • Motivation for the best practices applied by Scrum
  • Responsibilities of the Scrum roles (Team, SrcumMaster, Product Owner)
  • Content of the Scrum meetings (Sprint Planning, Daily Scrum, Sprint Demo, Sprint Retrospective)
  • Scrum Terms and Artifacts (Sprint, ScrumBoard, Burn Down Chart, Backlogs, "Done" & "Ready", Time boxing, Impediments, etc.)
  • How to write a good Product Backlog (User Stories)
  • Estimating User Stories and Tasks ("planning poker") 
  • Self-organization & self-management of teams
  • Utilizing the Scrum Board
  • Release planning in Scrum
  • Product Vision
  • Quality Built In
  • Continuous Improvement
  • Distributed Scrum