Subscribe to our Erlang Factory newsletter to receive the latest updates and news

Introduction to Agile Development using Scrum

an image Target Audience: Everybody involved in software development: Developers, Testers, Project Managers, Architects, Business People, Team Leads

Prerequisites: No preparation required
• 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.

Goal: After this course attendees will be able to use the Scrum framework to drive continuous improvement, motivate people and achieve superior business results for everybody.
Duration: Two days.
Registration: 08:30 on 31 May 2012.
Venue: Business Center Bilpalatset
Description: 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


Jesper Boeg


Jesper is working as Agile Coach and Lean Process Consultant at Trifork A/S. He has a Masters degree from Aalborg University in the area of Information Systems and wrote his thesis on how to successfully manage distributed software teams.
Jesper has been working hands on with Agile and Lean for the past 5 years as Management Consultant, Trainer, Coach, Team Leader, Product Owner and Scrum Master and he is a frequent speaker at international conferences. With a relentless Lean focus Jesper helps teams adopt Agile practices and break down the organizational and personal boundaries standing in the way. He believes that lack of communication is the root to all evil, and trust can only be established through an unrelenting focus on transparency in the entire organization.
Lately Jesper has found the principles of software Kanban increasingly helpful in helping teams appreciate and adopt Lean principles to optimize their current processes; Moving away from the faith based and Cargo Cult implementations of Agile which have been far too predominant as Agile have spread throughout the industry.
Bringing “Agility back in Agile” have therefore been keywords for Jesper’s work lately. It is his experience that specific Agile Best Practices rule sets are enforced in many organizations. Ultimately restricting teams from using the resources at hand effectively and adapt to the context they are faced with. Jesper believes that to be successful in the long run projects cannot just copy the success of others but must understand why things work and how they should be adapted to fit each individual context.