put everything in mind in the article body
This commit is contained in:
@@ -4,13 +4,21 @@
|
||||
<div class="flow-hypothesis">
|
||||
<p>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>
|
||||
|
||||
@@ -11,8 +11,9 @@
|
||||
</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.
|
||||
spread out rapidly. So we rush, as fast as we can, and we produce as many
|
||||
features as we can. And if a team has nothing to do, it becomes a disaster
|
||||
as it is money lost.
|
||||
</p>
|
||||
</div>
|
||||
</template>
|
||||
|
||||
@@ -11,7 +11,7 @@ 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
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user