Merge branch 'main' of github.com:jcalixte/tps into main

This commit is contained in:
Julien Calixte
2023-07-31 22:58:33 +02:00
13 changed files with 128 additions and 55 deletions

View File

@@ -4,13 +4,21 @@
<div class="flow-hypothesis">
<p>Here our hypothesis:</p>
<ol>
<li>it takes the same amount of time for each team to complete a task</li>
<li>
it takes the same amount of time for each team to complete a task
<span class="meaning">same task time</span>
</li>
<li>teams have no other external dependencies</li>
<li>
teams know exactly what they need to produce their part, they will tag
any defects they found when verifying the feature is good.
</li>
<li>the team where the defect appears must rework the feature.</li>
<li>
0 defect policy: the team where the defect appears must rework the
feature.
</li>
<li>release team never fails</li>
<li>there is no limit on how many defects a feature can have.</li>
</ol>
</div>
</template>

View File

@@ -4,13 +4,14 @@ import PullSystemIcon from '@/icons/PullSystemIcon.vue'
import PushSystemIcon from '@/icons/PushSystemIcon.vue'
import FeatureItem from '@/modules/feature/FeatureItem.vue'
import FlowControls from '@/modules/feature/FlowControls.vue'
import QualityIssue from '@/modules/feature/QualityIssue.vue'
import { Feature } from '@/modules/feature/feature'
const feature: Feature = {
name: 'As a user, in the homepage, I can login',
complexity: 3,
leadTime: 2,
qualityIssue: 2,
qualityIssue: 4,
status: 'doing',
step: 2
}
@@ -36,8 +37,8 @@ const feature: Feature = {
number and deliver as fast as possible.
</p>
<p>
<span class="numeric">{{ feature.qualityIssue }}</span> are the number of
defects the feature had during the flow.
<QualityIssue class="inline" :quality-issue="feature.qualityIssue" />
are the number of defects the feature had during the flow.
</p>
<p>
You have 20 features to deliver, and each day you can choose between 3
@@ -85,15 +86,22 @@ const feature: Feature = {
understand and limit rework. The more the team investigate, the more the
team learn and start to be extremely good at problem solving.
</p>
<h3>Blue bin: the security stocks</h3>
<h3>Blue bin: the security stock</h3>
<p>
Blue bins are your security stock, to make sure teams can work without any
blockers. It's to make sure the next team will always have material to
transform. But it comes with a cost: overburden, stagnation (increase lead
time) and duplicated mistakes (not simulated here). The less you have, the
time) and duplicated mistakes
<span class="meaning">not simulated here</span>. The less you have, the
less your team has mental charge. The more you have, the more secure you
are to make teams work. One solution: simplify your flow and lower the
number of operation the teams have to do to deliver a feature.
</p>
</div>
</template>
<style scoped>
.inline {
display: inline;
}
</style>