complete the article

src/modules/article/FlowConclusion.vue

@@ -0,0 +1,24 @@
+<template>
+  <div class="flow-conclusion">
+    <p>
+      When money and pressure are in the game, fear, uncertainty, and doubt
+      spread out rapidly. So we rush, as fast as we can, and when a team has
+      nothing to do, it becomes a disaster: money are being burned.
+    </p>
+    <p>
+      Teams will overproduce. They will do every pieces they can as they are
+      autonomous: product team will pitch their features, designers will design
+      every pages, developers will rush to code forgetting why the customer
+      needs this precise feature. They will then struggle to get these pieces to
+      the very end when they will transfer them to the others teams.
+      Multitasking will drastically drop the productivity. So the fear of having
+      nothing to give to the next team pushes us to produce just in case. Bugs
+      lead to more bugs that lead to more bugs.
+    </p>
+    <p>
+      But the best way to succeed is to ask: "Is this what you need? How can I
+      help you?". Just like in Ekiden, handovers are where the real struggles
+      happen but we're on the same race, together.
+    </p>
+  </div>
+</template>

src/modules/article/FlowHypothesis.vue

@@ -2,7 +2,7 @@
 
 <template>
   <div class="flow-hypothesis">
-    <p>Hypothesis:</p>
+    <p>Here our hypothesis:</p>
     <ol>
       <li>it takes the same amount of time for each team to complete a task</li>
       <li>

src/modules/article/FlowIntro.vue

@@ -1,18 +1,12 @@
 <template>
   <div class="flow-intro">
     <p>
-      This article is here to plan ahead ourselves to what can be misconceptions
-      on how to be effective. Teams will overproduce. They will do everything
-      piece they can as they are autonomous. They will then struggle to get
-      these pieces to the very end when they will transfer them to the others
-      teams. Multitasking will drastically drop the productivity. So the fear of
-      having nothing to give to the next team pushes us to produce just in case.
-      Bugs lead to more bugs that lead to more bugs.
-    </p>
-    <p>
-      When money and pressure are in the game, fear, uncertainty, and doubt
-      spread out rapidly. So we rush, as fast as we can, and if a team has
-      nothing to do, it becomes a disaster.
+      How good are we to succeed a project? Delivering the features at the good
+      quality and at the right time. We're pretty bad at it and there is a lot
+      of misconceptions on how to manage people to do what need to be done. I
+      wanted to create a simulation to plan ahead and see what are the
+      consequences of different strategy patterns and which is the most
+      effective.
     </p>
   </div>
 </template>

src/modules/article/FlowMultipleSimulation.vue

@@ -0,0 +1,17 @@
+<template>
+  <div class="flow-conclusion">
+    <p>Teams tend to underestimate how long a project will be.</p>
+    <p>
+      If we're not in a good pace, we just have to try harder. Only once. "Just
+      in time" becomes "Just this time". So teams overproduce. Creating stock
+      and latent defects the teams need to rework. The worse the project do, the
+      more silot we become and we tend to argue with a "I've done my job, if the
+      project fails it's not my fault.". The fact is that it's nobody's fault,
+      it's a system.
+    </p>
+    <p>
+      Short term objectives become the norm. It is never the right time to do
+      problem solving. To think on how we think.
+    </p>
+  </div>
+</template>

src/modules/article/FlowSingleSimulation.vue

@@ -0,0 +1,10 @@
+<template>
+  <div class="flow-conclusion">
+    <p>Pull systems win by a lot! Why is that?</p>
+    <p>
+      But it was only one simulation, maybe it can be different. To be sure,
+      let's generate 200 projects delivering 200 features each! And see what
+      happens...
+    </p>
+  </div>
+</template>