Certified ScrumMaster®

Jens & Poul

Organization

Agile Development Ltd

Trainer

  • Course

    Date: 31 March - 1 April, 2014
    Location: Høje Taastrup, Denmark

    Regular Price: See registration

    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 indenfor Scrumalliance rammer.

    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 og Poul Staal Vinje

    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: 31 March - 1 April, 2014
    Location: Høje Taastrup, Denmark

    Venue:
    Teknologisk Institut
    Bygning 6
    Gregersensvej
    Høje Taastrup, 2630 Denmark
    Get Directions

    Regular Price: See registration

  • 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
      Purpose 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 impediment 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

      Sprint Planning
      Sprint Planning, how to get from the what to the how
      How the team commit to the sprint
      Sprint Backlog as spreadsheet, on the wall or in a tool

      The Sprint
      Responsibilities in the sprint
      Updating progress
      Burndown chart

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

      Sprint Review
      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
      Coordination between teams (Integration Scrum)
      Multi Product Backlogs or one Product Backlog
      Sprint Planning from one Product Backlog for many Teams

      The End
      Group Photo
      Discussion about of where to go from here