Description

This internship will allow you to experience a Scrum project, playing the role of a member of the development team. Thanks to the implementation of successive sprint simulations, with their challenges and deadlines, you will experiment with agile techniques and be ready to integrate a SCRUM project.

Who is this training for ?

For whom ?

Developers, Scrum Masters, team leaders, architects

Prerequisites

Training objectives

Master agile developer techniques Lead sprint planning, daily scrum, demo and retrospective meetings Carry out load estimates as a team Establish a task board and generate the sprint burndown chart

Training program

• Launch of the workshop
  • Presentation of the objective: experience the phases of a Scrum project over one day, in the role of a developer.
  • Detail of the content of the days, development of 'an agenda and distribution of roles.
  • Presentation of the context of the project and the common thread application.
  • Exchanges Discovery of the approach.
• Kata: automated tests
  • Description of the test driven development (TDD) approach and its benefits.
  • 3A approach: Actor, Action, Assertion.
  • Presentation of the different testing strategies.
  • Boundary condition tests.
  • Tests on error cases and exceptions.
  • Performance tests.
  • Stress tests.
  • Load tests.
  • Scenario Dojo writing tests before the code: unit tests of the requirements of the common thread application.
• Kata: principles of Object Oriented design
  • rnSRP: single responsibility principle.
  • OCP: opening/closing principle.
  • LSP: Liskov substitution principle.
  • Expert principle.
  • DRY principle: Don't Repeat Yourself.
  • KISS principle: Keep It Simple Stupid.
  • Scenario rnDojo: object-oriented design principles.
  • Design and development of the functionalities of the common thread application taking into account object design principles.
• Kata: principle of independence
  • Reminder of the interest of polymorphism.
  • DIP: principle of dependency inversion.
  • ISP: reduction of apparent complexity by separation of interfaces.
  • Operating principle of doubles.
  • Interest of decoupled tests.
  • Impact on crossed tests.
  • Put in situation Dojo: decoupled tests.
  • Creation of Mocks and implementation of decoupled tests in the common thread application.
• Kata : refactorisation des packages
  • Introduction to package quality guidance.
  • Coding GRIn.
  • DIP, CCP, CRP rules and common function.
  • Package metrics.
  • Measurement tools.
  • Principle of refactoring.
  • Consequence of technical debt and risk of code "breakage" .
  • Scenario Dojo: use of the measurement tool and refactoring of the red thread application code