Agile . since Jun 23 . Index . DOCs TOP TOC

Abstract


Many traditional software practices stress the importance of programming in Flow. XP directly challenges the assertion that Flow is critical and proclaims Pair Flow.

Both Flow states are fragile. They are easily disrupted by outside distraction or task rotation. Both take a long time to enter. Furthermore, it takes days for a given pair to be comfortable enough with each other to be able to achieve Pair Flow at all.

My team at Silver Platter discovered that there is a third option to achieve high-efficiency programming. Our team spent the majority of its time in Beginner’s Mind. Whereas Flow depends on stability, Beginner’s Mind depends on instability, yet provides similar efficiency gains to a constant state of Flow.

This paper discusses one approach to achieve a constant state of Beginner’s Mind. It shows how to use those most-central of agile programming practices — pairing and task allocation — to constantly reinforce this mind state.

 

Agile . since Jun 23 . Index . DOCs TOP TOC

Introduction


 |

The Project and Environment

Flow and Pair Flow

Beginner’s Mind

Competencies Versus Skills

Promiscuity and Pair Net

Agile . Index . DOCs . TOC