Organization

Agile Development Ltd

Trainer

  • Course

    Date: 28-29 April, 2014
    Location: Aarhus, Denmark

    Regular Price: see registration

    Dette kursus holdes på Dansk - This class will be in Danish

    Læs om kursus på dansk ved at følge link.

    Agile project management is as radically different from traditional project management as agile processes are different from traditional methodologies. Rather than plan, instruct and direct, the agile project manager facilitates, coaches and leads. This person is called a ScrumMaster in the Scrum agile process to denote the difference and remind the person filling this role of the new responsibilities.Accepted participants learn how to be a ScrumMaster and how to make a development team, a project, or an organization agile. Exercises, case studies, and examples used to bring home the realization of how to be a ScrumMaster instead of a project manager.

    Goal

    Each individual is trained to be able to assume the following responsibilities:
    Remove the barriers between development and the customer so the customer directly drives development;
    Teach the customer how to maximize ROI and meet their objectives through Scrum;
    Improve the lives of the development team by facilitating creativity and empowerment;
    Improve the productivity of the development team in any way possible; and,
    Improve the engineering practices and tools so each increment of functionality is potentially shippable

    Trainer

    This class is taught by: Jens Oestergaard. Jens experience is wast, having been a Certied Scrum Trainer since 2004.

    Training

    The training is done with a lot of exercises. Be prepared to do hard work. The training will give you the feeling of Scrum itself.

    The first day is dedicated to the Why and the Philosophy, the Meaning of Scrum. The second day hands you the tools and the How of Scrum.

    Using anecdotes and experience, teaching the Scrum methodology, and how to use it to be an effective Agile project manager – you will learn to be a ScrumMaster.

     

     

    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: 28-29 April, 2014
    Location: Aarhus, Denmark

    Venue:
    Trifork
    Margrethepladsen 4
    Aarhus, Denmark
    http://www.trifork.dk

    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

     

  • Who Should Attend

    Suitable for anyone involved in product development, using Scrum.