IT Project Assessments & Technical Project Reconstruction

Technical illustration for IT project assessment

Traceable examination of project histories, requirements, change states, technical decisions, delivery states and risks.

Technical reconstruction and assessment of IT projects

In disputed, delayed or poorly documented IT projects, the first task is to establish which technical and documented project state actually existed at a particular time. Requirements, tickets, specifications, repository history, builds, releases, tests, technical decisions, communications and change records can be correlated into a reviewable technical chronology. The objective is not retrospective project management, but a traceable technical reconstruction of findings, deviations, risks, alternative explanations and statement boundaries.

Typical questions

Methodological approach

The examination separates question, examination period, reference requirements, technical artefacts, finding, interpretation and professional assessment. Timestamps, tickets, documents, repositories, commits, tags, builds, test evidence and deployment records are correlated into a reviewable chronology where the evidence supports the attribution. Deviations are tested against plausible counter-hypotheses and alternative causes rather than inferred from temporal correlation alone.

Further technical knowledge: The article Reconstructing IT project history: tickets, repository history, emails and records explains how technical and organisational sources can be correlated into a traceable project chronology.

Examination chain From a project question to a traceable technical assessment
1 Reconstruct history Correlate tickets, repositories, communications, records and delivery states.
2 Compare requirements and actual state Relate documented requirements and acceptance criteria to the implemented system state.
3 Verify test and release evidence Examine builds, tests, releases and deployment evidence for the relevant project state.
4 Assess decisions and risks Document supported deviations, technical consequences, uncertainties and alternative explanations.
The process graphic links directly to the corresponding detailed examination methods in the English knowledge base.

Examination logic for project reconstruction

The iterative problem-solving cycle of diagnosis, objective definition, analysis and decision-making provides the overarching framework. In a project assessment it is applied to historical and technical evidence. New records may require the examination period, reference requirements, hypotheses or earlier interpretations to be revisited.

Project evidence chainFrom an alleged project problem to a bounded technical reconstruction
1Diagnosis & scopeDefine the project question, time period, participant and system boundaries and available sources.
2Requirements & criteriaReconstruct requirements, acceptance criteria, definition of done and relevant comparison states.
3ReconstructionCorrelate tickets, communications, Git, builds, releases, tests and deployments and test competing explanations.
4SynthesisState findings, deviations, technical risks, uncertainty and conclusions not supported by the evidence.

Keep multiple timelines separate

Project sources can carry different time references. Ticket time, author and committer dates, build time, release time, deployment time and the actually observed runtime state may differ. A supportable reconstruction records these levels separately and connects them only where technical or documentary evidence supports the attribution. Missing intermediate states or conflicting timestamps remain explicit uncertainties.

Assessment focus

Extended technical examination modules

Technical findings do not automatically answer contractual interpretation, breach, fault or damages. Those decisions remain with the responsible legal or commercial decision-makers.

Areas of application

Typical applications include technical project disputes, project cancellations, handovers and supplier changes, reconstruction of historical delivery states, technical classification of change requests and preparation of audits or technically informed decision processes. The examination scope is limited to technically reviewable questions and is expressly separated from legal, tax or commercial advice.

Assessment sequence Diagnosis, objectives, evidence analysis and expert synthesis
1 Diagnosis Establish project state, evidence sources, contradictions and technical hypotheses.
2 Objectives Define examination questions, reference criteria, relevant period and statement boundaries.
3 Evidence analysis Correlate documentary and technical evidence and test plausible alternative explanations.
4 Expert synthesis Separate findings, interpretation and professional assessment and document remaining uncertainty.

Example scope of an assessment

  • Review of project records, specifications, change logs and communications.
  • Technical assessment of implementation and architecture.
  • Reconstruction of repository, build, test, release and deployment evidence.
  • Report with findings, professional assessment, counter-hypotheses and statement boundaries.

Indicative fee guidance by scope:

  • Clearly delimited technical review or expert statement: approximately €1,500–€4,500 net
  • More extensive technical expert assessment: approximately €4,500–€10,000 net
  • Complex IT expert report with extensive technical examination: approximately €10,000–€20,000 net or more

The actual effort depends in particular on the technical question, project and system size, number and condition of the artefacts to be examined, quality of the available records, required examination depth and report documentation.

After an initial review of the question and the available material, an individual non-binding proposal can be prepared. Depending on the subject matter, a fixed price or another suitable fee arrangement may be agreed.

The amounts above are intended solely as initial guidance and do not constitute a binding offer. The actual effort may fall outside these ranges in an individual matter.

Author's technical literature and publications

The following works provide additional technical and methodological context. They do not replace required primary sources, standards, manufacturer documentation or other independent specialist sources. Unpublished manuscripts, drafts and teaching materials are deliberately not presented here as public sources.

Further technical knowledge

Constructed case study: IT project assessment

Reconstructing project history, requirements and technical evidence before assessing deviations.

Constructed examination scenario: This is a methodological example, not a real mandate, a real court appointment or a report of actual findings.

Diagnosis – reconstruct the project situation

Review schedules, requirements, change records, communications, repository states and technical deliveries. Separate technical, organisational and communication factors.

Objectives – define the examination frame

Specify whether the assessment concerns requirements implementation, acceptance criteria, project chronology, technical decisions, delivery states or another defined technical question.

Analysis – correlate documentary and technical evidence

Compare specifications, tickets, repositories, builds, tests and releases. Test alternative explanations for delays, integration failures or quality issues instead of inferring causality from chronology alone.

Expert synthesis – documented deviations and limits

Summarise what is technically supported, which deviations are documented and which uncertainties remain. Contract interpretation, breach, fault and damages remain outside the technical assessment.

Methodological inspiration: Nicolai Andler, Tools für Projektmanagement, Workshops und Consulting – Kompendium der wichtigsten Techniken und Methoden, 6th revised and expanded edition, Publicis, Erlangen, 2015, ISBN 978-3-89578-453-8. The examination sequence and expert synthesis used here are independently formulated for technical expert work.

Statement boundary: The examination addresses technical and methodological questions within the agreed subject of examination and evidence base. Legal advice, legal evaluation, commercial decisions and formal approval remain outside the technical expert mandate unless explicitly stated otherwise.

Initial technical classification of an enquiry

Before accepting an assignment, the technical question, subject of examination, available records, possible conflicts of interest and the required scope are reviewed. An individual non-binding proposal can then be prepared.

Contact Mathias Ellmann

Frequently Asked Questions about IT Project Assessments

What is an IT project assessment?

It reconstructs the technical and organisational course of an IT project in order to identify documented causes of delays, defects or conflicts.

When is an IT project assessment useful?

It can be useful after project delays, cancellation, disputes or quality problems when the project history needs to be reconstructed from evidence.

Which documents are typically relevant?

Requirements, project plans, code states, repositories, change records, test evidence, release records and relevant communications may be required.

How can the assessment be used?

It provides a technical evidence base for professional clarification and can prepare technical questions for out-of-court or court contexts.