SCRUM PRACTICAL OVERVIEW (1 Day)

Group price 2950€

Training participants will get an overview of why, when, and how agile and scrum have emerged, theoretical bases behind scrum ceremonies, roles, and artefacts. You will practice a short scrum in 4 iterations and answer your questions.



Category:
Description
  1. Intro to Agile and Lean

    This short introductory course will cover the historical background of the waterfall, lean and agile, explain how deterministic and empirical models influence software development and why the empirical model works better in a constantly changing business environment.

    Training provides an overview of the continuous product and process improvement that can achieve with shorter feedback cycles and constant inspection and adoption run by your people.

    Participants will get an overview of:

    • Why Agile and Scrum roots
    • Disciplined/scientific agile development
    • Agile requirements gathering
    • Agile estimation and planning
    • Scrum roles (Product Owner, ScrumMaster, Development team) and their responsibilities
    • Scrum working process (Planning, Daily StandUp, Demonstration, Retrospective)
    • Backlog management, Task management, Progress tracking
    • Quality improvement techniques and tools (test-automation, TDD)

    Topics: Agile, Lean, Scrum, Hypotheses, Validation, Experiments, Learning, TDD, Deterministic, Empirical, Agile manifesto, Backlog, Planning poker, User Story, Sprint, Daily Standup, Definition of Done (DoD), Taskboard, Burn Down/Up chart

  2. Agenda
    • Practising Retrospective
    • The theory behind the agile process:
      • Agile and Lean history
      • Deterministic and Empirical models
    • Agile requirements and backlog management
    • Agile estimation (including practising Planning Poker)
    • Scrum framework (Roles, Artifacts, Ceremonies)
    • Scrum simulation (4 full sprint cycles)
    • Organisational setup (org. structure, tools, support)
    • Risks of/in implementation of Scrum
    • Questions and answers
  3. Learning methods

    Practical simulation. Handy theory for laying down the bases. Discussions. Cases and stories.

  4. Course structure & Ease of implementation
    50Theory %
    50Active learning %
    50Practical %
  5. About trainer

    Scrum.ee OÜ is offering agile and Scrum consultancy, coaching and training courses since 2008.

    Trainer Alek Kozlov has an IT management master degree from Estonian Business School. Alek’s is the Scrum.ee founder, business consultant and coach. Also, he is a trainer at Tallinn Technical University and DevTraining. Alek is one of Agile Estonia co-founders.

    Alek practises incremental and iterative approaches since 2002, Agile and Scrum since 2004, and has been helping other companies embrace the agile mindset and Scrum practices since 2009. Alek is a Certified Scrum Practitioner (CSP), ScrumMaster (CSM) and Product Owner (CSPO), Large-Scale Scrum (LeSS) practitioner, Innovation Games facilitator and passionate product/service designer.

    Alek was the first full-time Skype agile coach responsible for planning, executing, and supporting teams in their Scrum transition. He has been working with Skype, Teleia, Pipedrive, Skeleton Technologies, Insly, Helmes, Tieto Estonia, SMIT, Töötukassa, TTP and many other organisations different industries.

  6. Disclaimer

    Price does not include trainer’s travel and accommodation costs. Please contact us for details.

Who should attend

Business Managers
Product Managers
Business Analyst
Product Owners
Procurement specialists
Lawyers
Bookkeepers
Marketing specialists

  1. Level & Prerequisites

    Level: Basic overview of the scrum development process

    Prerequisites: No prerequisites required

What I will get

After this one day training participant will able to start using agile planning estimation technique to start from business side his/her work with practising scrum team.

Training will equip participants with good overview of scrum ceremonies (meetings), roles and artifacts just enough to be able to cooperate with your development partners, to compare your team/partner current working process with official scrum and will be able to identify improvements and next steps.