Your ORGANIZATIONAL AGILITY will quickly become LIMITED by your team’s TECHNICAL ABILITY.

Further Details

Product Backlog Refinement Workshop

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

Definition of Done

Sprint Planning

(Cross-team) Sprint Planning Part One is mostly 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

Explores how to drive the iteration with the examples derived from the PBR workshop. Detailed technical approach, good practices and conventions are discussed here.

The actual teaching or lecture is usually delayed to the next a couple of days until the participants had some 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 need to be written by TDD. Same as described above, the philosophy will be explained very quickly, most of the learning should come from hands-on coaching and practicing.

Collaboration 

Explores the fundamental techniques and practices that enable teams to collaboration in a Large-Scale Scrum situation. Including:

• Working in teams

  1. SCM, Build Automation and other tools

  2. Pair Programming

  3. Continuous Integration and CI Systems

  4. Collective Code Ownership

This is getting ready for the participant to really understand why things are happening in the way they are in Large-Scale Scrum.

Code Refactoring

Explores the why, what and how of code refactoring. We’ll train people to have the nose to smell bad code and also 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

Explore the difference between emergent design and the traditional style of design that happens often in a waterfall process.

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

Feature Teams

With all gained knowledge from the first 4 days, we 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 not maintained with good test coverage and the knowledge about how the code works is lost.

Craftsmanship

During this one of the final part where we discuss the alternative metaphor for software practitioners to map to their career and guide them.

Retrospectives

About the Trainer

Terry Yin is an coach of Odd-e. He has 20 years experience in the software industry. Terry has been working at Nokia for 10 years mostly in R&D management and Agile 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 an experienced trainer and conference speaker.