Product Developers Practices

on-site course

 - 

Munich, Germany

 - 

English

 - FREE

Date: 
November
 
20
 - 
24
2023
Time:  
Daily from 
9:00 am
 to 
5:00 pm
 (CET)
 (CST)
Location: 
Language: 
GB Flag SVG.German SVG Flag.
English
Trainer: 
Host: 
Terry Yin
 &
Learn more

SOLD OUT 😢

Missed... 😢 -> ☝️📅

Product Developers PracticesProduct Developers PracticesRobert Briese is a proven expert and he is the lead trainer at Lean Sherpas GmbH.
Contact info@leansherpas.com to resolve your issues.
100% Money Back if
You Don't Like the Course
The Certified Less Practitioner Training is available either online or onsite / offline.
Pay Online Course and take part for Free OnSite
If any problems arise during or after your Certified Less Practitioner Training you can contact us over our dedicated Slack Group.
Lifetime Support over Dedicated Slack Group
Contact info@leansherpas.com to resolve your issues.
100% Money Back if
You Don't Like the Course
The Certified Less Practitioner Training is available either online or onsite / offline.
Pay Online Course and take part for Free OnSite
If any problems arise during or after your Certified Less Practitioner Training you can contact us over our dedicated Slack Group.
Lifetime Support over Dedicated Slack Group

Organizational Agility is constrained by Technical Agility. The 5-day development practice course is 70% hands-on and 30% lecture and has three main focuses: Large-Scale Scrum, technical practices, and authentic team dynamics.

Price

3-day Certified LeSS Practitioner (CLP®)
5-day Online Course: provisional LeSS Practitioner (pCLP®)
2-day On site LeSS & Learn

The standard price is 2,490.00€ (net) excl. VAT.
The early bird price, 5 weeks before the training is 1990.00€ (net) excl. VAT.
Group bookings of 3 people or more receive a 650.00€ discount per person on the standard price || Private courses on request.

The standard price is € (net) excl. VAT.
The early bird price, 5 weeks before the training is € (net) excl. VAT.
Group bookings of 3 people or more receive up to € discount per person on the standard price || Private courses on request.

Information about the course

  • A comprehensive 
    provisional 
    Certified LeSS Practitioner Training on organizational agility
  • Globally recognized 
    pCLP® & 
    CLP® Certificate from the LeSS Company®
  • Experience true agility during a simulation building a product

  • Practice new thinking tools that guide you in your transformation

  • Leave with action plans and resources

CLP Badge

The 5-day development practice course is 70% hands-on and 30% lecture and has three main focuses: Large-Scale Scrum, technical practices, and authentic team dynamics. It covers Scrum practices such as cross-team Sprint Planning, Backlog Refinement, working as a team, and many technical practices such as Test-Driven Development, Continuous Integration, Acceptance Test-Driven Development, and Refactoring. It also covers how to apply these practices in a legacy codebase situation.

Who is this class for:

We don't expect participants to have prior knowledge of the tech stack listed below, including the programming languages or domain. People are welcome to the class as long as they are fluent software developers.

We also allow 1~2 non-current developers (e.g., a ScrumMaster or PO) in each class, as long as they have some development experience and promise to work as a developer in a team in the class. So far, their feedback is even better than the developers:-) It's probably due to the opportunity to observe a team from within and the others doing their job.

Current Tech Stack:

