- Pushing all the feature as fast as possible, we make the assumption that - we can deliver in (# step × # features = 150 days) if everything goes - well. The fastest a team can do. We overburden the teams but it's for the - good cause. We already payed everybody to work so if there is someone who - has nothing to do, this is just money down the drain. + Pushing all the feature as fast as possible, this is the only strategy + that allows us to target the best possible result: `# step × # status × # + features`. We may overburden teams in the process though. But as we + already invest money everybody to work so if there is someone who has + nothing to do, this is just money down the drain.
-- We know that we will never reach the best score ever: the push system - where everything goes right. But we limit overburden. We know we prefer + It comes from the assumptions that we will never reach the best score ever + aka "the push system where everything goes right". We know we prefer waiting for next team to be ready before doing some extra work than having stock of feature pre-baked.
diff --git a/src/modules/feature/feature-board.ts b/src/modules/feature/feature-board.ts index 35e55df..d089230 100644 --- a/src/modules/feature/feature-board.ts +++ b/src/modules/feature/feature-board.ts @@ -241,7 +241,7 @@ export const nextDay = ( ): FeatureState => { state.meta.totalDays++ // each day, the teams know how to better work together - state.meta.teamWorkExperience += 0.01 + state.meta.teamWorkExperience += 0.1 if (strategy === 'problem-solving') { const hasTeamLearned = randomFloat(0, 1) > 0.25