In a distressed MtO project, the feature burndown shows whether the team is closing scope gaps (link). But there is a second dimension that the burndown does not capture: product quality. Features can be declared “done” while carrying unresolved defects that compound across releases and eventually lead to ugly customer escalations—or worse: field failures. That can result in shipping broken products—not because the team hasn’t worked hard on developing new features, but because product quality hasn’t been managed early on. Read…

Made-to-Order (MtO) projects are fundamentally different from R&D. A customer defines the requirements. The scope is contractually fixed. The lifecycle follows a V-model (at least in regulatory-relevant projects) with formal verification at every level of Read…