We chose a particular stack so that people do real work in the class, but the specific stack doesn't matter so much for participation. Our current stack is:

  • a web service (https://doughnut.odd-e.com)
  • VueJS 3 on the frontend using TypeScript
  • Spring Boot backend using Java and MySQL
  • various external service dependencies
  • Cypress for end-to-end testing
  • Github Action for CI/CD
  • Google Cloud for production

The source code is here: https://github.com/nerds-odd-e/doughnut

Monday:

  • Requirement workshop / A-TDD
  • Definition of Done
  • Cucumber and Friends
  • Sprint Plannings

Tuesday:

  • Test-Driven Development
  • Collaboration (Working in teams, SCM, Build Automation and other tools, Pair Programming, Continuous Integration and CI Systems, Collective Code Ownership)

Wednesday:

  • Code Smells & Refactoring
  • Thinking about test and test automation (Testing Pyramid, Mocking, Unit testing in other languages: JavaScript, Python, etc., Good Unit Testing

Thursday:

  • Thinking about Design
  • Feature Team Revisit

Friday:

  • Working with Legacy Code
  • Craftsmanship
  • Retrospective

Details :

Product Backlog Refinement Workshop

In Large-Scale Scrum, the PBR workshop is one of the most critical activities. By doing the workshop in the sprint with multiple teams, we will cover the three essential aspects of this workshop: splitting big items, detailing the items, and estimating. Some optional techniques we might cover based on the situation include: impact mapping, storying mapping, specification by example, estimation ceremonies, etc.

Definition of Done

What is the purpose of the Definition of Done? We will also talk about what it is about, how to use it, and who should ensure it.

Sprint Plannings

(Cross-team) Sprint Planning Part One is mainly covered by the PBR workshop since there's only one sprint. Sprint Planning Part Two will be explained and practiced in detail.

Acceptance Test-Driven Development with Cucumber and Friends

This part explains how to drive the iteration with the examples derived from the PBR workshop. We will discuss the detailed technical approaches, good practices, and conventions.

The actual teaching or lecture is usually delayed to the next couple of days until the participants have real experience struggling with the tools and process. Most of the learning should be from the practices and on-time coaching from the course instructors. Same as all the other technical practices

Test-Driven Development

From day 2, all the code needs to be written by TDD. Same as described above, We will explain the philosophy very quickly with a simple exercise. Most of the learning should come from hands-on coaching and practicing.

Collaboration

This part explains the fundamental techniques and practices that enable teams to collaborate in a Large-Scale Scrum situation. Including:

  • Working in teams
  • SCM, Build Automation, and other tools
  • Pair Programming
  • Continuous Integration and CI Systems
  • Collective Code Ownership

The above is getting the participant ready to understand why things are happening in the way they are in Large-Scale Scrum.

Code Refactoring

This part covers the why, what, and how of code refactoring. We'll train people to have the nose to smell bad code and the techniques to remove the bad smells.

More on Test Automation

With both the automated acceptance test and unit test covered in the course, in this part, we go deeper into (automated) testing. Including:

  • Real testing/exploratory testing
  • Product-wise testing strategies
  • Good automated testing
  • Unit testing other programming languages

Thinking about Design

Here we discuss the difference between emergent design and the traditional design style that often happens in a waterfall process.

On top of that, we also talk about the design principles and paradigms.

Thinking about "real testing", again

Feature Teams

With all gained knowledge from the first four days, we will finally explore this organizational structure topic again and see the links between the technical practices and team approaching and feature teams.

Legacy Code

Based on the book by Michael Feathers, Working Effectively With Legacy Code, we discuss the way of working when the code is without good test coverage, and the knowledge about how the code works is lost.

Craftsmanship

We will discuss the alternative metaphor for software practitioners to map their careers and guide them.

Retrospectives

The training is over, the teams created in the course won't continue (usually). We will try to give people an experience of a good retrospective, learn to identify bad smells in a retrospective, and learn good techniques for running a retrospective. We will also cover how large organizations do retrospectives.

It's hard to document what we do in the course precisely. Because every time the teams will be working on different product backlog items and continue the product left by the previous class, many contents will be emergent.

Monday:

  • Requirement workshop / A-TDD
  • Definition of Done
  • Cucumber and Friends
  • Sprint Plannings

Tuesday:

  • Test-Driven Development
  • Collaboration (Working in teams, SCM, Build Automation and other tools, Pair Programming, Continuous Integration and CI Systems, Collective Code Ownership)

Wednesday:

  • Code Smells & Refactoring
  • Thinking about test and test automation (Testing Pyramid, Mocking, Unit testing in other languages: JavaScript, Python, etc., Good Unit Testing

Thursday:

  • Thinking about Design
  • Feature Team Revisit

Friday:

  • Working with Legacy Code
  • Craftsmanship
  • Retrospective

Details :

Product Backlog Refinement Workshop

In Large-Scale Scrum, the PBR workshop is one of the most critical activities. By doing the workshop in the sprint with multiple teams, we will cover the three essential aspects of this workshop: splitting big items, detailing the items, and estimating. Some optional techniques we might cover based on the situation include: impact mapping, storying mapping, specification by example, estimation ceremonies, etc.

Definition of Done

What is the purpose of the Definition of Done? We will also talk about what it is about, how to use it, and who should ensure it.

Sprint Plannings

(Cross-team) Sprint Planning Part One is mainly covered by the PBR workshop since there's only one sprint. Sprint Planning Part Two will be explained and practiced in detail.

Acceptance Test-Driven Development with Cucumber and Friends

This part explains how to drive the iteration with the examples derived from the PBR workshop. We will discuss the detailed technical approaches, good practices, and conventions.

The actual teaching or lecture is usually delayed to the next couple of days until the participants have real experience struggling with the tools and process. Most of the learning should be from the practices and on-time coaching from the course instructors. Same as all the other technical practices

Test-Driven Development

From day 2, all the code needs to be written by TDD. Same as described above, We will explain the philosophy very quickly with a simple exercise. Most of the learning should come from hands-on coaching and practicing.

Collaboration

This part explains the fundamental techniques and practices that enable teams to collaborate in a Large-Scale Scrum situation. Including:

  • Working in teams
  • SCM, Build Automation, and other tools
  • Pair Programming
  • Continuous Integration and CI Systems
  • Collective Code Ownership

The above is getting the participant ready to understand why things are happening in the way they are in Large-Scale Scrum.

Code Refactoring

This part covers the why, what, and how of code refactoring. We'll train people to have the nose to smell bad code and the techniques to remove the bad smells.

More on Test Automation

With both the automated acceptance test and unit test covered in the course, in this part, we go deeper into (automated) testing. Including:

  • Real testing/exploratory testing
  • Product-wise testing strategies
  • Good automated testing
  • Unit testing other programming languages

Thinking about Design

Here we discuss the difference between emergent design and the traditional design style that often happens in a waterfall process.

On top of that, we also talk about the design principles and paradigms.

Thinking about "real testing", again

Feature Teams

With all gained knowledge from the first four days, we will finally explore this organizational structure topic again and see the links between the technical practices and team approaching and feature teams.

Legacy Code

Based on the book by Michael Feathers, Working Effectively With Legacy Code, we discuss the way of working when the code is without good test coverage, and the knowledge about how the code works is lost.

Craftsmanship

We will discuss the alternative metaphor for software practitioners to map their careers and guide them.

Retrospectives

The training is over, the teams created in the course won't continue (usually). We will try to give people an experience of a good retrospective, learn to identify bad smells in a retrospective, and learn good techniques for running a retrospective. We will also cover how large organizations do retrospectives.

It's hard to document what we do in the course precisely. Because every time the teams will be working on different product backlog items and continue the product left by the previous class, many contents will be emergent.

Certification

At the end of the course you will receive the 
p
CLP certification and an account on less.works. (❗ You must be present at least 90% of the time to receive the certificate).
Furthermore, after attending the course, you can claim up to 25 SEUs (Scrum Education Units) of category C for the Scrum Alliance CSP (Certified Scrum Professional).

A possible later on site certification as Certfied LeSS Practitioner is included in the price || however, catering costs and pro rata seminar room costs are to be borne by the participant.

  • Team- and organizational coaches

  • Agile coaches

  • Scrum Master

  • Organizational leaders and senior managers

  • Product Owner, produkt managers and stakeholders

  • Software engineers, hands-on technologists, designers

  • Business consultants

  • Eveyone who wants to know more about Scrum

Prerequisites

The only prerequisite to this Large-Scale Scrum Course is basic Scrum knowledge. That can be picked up by attending a Certified Scrum Master or a Professional Scrum Master course, or thoroughly reading Scrum introduction material such as the Scrum Primer and practicing Scrum.

You need a stable and fast Internet connection, a webcam, a headset, and an environment where you can focus and interact with others online if needed.

Recommended Preparation

Large-Scale Scrum Course participants should review Scrum introduction material such as the Scrum Primer. Another great preparation for this Course is the Scrum Test on less.works. It’s strongly encouraged to do this test before attending the course.

Event Information

  • What awaits you in a Certified LeSS Practitioner course:

    Centricity: Our locations are as central and as easy to reach as possible.

    Engagement: Our courses are designed to incorporate interactive tasks as well as group exercises, in order to create the best possible learning experience.

    Equipment: All equipment required for the course (e.g. workbooks) is provided for you by us.

    Food & drink: We provide vegan and gluten-free catering options and are happy to accommodate other allergies/intolerances as well. Just let us know your preferences.

SOLD OUT 😢

Missed... 😢 -> ☝️📅

Feedback from participants

No items found.

About the Trainer

s

Erfahrungen & Bewertungen zu Robert Briese

Terry Yin is a programmer for life, a reflective practitioner. He has rich experience in the software industry. Terry has been working at Nokia for 10 years mostly in R&D management and Adaptive transformation before joining Odd-e. He has coached Large Scale Scrum and software development technical practices in a large variety of software companies. Terry has been an active programmer for more than 25 years, crossing many domains. He’s open source software static analyser (https://github.com/terryyin/lizard) is used in many large organization, e.g. Nokia, Ericsson and even the Atlas experiment at CERN. He's also the developer of the https://less.works web site. He’s also an experienced trainer and conference speaker.

SOLD OUT 😢

Missed... 😢 -> ☝️📅

More events you might like:

Large-Scale Scrum – Certified LeSS Practitioner
Jul 2, 2024
German SVG Flag.GB Flag SVG.
Cologne, Germany
 - 
CLP®
 - 
German
Large-Scale Scrum – Certified LeSS Practitioner

Learn how to simplify your organization by being agile instead of just pretending. Use a unique opportunity to learn from 2 certified LeSS trainers the key thinking and organizational tools behind a lean enterprise. This course is in German language.

Large-Scale Scrum – Certified LeSS Practitioner
Jun 5, 2024
German SVG Flag.GB Flag SVG.
Hamburg, Germany
 - 
CLP®
 - 
German
Large-Scale Scrum – Certified LeSS Practitioner

In this 3-day workshop, you will explore an organizational design methodology that optimizes your organization for adaptability and simultaneously creates value for your company and customers. Learn how to apply Scrum principles to your entire organization by utilizing LeSS (Large-Scale Scrum), thereby promoting comprehensive integration for effective results in today's dynamic business environment.

Certified LeSS Practitioner
Jul 10, 2024
German SVG Flag.GB Flag SVG.
Munich, Germany
 - 
CLP®
 - 
German
Certified LeSS Practitioner

Learn how to simplify your organization by being agile instead of just pretending. Join Konstantin Ribel (one of very few certified LeSS trainers worldwide) for a three-day course in Munich to learn the key thinking and organizational tools behind a lean enterprise. This course is in German language.

Success! 🎉🎉 Thank you for your registration, Name.

Welcome to Lean Sherpas. ✨
You will receive all the details for booking in a few minutes by email: Email

Your to-do list before the training starting Datum:

✔️ Follow us on LinkedIn
✔️ Take the scrum test on LeSS.works
✔️ Book an introductory meeting with the Team
✔️ Add the training to your calendar

Meet the Team×