KronoDesk as solid KnowledgeBase
Rating: 10 out of 10
IncentivizedUse Cases and Deployment Scope
It is used as a general communication and issue tracking tool, so that nothing intended to be changed gets lost and is a very practical knowledge base.
The integration with Spira-tools is a welcome and practical to track incidents and test information, which are the basis of many of the issues, tracked in KronoDesk.
Pros
- As a system architect I have a clear overview of open issues through clear issue description and assignment to developers.
- The overview and tracking are most important to me.
Cons
- The possibility to create a system/subsystem/component/interface tree of the system landscape, to be used to more detailed issue associations and subsequent detailed planning and monitoring of issues.
- A quick issue entry with the most important information would be helpful.
- A "live" report that can contains my current "hot" issues would be helpful.
Likelihood to Recommend
I advise my customers to use it for all issue tracking, in business development as well as in business operations. An interface to operational systems is therefor very helpful and enlarges the value of the KronoDesk knowledge base, provided that this information is "open" to all users of all departments.