Yi Lv

Father of a 10-year old daughter, Agile coach and trainer

[Yi Lv @yi_lv]

How can organizations benefit from LeSS? 1) adopt LeSS frameworks; 2) use LeSS ideas for improvement. We seem having drifted to 1), and I'd like to promote 2) to get balanced.

https://t.co/37ah8pym1z

[Yi Lv @yi_lv]

@chethendrickson @KentBeck "miss the point" is sometimes a form of resistance. i notice it when i repeat that "you miss the point" for 3 times:-)

[Yi Lv @yi_lv]

a recent talk about from LeSS to learning organization through practicing systems thinking on product & process experiments.

https://t.co/v54zMhOgpi

[Yi Lv @yi_lv]

@michaeldotjames I wonder if the element of winning is an inherent part of argument/debate, even though some people would say that we argue/debate to learn. What is the right word that conveys curiosity and openness - dialogue?

[Yi Lv @yi_lv]

Systems thinking in product learning may begin from Impact Mapping; systems thinking in process learning may begin from Root Cause Analysis.

https://t.co/X7qgQZSHzh
https://t.co/nAX2px6wGk

[Yi Lv @yi_lv]

@agilepete @agilepete glad to hear about this, and thanks for asking. i would probably gather relevant people to do a system modeling about this experiment (why we do this, possible consequences, etc.) before starting, then check its effects regularly to learn and adapt.

[Yi Lv @yi_lv]

"Maximize dependencies between teams" for whole product focus! https://t.co/DAYwfNSc6q

[Yi Lv @yi_lv]

In fact, the fundamental change is the expansion of product definition! https://t.co/p3GkUCv0Lo

[Yi Lv @yi_lv]

Two different configurations of multi-team product group have different answers regarding whether to have a Product Group Owner: https://t.co/8yXSsHJ2OS

[Yi Lv @yi_lv]

LeSS vs. LeSS Huge, main differences: 1) RA or not; 2) all-at-once or evolutionary incremental approach.

https://t.co/lTJmNWtUhY

[Yi Lv @yi_lv]

Take advantage of being "sufficient but not necessary" to postpone RA and keep one PBL, https://t.co/3REz8GZPdk

[Yi Lv @yi_lv]

Prioritize together to increase the capability on prioritization and make it less limiting, https://t.co/9wtX1r1hgo

[Yi Lv @yi_lv]

Keep one PBL & get rid of separate PBLs, even when teams are not ready in taking over the clarification yet.

https://t.co/LsbQD3TpCU

[Yi Lv @yi_lv]

Working on a new series to explore how to break the limits to one product backlog, the first two are my old perspective and experience, and will write my latest thinking in the next articles.

https://t.co/IQYIxmwoGv
https://t.co/eUQNpiBNer

[Yi Lv @yi_lv]

We define RAs by whatever dimension that carries value, https://t.co/R0NhUYcMnc

[Yi Lv @yi_lv]

@JurgenLACoach happened to write about the same idea:-) https://t.co/3WwRYJh51Q

[Yi Lv @yi_lv]

The first step towards one product backlog could be ... a priority guideline, https://t.co/K5iLJAGEXE

[Yi Lv @yi_lv]

Just re-read the "code as design" article, and wonder if I should treat the design in mechanical engineering (what one of my clients is doing) as the code in software. If yes, then it would be "design as code"😉

[Yi Lv @yi_lv]

Percentage of people in special roles is a good indicator for the degree of self-organization in teams, https://t.co/3WwRYJh51Q

[Yi Lv @yi_lv]

Experiments are at the heart of LeSS; reasoning is at the heart of experiments. https://t.co/pJ1QkbusXt