Software project management tool plug-in
In an example embodiment, an intelligent plug-in is provided for a software project management tool that facilitates automated capture and review of key performance indices (KPIs) in order to meet the quality needs of each workstream. This added automation, however, can be technically challenging due to a variety of factors, including the number of disparate systems from which KPIs need to be captured and the desirability of adding customized KPIs. The intelligent plug-in accesses a library of KPIs, but also enables a quality lead to define new KPIs and/or customize quality KPIs from the library. The quality lead is also then able to set thresholds for each KPI from within the plug-in. Upon movement of a user story within the software project management tool to a “development completed” or similar state, an automatic review of all defined KPIs for the corresponding user story are reviewed.
1 . A system comprising:
at least one hardware processor; and
a non-transitory computer-readable medium storing instructions that, when executed by the at least one hardware processor, cause the at least one hardware processor to perform operations comprising:
accessing, via a plugin integrated with a software project management tool, a first document, the first document including a description of a capability need for a feature of a software in development;
accessing, from a software library in the software project management tool, a plurality of key performance indices (KPI) tests linked to the first document, each KPI test including at least one argument and at least one variable, each argument having an associated threshold;
detecting, via automatic monitoring of a status field of the first document within the software project management tool, that a status field of the first document has been changed to indicate that development of the feature has been completed;
in response to the detecting, automatically evaluating each of the plurality of KPI tests by programmatically retrieving data from a plurality of disparate systems and comparing the evaluated KPI tests to corresponding thresholds;
based on the evaluating, categorizing, by the plugin, a quality level of the feature in one of a plurality of different quality categories; and
causing rendering of a user interface on a display, the user interface containing a screen corresponding to the first document and a visual indicator corresponding to the quality category in which the quality level of the feature has been categorized, wherein the user interface further comprises a selectable button that, when selected by a user, causes rendering of an indication of which of the plurality of KPI tests have passed and which have failed.
2 . The system of claim 1 , wherein the selectable button is rendered next to the visual indicator, and wherein the visual indicator is dynamically updated in real time based on results of the KPI tests.
3 . The system of claim 2 , wherein at least some of the plurality of KPI tests have been customized specifically for the first document.
4 . The system of claim 1 , wherein the user interface further includes a button rendered next to the visual indicator, the button, when selected by a user, causing rendering of a separate screen indicating which of the plurality of KPI tests have passed and which of the plurality of KPI tests have failed.
5 . The system of claim 1 , wherein at least one of the disparate systems is a bug and issue tracking component.
6 . The system of claim 1 , wherein at least one of the KPI tests is an indication of what percentage of source code corresponding to the feature is covered by at least one unit or integration test.
7 . A method comprising:
accessing, via a plugin integrated with a software project management tool, a first document, the first document including a description of a capability need for a feature of a software in development;
accessing, from a software library in the software project management tool, a plurality of key performance indices (KPI) tests linked to the first document, each KPI test including at least one argument and at least one variable, each argument having an associated threshold;
detecting, via automatic monitoring of a status field of the first document within the software project management tool, that a status field of the first document has been changed to indicate that development of the feature has been completed;
in response to the detecting, automatically evaluating each of the plurality of KPI tests by programmatically retrieving data from a plurality of disparate systems and comparing the evaluated KPI tests to corresponding thresholds;
based on the evaluating, categorizing, by the plugin, a quality level of the feature in one of a plurality of different quality categories; and
causing rendering of a user interface on a display, the user interface containing a screen corresponding to the first document and a visual indicator corresponding to the quality category in which the quality level of the feature has been categorized, wherein the user interface further comprises a selectable button that, when selected by a user, causes rendering of an indication of which of the plurality of KPI tests have passed and which have failed.
8 . The method of claim 7 , wherein the selectable button is rendered next to the visual indicator, and wherein the visual indicator is dynamically updated in real time based on results of the KPI tests.
9 . The method of claim 8 , wherein at least some of the plurality of KPI tests have been customized specifically for the first document.
10 . The method of claim 7 , wherein the user interface further includes a button rendered next to the visual indicator, the button, when selected by a user, causing rendering of a separate screen indicating which of the plurality of KPI tests have passed and which of the plurality of KPI tests have failed.
11 . The method of claim 7 , wherein at least one of the disparate systems is a bug and issue tracking component.
12 . The method of claim 7 , wherein at least one of the KPI tests is an indication of what percentage of source code corresponding to the feature is covered by at least one unit or integration test.
13 . A non-transitory machine-readable medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform operations comprising:
accessing, via a plugin integrated with a software project management tool, a first document, the first document including a description of a capability need for a feature of a software in development;
accessing, from a software library in the software project management tool, a plurality of key performance indices (KPI) tests linked to the first document, each KPI test including at least one argument and at least one variable, each argument having an associated threshold;
detecting, via automatic monitoring of a status field of the first document within the software project management tool, that a status field of the first document has been changed to indicate that development of the feature has been completed;
in response to the detecting, automatically evaluating each of the plurality of KPI tests by programmatically retrieving data from a plurality of disparate systems and comparing the evaluated KPI tests to corresponding thresholds;
based on the evaluating, categorizing, by the plugin, a quality level of the feature in one of a plurality of different quality categories; and
causing rendering of a user interface on a display, the user interface containing a screen corresponding to the first document and a visual indicator corresponding to the quality category in which the quality level of the feature has been categorized, wherein the user interface further comprises a selectable button that, when selected by a user, causes rendering of an indication of which of the plurality of KPI tests have passed and which have failed.
14 . The non-transitory machine-readable medium of claim 13 , wherein the selectable button is rendered next to the visual indicator, and wherein the visual indicator is dynamically updated in real time based on results of the KPI tests.
15 . The non-transitory machine-readable medium of claim 14 , wherein at least some of the plurality of KPI tests have been customized specifically for the first document.
16 . The non-transitory machine-readable medium of claim 13 , wherein the user interface further includes a button rendered next to the visual indicator, the button, when selected by a user, causing rendering of a separate screen indicating which of the plurality of KPI tests have passed and which of the plurality of KPI tests have failed.
17 . The non-transitory machine-readable medium of claim 13 , wherein at least one of the disparate systems is a bug and issue tracking component.