A Six-Month Deadline Is Not a Development Plan

Why technical milestones must follow

dependencies, evidence and risk

COMMENTARY

By Ntokozo Mthembu, PhD, Pr Eng

Johannesburg, South Africa

Abstract

Technology-development projects are often planned around contractual dates rather than technical dependencies. This article argues that a six-month funding window is a constraint, not a development plan. Drawing on anonymised professional experience and public systems-engineering guidance, it distinguishes calendar milestones from evidence-bearing technical gates. It proposes a five-stage chain: freeze the baseline; release the design; prove build readiness; build, integrate and learn; and verify and hand over. Each stage should specify deliverables, acceptance criteria, accountable reviewers and retained evidence. The article explains why uncertainty and iteration are inherent in experimental development, what a time-constrained project can honestly claim, and how innovators and funders should respond when the programme window and engineering reality diverge. It concludes that public or risk capital should be governed by the reduction of material uncertainty—not merely elapsed time or the percentage of budget spent.

Keywords: technology development; project scheduling; technical gates; verification; innovation funding; prototype

Six months sounds precise. It fits neatly into a funding agreement, a steering-committee calendar and a row in a project plan. Yet “complete the prototype in six months” is not a development plan. It is a date attached to an outcome whose technical meaning may still be unresolved.

This distinction matters in industrial innovation, where the work is not merely to execute a known recipe. The team may still have to stabilise requirements, resolve interfaces, translate a concept into controlled design information, test manufacturing assumptions, learn from a trial build and verify performance. Compressing the calendar does not remove those dependencies. It can only change the scope, resources, risk exposure or confidence of the result.

A fixed window can nevertheless be useful. It forces prioritisation and can prevent an exploratory project from becoming indefinite. The discipline lies in defining a feasible end-state for that window and constructing a traceable route to it. The six-month target should therefore be treated as a boundary condition—not as the logic of the engineering programme.

This article draws on anonymised professional experience with a time-constrained South African technology-development project. No project identity, proprietary design, commercial terms or controlled documentation is disclosed. The purpose is to extract a general planning lesson for innovators, funders, technical reviewers and programme managers.

More…

To read entire article, click here

How to cite this article: Mthembu, N. (2026).  A Six-Month Deadline Is Not a Development Plan: Why technical milestones must follow dependencies, evidence and risk, commentary, PM World Journal, Vol. XV, Issue XI, November.  Available online at https://pmworldjournal.com/wp-content/uploads/2026/11/pmwj170-Nov2026-Mthembu-Six-Month-Deadline-Is-Not-a-Development-Plan.pdf

About the Author

Dr. Ntokozo Mthembu

South Africa

Dr. Ntokozo Mthembu, PhD, Pr Eng, is an independent engineering, technology and innovation consultant based in Johannesburg, South Africa. A former specialist in the Support Programme for Industrial Innovation at the Industrial Development Corporation, he has more than 28 years’ experience in engineering, manufacturing, innovation funding, commercialisation, technical due diligence and strategic evaluation. His work focuses on technical assessment, technology commercialisation and evidence-based evaluation frameworks for industrial and digital innovation. He writes in his personal capacity. He can be contacted at nsdpmthembu@gmail.com