Explanation
      Back to home
      1. Uplevel Help Center
      2. Explanation

      Time Allocation / Available Dev Time

      How does Uplevel calculate Time Allocation for my teams?

      Time Allocation is a specific Uplevel insight that provides an automated, up-to-date breakdown of where your organization’s time and efforts are spent. As a pivotal lens for engineering organizations today, Uplevel’s Time Allocation empowers engineering leadership with the right visibility to proactively align efforts to strategic business priorities and systematically inform tax capitalization reporting, all while saving your teams from manual, heavy lifting on a regular basis to try to compile this on their own.

      Learn more about Uplevel's Time Allocation and the ways we work with your varying team processes here.

      Uplevel’s Time Allocation has been rigorously evaluated and audited for the purposes of tax capitalization reporting, and has passed each test due to the way in which Uplevel overlays metadata from each data source:

      1. Uplevel references each developer’s calendar to discern time spent in Meetings and Out-of-Office vs. available time on the calendar. 
      2. Uplevel then intelligently captures the amount of Chat Interruptions each developer has for each day. 
      3. Uplevel measures Available Dev Time with the remaining time outside of Meetings/Out-of-Office/Interruptions.
      4. With the Available Dev Time, Uplevel then aggregates all the activity from Jira, Git, and Incident Management to identify engineering time and efforts spent on various Epics, Projects, Issue Types and more. 
      5. No process change or additional work is required of your teams in order to capture Time Allocation. However, Uplevel can also custom build Time Allocation based on existing Jira data to map to how your teams organize their work. Examples of custom aggregations include using custom Jira fields, parent link mappings, or even a custom rule (e.g. Project 47 + Bug Issue Types = KTLO). 
        1. For example, Uplevel maps all of our engineering work using a hierarchy in Jira. "Initiative" represents larger bodies of work and is captured via a required field on Jira Epics. We plan our initiatives on a quarterly basis and are then able to track alignment to the plans ongoing throughout a quarter with Time Allocation. 
        2. Other examples of custom Jira fields from Uplevel customers are “Work Type”, “Work/Task Classification”, “Eng. Category” and “Workstream”. 
        3. If these practices don’t exist today, Uplevel has many best practices to help you operationalize a new custom Jira field. Many Uplevel customers have implemented this as a new process, which Uplevel can help expedite by surfacing the work not linked or tagged according to the standard being used.
      6. Beyond simply looking at PR activity at the repo level, Uplevel intelligently links PRs to the respective Jira work to provide an enhanced view of where time is spent. 
      7. If Uplevel doesn’t see any signals from Jira, Git, or Incident Management activity on a given day, Uplevel will sequentially look at the previous 6 days to see what Jira issues, PRs, and Incidents may still be open or being worked on. Activity is distributed across work items using story points.
      8. If Uplevel sees no open Jira issue assigned to an individual on a given day (that is actively being worked on: with activity in the last 7 days) or linked GitHub activity in the last 14 days, then Uplevel categorizes that Available Dev Time as Other efforts (aka. No Issue or PR activity), as Uplevel estimates that the developer is working in tools not captured by Uplevel on that day (e.g. documentation, Miro, etc.)
        1. Example: Lisa is a developer and Uplevel sees no Jira, Git, or Incident Management activity for Tuesday. However, Uplevel sees that Lisa has an open Jira ticket with an associated PR authored on Monday and the PR is still open on Tuesday. Uplevel estimates that Lisa is still working on that PR/Ticket
      9. Out-of-Office is based on the meeting classifier, and is triggered by meeting titles such as OOO/away/travel/appointment/school drop off/etc. This is used to capture brief absences such as being unavailable for an hour for an appointment, and also longer vacations that are marked on the calendar. It also automatically treats that US business holidays are Out-of-Office since these are often not explicitly marked on the calendar.

      Jira Hierarchies (1) (1)

      Learn more

      What is an Allocation Scheme? 

      A comparison of time allocation units

      Estimated Allocation Costs