Project forensics & IT mediation
What the Jira tickets of a failed project tell you
When a software project ends up in mediation, you learn quickly what really kills delivery. It is never the programming language.
By Christian Liebich · · 2 min read · Executive Briefing
I have been brought into mediation proceedings as a technical advisor, to estimate and evaluate the open Jira tasks of a failed software project. When an IT project breaks down so badly that it ends up in mediation, you learn very quickly what actually kills software delivery.
It is never the programming language. And it is almost never a lack of technical skill.
The same story in every disputed ticket
- Requirements were written to protect the author, not to explain the business problem.
- Developers built strictly to the ticket instead of solving the problem, because trust had already collapsed.
- Jira was used to monitor people rather than to communicate with them.
The early warning signs
At the federal IT office (FOITT) I walked into a project that showed the same early signs: a team of senior developers in constant conflict with each other, with their superiors and with their stakeholders.
I did not start by rewriting the sprint board. I started by earning respect in the code, taking a seat in the stakeholder committees to absorb the pressure, and matching the tasks to the actual strengths of each engineer.
Nine months later I was promoted to lead that unit: nine people, four production microservices, four web projects in lifecycle and over CHF 4 million in annual development volume.
Before the lawyers do it
If your team and your stakeholders are communicating through passive-aggressive Jira comments, you do not need a better agile coach. You need someone who steps in and rebuilds the bridge before the lawyers have to.
