article: add notes to pull system article

This commit is contained in:
Julien Calixte
2024-12-23 11:07:25 +01:00
parent 5921f6cb45
commit 3746f8d02f
6 changed files with 33 additions and 7 deletions

View File

@@ -78,7 +78,6 @@ input[type='submit'] {
text-align: center; text-align: center;
text-decoration: none; text-decoration: none;
text-transform: uppercase; text-transform: uppercase;
margin: 1rem 0;
} }
.button.button-outline, .button.button-outline,

View File

@@ -9,5 +9,6 @@
consequences of different strategy patterns and which is the most consequences of different strategy patterns and which is the most
effective. effective.
</p> </p>
<p><em>Note: better experience on desktop.</em></p>
</div> </div>
</template> </template>

View File

@@ -1,9 +1,20 @@
<template> <template>
<div class="flow-conclusion"> <div class="flow-conclusion">
<p>
Okay, now we're pretty sure! For a long time, I wanted a proof
<em>to trust the process</em>, that's the beauty of simulations. . It's
quite impossible to convince people when we're in the middle of the
battle. If teams change every time, you are doomed to get this problem
over and over again.
</p>
<p> <p>
Teams tend to underestimate how long a project will be. And how hard it Teams tend to underestimate how long a project will be. And how hard it
will be to work with others. will be to work with others.
</p> </p>
<p>
Note that problem solving is always a good practice. The capacity of the
team to stop and think about how they work is critical.
</p>
<p> <p>
If we're not in a good pace, we just have to try harder. Only once. "Just If we're not in a good pace, we just have to try harder. Only once. "Just
in time" becomes "Just this time" many times. So teams overproduce. in time" becomes "Just this time" many times. So teams overproduce.

View File

@@ -1,9 +1,20 @@
<template> <template>
<div class="flow-conclusion"> <div class="flow-conclusion">
<p>Pull system wins!</p>
<p> <p>
Let's make sure it wasn't luck and generate 200 projects delivering 200 Pull system wins! The fact that
features each! And see what happens. <a
target="_blank"
rel="noopener noreferrer"
href="https://journals.aps.org/pre/abstract/10.1103/PhysRevE.96.052303#:~:text=The%20%E2%80%9Cfaster%2Dis%2Dslower,evacuation%20time%20can%20be%20achieved"
>faster is slower</a
>
is counter-intuitive but it is a fact. The more we push the more we are
slowing down the system.
</p>
<p>
Before any conclusion, comparing two simulations is not enough. Let's be
more scientific here and let's generate 200 projects delivering 200
features each and see what happens.
</p> </p>
</div> </div>
</template> </template>

View File

@@ -48,6 +48,10 @@ const featureStore = useFeatureStore()
.row { .row {
display: flex; display: flex;
justify-content: center; justify-content: center;
button {
margin: 1rem 0;
}
} }
} }
</style> </style>

View File

@@ -37,13 +37,13 @@ const simulateEverything = () => {
class="button button-outline" class="button button-outline"
@click="simulationStore.multiSimulation(1, 'push-dps')" @click="simulationStore.multiSimulation(1, 'push-dps')"
> >
simulate push with DPS simulate push with problem solving
</button> </button>
<button <button
class="button button-outline" class="button button-outline"
@click="simulationStore.multiSimulation(1, 'pull-dps')" @click="simulationStore.multiSimulation(1, 'pull-dps')"
> >
simulate pull with DPS simulate pull with problem solving
</button> </button>
</div> </div>
<div class="row" v-else-if="type === 'multiple'"> <div class="row" v-else-if="type === 'multiple'">