DevOps is a software development methodology that congregates development and operational efforts required for software development. It is a collaborative process
resulting in increased speed and quality of software delivery. ServiceNow’s DevOps Change tracks the DevOps process (at the code level) end-to-end while DevOps Config is specific in managing and validating configuration data. Being closely related yet different products, the users constantly switch between the products during the development cycle. When software delivery fails, finding the root cause is a tiresome task in the current setup. This project evaluates the need for a unified experience for DevOps Change and DevOps Config to streamline the development cycle tracking and increase efficiency in resolving software delivery failure.
Carrying out desk research helped understand the process, products and set objectives for primary research. The interviews were conducted with product managers, product success managers and customers for an in-depth understanding of problems and the persona. Analyzing the primary and secondary research data resulted in four insight statements. The solutions were brainstormed for each insight using the How Might We approach. It resulted in sketching of multiple iterations of the screens in low fidelity. Based on the feedback on the low-fidelity designs, high-fidelity click through prototypes were created adhering to ServiceNow’s UI design guidelines. Testing the prototypes with solution experts, their overall feedback on the unified experience was positive, albeit with minor usability issues were rectified.
Observations from the usability test suggest that a functionally combined DevOps product simplifies tracking of the DevOps process and associated configuration data. The unified product not only streamlines the delivery failure correction but also prevents it in the first place.
