Coach’s Tools – Coaching, Consulting, Training

Below, are some light-weight coaching tools that can be effectively used in conversations with customers (classroom setting and individual discussions):

Impact of appropriate motivation on individual’s ability to evolve: relation of Evolution of Human Operating System on Evolution of Tribal (Organizational) System:
Individual Performance, Incentives, Bonuses Effect of individual performance appraisals and subjective/discretionary allocation of monetary intensives on organizational health. Conventional (more traumatizing) ways to allocate intensives.
Individual Performance, Incentives, Bonuses Effect of individual performance appraisals and subjective/discretionary allocation of monetary intensives on organizational health. Alternative (less traumatizing) ways to allocate intensives.
Roles & Responsibilities in basic Scrum and Large Scale Scrum (LeSS) settings:
Organizational Ecosystem: correlation between system variables at various System levels
Causal Loop Diagrams (CLD) & System Thinking – Example 1
Causal Loop Diagrams (CLD) & System Thinking – Example 2
Mind Maps Cheat Sheet for Class use: Color
Mind Maps Cheat Sheet for Class use: Black & White
LeSS “Hexagon of Values”
Organizational Flattening with LeSS
“WBS” (agile way) – 1 pager
Understanding Scrum Roles through System Modelling (CLD)
Understanding Root Causes of Command & Control Behavior through System Modelling (CLD)
Product Definition Expansion Work-sheet
Agile Vendor Selection Cheat-Sheet
Agile Intro – 1-pager
How to Ensure Effective Coaching?
Samples of Agile Metrics
Challenges With Agile Training: Examples, Reasons, Consequences
Scrum Anti-Patterns (not all are equally easy to identify)
Agile Self-Assessment Worksheet (ASAW)
LeSS Game: Team Design (Feature Teams vs. Component Teams)
Crossword “Legacy Ecosystem”
The 5 WHYs: Getting to a Root Cause

LeSS – Large-Scale Scrum Site

Playing with words September 11, 2020

Harmful Agile Adoptions by Playing with Words This is an ad-hoc post written out of pure frustration with many so-called AGILE adoptions. Everywhere I go, new fancy names get adopted for old concepts without any behavioral change. The most common is a mixture of Scrum terms and “spotify model” terms. It would be good if […]

basvodde

The path of least resistance towards one backlog August 18, 2020

(Originally published by Lv Yi on Oct 3, 2019) How could we create a path of least resistance towards one backlog? A collection of multiple backlogs is NOT one backlog Assuming that multiple teams are working on the same product, the following is a typical conversation between me and a friend in the community or […]

yi-lv

Reasoning before measuring August 4, 2020

(Originally published by Lv Yi on May 7, 2020) I often get this question – what do you measure while adopting Agile? The conversation usually goes like this: [me] What is it about adopting Agile? [him] … doing Scrum. [me] What effect do you expect after adopting Agile? [him] higher efficiency. [me] How would you […]

yi-lv

We love individual responsibility more than we would admit July 28, 2020

(Originally published by Lv Yi on June 8, 2020) When a team responsible for “A” (be it a function, component or customer domain) grows too big, we split it into two teams, responsible for the subsets of “A” that are as independent as possible (the left side). Why is it so natural to do this, […]

yi-lv

Team Leader vs Product Owner and ScrumMaster for component team July 21, 2020

(Originally published by Lv Yi on June 3, 2018) [Team Leader = TL; Product Owner = PO; ScrumMaster = SM] Real Scrum requires significant organizational redesign. I have seen two common settings to pilot Scrum: 1) project group and 2) component team. As those are existing structures, it is convenient to just use them. However, […]

yi-lv