A Loopian Dictionary – Tom and Geri Scrum

There are hundreds and hundreds of control loops to document in agile if we really want to understand how agile works. I thought I would re-document my feedback loops posted previously in a more loopian vocabulary. This will either be interesting, or incomprehensible, or perhaps both.

Loop: A completed feedback cycle.
Loops: Plural of Loop. The name of the process.
Looped: Past tense of Loop. The process of having feedback provided to you.
S-Looped: A loop where the feedback may be provided on a second by second basis.
M-Looped: A loop where the feedback may be provided on a minute by minute basis.
H-Looped: A loop where the feedback may be provided on a hour by hour basis.
D-Looped: A loop where the feedback may be provided on a day by day basis.
Loopy: Someone working in Loops.
Aloopy: An automated process/daemon running in Loops to provide automated feedback.

Putting these definitions together we could get:

loopy s-looped: Someone providing feedback on a second by second basis, usually through pairing.

aloopy s-looped: Something providing feedback on a second by second basis.

Here, rewritten, are the loops listed in a previous post:

As a loopy, I want my design ideas loopy s-looped so I do not get stuck and waste time.
As a loopy, I want my variable names loopy s-looped for clarity so the code is easier to maintain the very first time it is checked in.
As a loopy, I want my class/function names loopy s-looped for clarity so the code is easier to maintain the very first time it is checked in.
As a loopy, I want my each line of code loopy s-looped for clarity so the code is easier to maintain the very first time it is checked in.
As a loopy, I want each line of code loopy s-looped for logic errors to reduce errors in the code the very first time it is checked in.

Writing a few more loops this way:

As a loopy, I want my token of code aloopy s-looped as I type for syntax errors so no syntax errors are introduced as I type.
As a loopy, I want each function of code I am editing aloopy s-looped as I type for unit correctness so I do not have to wait to run all the unit tests to see that this code is accurate. **
As a loopy, I want all units dependent on the code I am editing aloopy m-looped for unit correctness so I know if I am breaking code in dependent systems before I check the code into production.

** A new development environment feature? You start thinking up all sorts of new features when you start thinking in terms of loops and in terms of leveraging all of this processing power that is mostly being wasted.

-Tom