article: improve and humanise
This commit is contained in:
@@ -165,8 +165,8 @@ const displaySimulationConclusion = computed(() => {
|
|||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
To implement this, we introduce "blue bins" as safety stock. These bins
|
To implement this, we introduce "blue bins" as safety stock. These bins
|
||||||
ensure teams always have work ready to process without delays. For our
|
ensure teams always have work ready to process without delays but we
|
||||||
simulation, each team has two blue bins, which provides a good balance.
|
stop whenever blue bins are full.
|
||||||
</p>
|
</p>
|
||||||
<!-- [dps]
|
<!-- [dps]
|
||||||
<h3>Problem solving: no production, just reflection</h3>
|
<h3>Problem solving: no production, just reflection</h3>
|
||||||
@@ -182,8 +182,8 @@ const displaySimulationConclusion = computed(() => {
|
|||||||
<FeatureSteps alias="playground" />
|
<FeatureSteps alias="playground" />
|
||||||
<div class="manual-simulation text">
|
<div class="manual-simulation text">
|
||||||
<p>
|
<p>
|
||||||
What insights can we gain from these strategies? Here are some
|
Well, what do you think? Not so simple... What are the insights from
|
||||||
observations:
|
these strategies? Here are some observations:
|
||||||
</p>
|
</p>
|
||||||
<ol>
|
<ol>
|
||||||
<li>
|
<li>
|
||||||
@@ -206,7 +206,7 @@ const displaySimulationConclusion = computed(() => {
|
|||||||
system.
|
system.
|
||||||
</p>
|
</p>
|
||||||
</div>
|
</div>
|
||||||
<SimulationControls type="single" class="above" />
|
<SimulationControls type="single" />
|
||||||
<SimulationDashboard />
|
<SimulationDashboard />
|
||||||
<div class="text">
|
<div class="text">
|
||||||
<p>
|
<p>
|
||||||
@@ -216,12 +216,11 @@ const displaySimulationConclusion = computed(() => {
|
|||||||
focus on a small number of feature helping them having less overburden.
|
focus on a small number of feature helping them having less overburden.
|
||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
Now, what happens when we have a lot of projects to deliver? Are
|
Do you mind comparing more projects? What happens when we simulate 1000
|
||||||
patterns the same? Let's simulate... 1000 news mobile app! 500 for each
|
news mobile app! Are patterns the same?
|
||||||
system and see what are the trends.
|
|
||||||
</p>
|
</p>
|
||||||
</div>
|
</div>
|
||||||
<SimulationControls type="multiple" class="above" />
|
<SimulationControls type="multiple" />
|
||||||
<div class="flow-multiple-simulation text">
|
<div class="flow-multiple-simulation text">
|
||||||
<p v-if="displaySimulationConclusion">
|
<p v-if="displaySimulationConclusion">
|
||||||
Now we’re pretty confident! As quality issues increase in the
|
Now we’re pretty confident! As quality issues increase in the
|
||||||
@@ -234,25 +233,22 @@ const displaySimulationConclusion = computed(() => {
|
|||||||
<p v-else>
|
<p v-else>
|
||||||
Waiting for at least {{ SIMULATION_THRESHOLD }} simulations...
|
Waiting for at least {{ SIMULATION_THRESHOLD }} simulations...
|
||||||
</p>
|
</p>
|
||||||
<p>
|
|
||||||
Teams often underestimate the complexity of a project and the challenges
|
|
||||||
of collaborating with others. Unfortunately, this is something I’ve
|
|
||||||
observed in many software projects.
|
|
||||||
</p>
|
|
||||||
<!-- [dps]
|
<!-- [dps]
|
||||||
<p>
|
<p>
|
||||||
Note that problem solving is always a good practice. The capacity of the
|
Note that problem solving is always a good practice. The capacity of the
|
||||||
team to stop and think about how they work is critical.
|
team to stop and think about how they work is critical.
|
||||||
</p> -->
|
</p> -->
|
||||||
<p>
|
<p>
|
||||||
If a project isn’t progressing well, the response is often to "try
|
Teams often underestimate the complexity of a project and the challenges
|
||||||
harder"—just once. However, "Just in time" frequently turns into "Just
|
of collaborating with others. Unfortunately, this is something I’ve
|
||||||
this time" over and over. This approach causes teams to overproduce,
|
observed in many software projects. If a software isn’t progressing
|
||||||
creating unnecessary stock and latent defects that require rework. The
|
well, the response is often to "try harder"—just once. However, "Just in
|
||||||
more the project struggles, the more siloed teams become, leading to
|
time" frequently turns into "Just this time" over and over. This
|
||||||
blame-shifting: "I did my part; if the project fails, it’s not my
|
approach causes teams to overproduce, creating unnecessary stock and
|
||||||
fault." The reality is, it’s not anyone’s fault—it’s the system that’s
|
latent defects that require rework. The more the project struggles, the
|
||||||
broken.
|
more siloed teams become, leading to blame-shifting: "I did my part; if
|
||||||
|
the project fails, it’s not my fault." The reality is, it’s not anyone’s
|
||||||
|
fault—it’s the system that’s broken.
|
||||||
</p>
|
</p>
|
||||||
<!-- [dps]
|
<!-- [dps]
|
||||||
<p>
|
<p>
|
||||||
|
|||||||
Reference in New Issue
Block a user