From the course: Learning Jira: Leveraging Sprints, Releasing Features, Fixing Bugs, and Tracking Development
Unlock this course with a free trial
Join today to access over 24,900 courses taught by industry experts.
Estimating work and tracking time - Jira Tutorial
From the course: Learning Jira: Leveraging Sprints, Releasing Features, Fixing Bugs, and Tracking Development
Estimating work and tracking time
- [Instructor] Estimation helps predict and plan work, set expectations, and communicate scope. There are two ways to estimate work. In this section, we'll discuss the differences between time and story point estimates. As a reminder from the Learning Jira course, time estimates are entered in minutes, hours, days, or weeks. In the example, 2,400 minutes is the same as 40 hours, five days, or one work week. Time is specified using m for minutes, h for hours, m for days, and w for weeks. Multiple time units can also be combined, like one day and one hour in the example. Finally, you can also enter time in decimal format. If 2.5 days are entered, it will be converted to read 2d 4h. Any type of team can use this method. It's possible that the time format in your application looks slightly different. The format is configurable at the application level. Also, by default, JIRA assumes that there are eight work hours per day…
Contents
-
-
-
(Locked)
Software project types12m 3s
-
(Locked)
Common work types18m 9s
-
(Locked)
Using software workflows9m 58s
-
(Locked)
Leveraging backlogs and sprints7m 37s
-
(Locked)
Estimating work and tracking time13m 53s
-
(Locked)
Using fix versions10m 22s
-
(Locked)
Types of boards8m 12s
-
(Locked)
Types of reports9m 6s
-
(Locked)
Common integrations5m 31s
-
(Locked)
-
-
-
-
-