Agile Saturation State
This post is a non-scientific commentary to the static analysis of some graphs (which still can not be published, because they are particleboard). All facts are fictional, all names are changed.
Imagine building a house ...
One builds a clutch.
Another cuts holes in the walls for windows.
')
The third one is trying to insert frames, but while he was running behind the glass, someone had already scored everything with plywood.
The fourth bricked holes in the walls.
The fifth puts electrical wiring. When at a plinth, when on a floor on a diagonal, because it is faster.
The fifth decided that the sign "Do not turn on!" People are working! ”Is too commanding and replaced by“ Caution! High voltage!"
The sixth tried to turn on the drill, cursed, ran to the shield, cursed again, tore off the plate and turned on all the switches.
Seventh…
In the midst of this, the foreman blinked, asking how many bricks were laid, how many windows were cut, how many holes were punched, how many meters of electrical wiring were connected and whether anyone else had any comments.
This shows that the most important for any agile project are two terms:
The task of an experienced specialist to go with the increase after the occurrence of the first, but before the second.
Imagine building a house ...
One builds a clutch.
Another cuts holes in the walls for windows.
')
The third one is trying to insert frames, but while he was running behind the glass, someone had already scored everything with plywood.
The fourth bricked holes in the walls.
The fifth puts electrical wiring. When at a plinth, when on a floor on a diagonal, because it is faster.
The fifth decided that the sign "Do not turn on!" People are working! ”Is too commanding and replaced by“ Caution! High voltage!"
The sixth tried to turn on the drill, cursed, ran to the shield, cursed again, tore off the plate and turned on all the switches.
Seventh…
In the midst of this, the foreman blinked, asking how many bricks were laid, how many windows were cut, how many holes were punched, how many meters of electrical wiring were connected and whether anyone else had any comments.
This shows that the most important for any agile project are two terms:
- T us , when the system becomes saturated with errors and the rate of making new increases to the rate of eliminating old ones.
- T na , when the customer understands that the final result will not be not only in the foreseeable future, but also in the future boundless, and covers the shop.
The task of an experienced specialist to go with the increase after the occurrence of the first, but before the second.
Source: https://habr.com/ru/post/286364/
All Articles