Details

      Description

      As an operation manager, I want to see my process throughput (velocity) results, so that I can learn what is my actual velocity in a given timeframe (1 month, 1 week, 1 day, etc).

      Context

      Performance Metrics
      One of the main reasons to have and keep tracking reports for a workflow process is to evaluate what are the current problems of your actual process and find ways to solve and optimize it. That being said, we decided to create the "Performance Metrics" to allow our customers to be able to identify those problems (e.g. bottlenecks, delays, etc.) and give all de details necessary to help they understand and tune their processes within Liferay.

      In this MVP, we focus to give performance metrics over the following dimensions:

      • Overall process performance (velocity/throughput)
      • Assignee performance (Assignee's velocity/average completion time, load)
      • Steps performance (Average completion time, SLA breaches)

      This Feature: Velocity/Throughput Metrics
      This metric is particularly helpful to help managers to understand what amount of processing they can achieve with the current process, number of people and level of automation. Also, it's a very good parameter to be used to evaluate if the process' performance is getting better or worse over time.

      Acceptance Criteria

      • Given that a user accessed the Metrics of a workflow process, when the user accesses the Performance tab of the report, then the user should be able to identify the current velocity/throughput of the chosen process in the "last 30 days" as the default timeframe and "inst/day" as the default velocity unit;
      • Given that users are seeing the performance report of a process, when they start analyzing the velocity metrics of the process, then they should be able to choose and understand the velocity of the process in different timeframes;
      • Given that users are seeing the performance report of a process, when they start analyzing the velocity metrics of the process, then they should be able to choose the best unit of velocity (Instances per day, Instances per week, Instances per month, etc.) for the analysis;
      • Given users that doesn't have previous experience or training in Liferay workflow metrics, when they see the velocity metrics of the report, then the system should be able to provide them with a short tip/explanation about the velocity metrics.
      • The label for the timeframe dropdown option Yesterday should read as "<dd MM>, 12 AM - <dd MM>, 11:59 PM";
      • The process throughput result might reflect the user choice related to time range and velocity unit filters;
        • Depending on the selected time frame option, the velocity unit options will update accordingly.
        • For each time frame option, there will be a default velocity unit option, and users can select other options if available, as described bellow

      Time period rules

      • Yesterday: from 00:00 to 23:59 of the previous day;
        • Default velocity unit: instances per hour;
      • Today: from 00:00 to the next nearest hour of the current day;
        • Default velocity unit: instances per hour;
      • Last 7 days: from 6 days ago to today;
        • Default velocity unit: instances per day;
      • Last 30 days: from 29 days ago to today;
        • Default velocity unit: instances per day;
        • Others velocity unit: instances per week;
      • Last 90 days: from 89 days to today,
        • Default velocity unit: instances per week;
        • Others velocity unit: instances per day and instances per month;
      • Last 180 days: from 179 days ago to today
        • Default velocity unit: instances per month;
        • Others velocity unit: instances per week;
      • Last Year: from 364 or 365 days to today,
        • Default velocity unit: instances per month.
        • Others velocity unit: instances per week;

      Definitions of Done

      • Related tests created and passed successfully;
      • All Acceptance Criteria were passed;
      • Make sure that all system documentation were updated (if necessary);
      • Validated by QA, Product Designer and/or PM;
      • No critical issue related to Story scope (ex.: similar of a FP4, FP5 bug);
      • Code with peer review completed.

      Design Deliverables

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dennys.barros Dennys Barros (Inactive)
              Reporter:
              nathalia.moura Nathália Moura (Inactive)
              Engineering Assignee:
              Nathália Moura (Inactive)
              Recent user:
              Rodrigo Cunha
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.2.10 DXP FP2
                  7.2.10.1 DXP SP1
                  Master