Can you build a city with JIRA?
Tech Crunch published a great article by John Evans that caught my eye.
The author uses the analogy of building a city from scratch to point out the problems with using JIRA (or any other ticket based system) for software projects. From the article:
“Use (JIRA) for tracking iterative development and bug fixes, by all means. It’s very good at that. But it is a tool deeply ill-suited to be the map of a project’s overall vision or infrastructure, and it is never the source of truth — the source of truth is always the running code. .”
I cannot agree more. That is why we created Panoptics in the first place. It is intended to help customers grasp the big picture from the runtime environment. The author goes on to suggest the remedy as follows:
“Allow me to propose something shocking and revolutionary: prose. Yes, that’s right; words in a row; thoughtfully written paragraphs. I’m not talking about huge requirements documents. I’m talking about maybe a ten-page overview describing the vision for the entire project in detail, and a six-page architectural document explaining the software infrastructure”
Once again spot on I think! At Crosscode, we love and use JIRA for issue tracking. However, our developers and architects write extensive architecture and design documents for every aspect of the product. The results have been pretty good so far I think. BTW, we put all those documents in Confluence 🙂