Organization

Agile Development Ltd

Trainer

  • Course

    Date: 17-18 September, 2013
    Location: København, Denmark

    Regular Price: 12 500 DKK

    Formålet med dette kursus er at certificere deltagerne som Scrum Masters. Deltagerne vil lære hvordan man coacher og leder et udviklingsteam, et projekt eller en organisation på vejen mod agilitet. Øvelser, case studies og eksempler anvendes til at forstå, hvordan man bliver en succesfuld Scrum Master

    Kursusdeltagerne trænes i: • at nedbryde barrierer mellem udvikling og kunde • at lære kunden hvorledes man maksimerer ROI og opnå de fastsatte mål ved hjælp af Scrum • at forbedre udviklingsteamets arbejdsforhold • at forbedre udviklingsteamets produktivitet • at forbedre udviklingsmetoder, værktøjer og funktionalitet

    Som certificeret Scrum Master er du autoriseret til at deltage i udviklingen af Scrum metodikken.

    Målgruppe og forudsætninger

    Udgangspunktet for at deltage i Scrum certificeringen er forståelse for det basale i projektledelse samt et ønske om at vide mere om, hvordan Scrum fungerer og implementeres i en organisation. Deltagerne kan være projektledere, administrative ledere, udviklere el. lignende, der har erfaring med projekter, der har til formål at udvikle eller forbedrer services eller produkter. Forudsætningen for at deltage er, at deltageren har læst minimum én af Scrum bøgerne som f.eks. Agile Software Development with SCRUM, by Ken Schwaber, Mike Beedle

    Underviser – Jens Østergaard

    Jens Østergaard har mange års erfaring med at undervise og praktisere Scrum. Jens underviser både på Dansk og Engelsk og certificere deltagerne som Scrum Masters. Ved hjælp af anekdoter og erfaringer underviser Jens i Scrum metodikken og fortæller hvordan Scrum anvendes effektivt af en agil projektleder. Igennem 20 år har Jens arbejdet som udvikler, dba, teamleader, projekt leder og Scrum Master. Han har arbejdet med alle aspekter af software udvikling og har gennem årene ledet flere Scrum projekter. Kurset gennemgår de basale komponenter af den agile proces Scrum; herunder ledelse, planlægning og scaling af Scrum projekter.

    All CSM courses are taught by Certified Scrum Trainers. Taking a CSM course, passing the CSM test, and accepting the license agreement designates you as a Certified ScrumMaster, which indicates that you have been introduced to and understand the basic concepts you need to perform as a ScrumMaster or team member on a Scrum team. This course also satisfies two elements of the CSD track: Scrum Introduction and Elective.

  • Details

    Date: 17-18 September, 2013
    Location: København, Denmark

    Venue:
    Trifork A/S
    Spotorno Allé 4
    DK-2630 Taastrup
    København, Denmark
    Get Directions

    Regular Price: 12 500 DKK

  • Agenda
    • Why Agile

      • Opacity of waterfall
      • Emergence
      • Processes
      • Patterns

      Overview of Scrum

      • Agile Principles    
      • Brief History of Scrum
      • Heart of Scrum
      • Scrum Overview
      • Emergency Procedure

       Roles

      • Overview of the roles
      • Mixing the roles

       DONE

      • Why DONE
      • Advantage of DONE
      • How to create a definition of DONE

      Product backlog

      • Product Backlog Items (PBIs), User stories and other choices on the Product Backlog
      • Backlog Meetings
      • INVEST in your Product Backlog
      • Estimating your PBI's

      Retrospective

      • Pupose of Retrospective
      • Techniques for Retrospective

      Agile Contract

      • Traditional Contract
      • Agile Contract

      The ScrumMaster

      • Responsibilities and mindset
      • How to react in different scenarios
      • Scrum Master's empidiment list

       The Product Owner

      • Description and responsibilities
      • Character of a good Product Owner
      • Product Owner team

      The Development team

      • Composition and cross-functionality
      • Responsibilities of the Team Member
      • Organizing
      • What to do with dysfunctional Team Members
      • Distributed Teams

      Sprintplanning

      • Part 1 and Part 2
      • Sprintplanning, how to get from the what to the how
      • How the team commit to the scope of the sprint
      • Sprintbacklog as spreadsheet, on the wall or in a tool

      The Sprint

      • Responsibilities in the sprint
      • Updating progress
      • Burndown chart

      Daily Scfrum

      • Who can say what
      • Why it is important the team feels ownership

      Sprintreview

      • Pupose of meeting
      • A review not a demo

      Release Planning

      • Allocating Sprints
      • Tracking progress – the Release Burndown
      • What to expect

       Scaling

      • From one team to many
      • Cordination between teams (Integration Scrum)
      • Multi Product Backlogs or one Product Backlog
      • Sprintplanning from one Product Backlog for many Teams

      The End

      • Group Photo
      • Discussion about of where to go from here