Introduction
The idea of having the two backlogs can still be pretty new to many people, so I will first try to explain in this posts the philosophy behind the usage of different backlogs and present the integration of different management systems. The Operations backlog or Ops backlog is usually a backlog for management of business and end users, where incidents, problems, tickets and service requests are being recorded. By monitoring and event management events are dispatched back to the Development backlog or Dev Backlog, where the main goal of the team is to deliver constant structural enhancements, to improve the satisfaction and to prevent and incidents affecting the high quality of performance and functionality for the end user.
In order to ensure a smooth connection between different backlogs, there are some good solutions on the market for incident management, such as Service Now, Remedy, Trello, ZenDesk, User Voice and much more. To get more insights from real examples, in many of my projects the development, which is using Dev Backlog was made in Visual Studio and integrated with Ops Backlogs, using different incident management apps mentioned above. The idea is well captured in the image below: https://goo.gl/iURK1n #DataIntegration #ML
