modal-121 / 10 - Task Management in JIRA Create & Assign Task Task Workflow /004 Estimation & Actual hours for task_en.srt
| 1 | |
| 00:00:00,000 --> 00:00:02,000 | |
| Welcome to the testing work. | |
| 2 | |
| 00:00:03,000 --> 00:00:11,000 | |
| Previously we have seen how we can create task and what is task workflow priority task end to end workflow. | |
| 3 | |
| 00:00:13,000 --> 00:00:20,000 | |
| Now I'll show you original estimation and actual time estimation means when we're creating a task, | |
| 4 | |
| 00:00:21,000 --> 00:00:24,000 | |
| we are doing the estimation like it will be completed in two days. | |
| 5 | |
| 00:00:25,000 --> 00:00:32,000 | |
| And when actually somebody is working on this, he or she will enter the time, how many hours or I'll | |
| 6 | |
| 00:00:32,000 --> 00:00:36,000 | |
| see how many days spent on a particular task. | |
| 7 | |
| 00:00:37,000 --> 00:00:41,000 | |
| So I'll show you how we can put estimation time and actual time. | |
| 8 | |
| 00:00:42,000 --> 00:00:42,000 | |
| Okay. | |
| 9 | |
| 00:00:43,000 --> 00:00:45,000 | |
| I'm taking example as a lead. | |
| 10 | |
| 00:00:45,000 --> 00:00:48,000 | |
| I'm going to create a task and assign it to my tester. | |
| 11 | |
| 00:00:48,000 --> 00:00:54,000 | |
| So I'll just go here and going to my dashboard first. | |
| 12 | |
| 00:00:54,000 --> 00:00:56,000 | |
| Okay, I take an example. | |
| 13 | |
| 00:00:56,000 --> 00:00:57,000 | |
| I'm working here as a lead. | |
| 14 | |
| 00:00:57,000 --> 00:01:00,000 | |
| I want to assign a task to my tester. | |
| 15 | |
| 00:01:00,000 --> 00:01:05,000 | |
| So this create a task and there's a project. | |
| 16 | |
| 00:01:05,000 --> 00:01:07,000 | |
| I'm going to create a task here. | |
| 17 | |
| 00:01:08,000 --> 00:01:08,000 | |
| Okay. | |
| 18 | |
| 00:01:08,000 --> 00:01:10,000 | |
| What is this, somebody? | |
| 19 | |
| 00:01:10,000 --> 00:01:12,000 | |
| So I'm saying it's a testing task. | |
| 20 | |
| 00:01:14,000 --> 00:01:23,000 | |
| And execute test cases off registration module. | |
| 21 | |
| 00:01:23,000 --> 00:01:25,000 | |
| Or in other words, you can write. | |
| 22 | |
| 00:01:28,000 --> 00:01:30,000 | |
| Registration module testing. | |
| 23 | |
| 00:01:33,000 --> 00:01:36,000 | |
| Mature testing and okay. | |
| 24 | |
| 00:01:36,000 --> 00:01:37,000 | |
| Which components belong to? | |
| 25 | |
| 00:01:37,000 --> 00:01:39,000 | |
| That's my registration. | |
| 26 | |
| 00:01:39,000 --> 00:01:42,000 | |
| You can attach it to this case of this module. | |
| 27 | |
| 00:01:42,000 --> 00:01:44,000 | |
| So just go here, upload. | |
| 28 | |
| 00:01:45,000 --> 00:01:52,000 | |
| And if you remember previously I have shown you that was the disk, so I just uploaded here. | |
| 29 | |
| 00:01:52,000 --> 00:01:53,000 | |
| Okay. | |
| 30 | |
| 00:01:53,000 --> 00:01:55,000 | |
| Now, in description, we need to write. | |
| 31 | |
| 00:01:55,000 --> 00:01:56,000 | |
| What exactly? | |
| 32 | |
| 00:01:57,000 --> 00:02:02,000 | |
| My test to have to do something first. | |
| 33 | |
| 00:02:03,000 --> 00:02:19,000 | |
| Execute all test cases, report all books, which you'll find while doing testing. | |
| 34 | |
| 00:02:22,000 --> 00:02:25,000 | |
| Retesting of all. | |
| 35 | |
| 00:02:27,000 --> 00:02:29,000 | |
| Fixed issues. | |
| 36 | |
| 00:02:31,000 --> 00:02:32,000 | |
| Issues. | |
| 37 | |
| 00:02:33,000 --> 00:02:34,000 | |
| So these are the tasks we need to perform. | |
| 38 | |
| 00:02:35,000 --> 00:02:36,000 | |
| Acceptance criteria is that. | |
| 39 | |
| 00:02:41,000 --> 00:02:42,000 | |
| Criteria. | |
| 40 | |
| 00:02:45,000 --> 00:02:56,000 | |
| All test gifts executed all bugs, reported Butera. | |
| 41 | |
| 00:02:58,000 --> 00:03:01,000 | |
| The testing completed. | |
| 42 | |
| 00:03:05,000 --> 00:03:11,000 | |
| And at the last best execution report. | |
| 43 | |
| 00:03:14,000 --> 00:03:15,000 | |
| Shared. | |
| 44 | |
| 00:03:15,000 --> 00:03:18,000 | |
| So these are the acceptance criteria for this task. | |
| 45 | |
| 00:03:18,000 --> 00:03:19,000 | |
| Okay. | |
| 46 | |
| 00:03:19,000 --> 00:03:24,000 | |
| Now I'll go and assign it to my tester. | |
| 47 | |
| 00:03:24,000 --> 00:03:25,000 | |
| Okay. | |
| 48 | |
| 00:03:25,000 --> 00:03:26,000 | |
| What does the priority? | |
| 49 | |
| 00:03:26,000 --> 00:03:27,000 | |
| I'm saying it's a high priority task. | |
| 50 | |
| 00:03:28,000 --> 00:03:36,000 | |
| I just create as of now, I'm not giving any estimation because as a lead, I don't know how many hours | |
| 51 | |
| 00:03:36,000 --> 00:03:37,000 | |
| my tester is going to take. | |
| 52 | |
| 00:03:37,000 --> 00:03:39,000 | |
| We have we can have two condition. | |
| 53 | |
| 00:03:40,000 --> 00:03:47,000 | |
| One is as a lead, I'll put hours, how many hours I'm giving to my tester for this task. | |
| 54 | |
| 00:03:48,000 --> 00:03:54,000 | |
| That is, that I want my tester to analyze this task and then put estimated hours. | |
| 55 | |
| 00:03:55,000 --> 00:03:57,000 | |
| So in both we it is correct. | |
| 56 | |
| 00:03:57,000 --> 00:04:03,000 | |
| Sometimes, if configured in the data, you will get estimated hours. | |
| 57 | |
| 00:04:03,000 --> 00:04:04,000 | |
| Option over here. | |
| 58 | |
| 00:04:04,000 --> 00:04:06,000 | |
| So you can put estimated hours. | |
| 59 | |
| 00:04:07,000 --> 00:04:08,000 | |
| Sometimes you will not get it. | |
| 60 | |
| 00:04:09,000 --> 00:04:13,000 | |
| The person who is going to work on this task will analyze and put estimated hours. | |
| 61 | |
| 00:04:14,000 --> 00:04:17,000 | |
| So as of now, I just put it up without any estimated hours. | |
| 62 | |
| 00:04:18,000 --> 00:04:18,000 | |
| Okay. | |
| 63 | |
| 00:04:19,000 --> 00:04:24,000 | |
| The Oscars created idea is a failed therapy known as a lead. | |
| 64 | |
| 00:04:24,000 --> 00:04:28,000 | |
| I have completed my task now as a tester. | |
| 65 | |
| 00:04:29,000 --> 00:04:31,000 | |
| I'm going to my dashboard. | |
| 66 | |
| 00:04:32,000 --> 00:04:33,000 | |
| So that's a dashboard of my tester. | |
| 67 | |
| 00:04:34,000 --> 00:04:35,000 | |
| Okay. | |
| 68 | |
| 00:04:35,000 --> 00:04:36,000 | |
| That is a task which is assigned to me. | |
| 69 | |
| 00:04:36,000 --> 00:04:37,000 | |
| Let's go and do it. | |
| 70 | |
| 00:04:38,000 --> 00:04:39,000 | |
| Okay. | |
| 71 | |
| 00:04:39,000 --> 00:04:39,000 | |
| As of now. | |
| 72 | |
| 00:04:40,000 --> 00:04:43,000 | |
| Now I'll go and try to analyze this task. | |
| 73 | |
| 00:04:43,000 --> 00:04:44,000 | |
| Okay. | |
| 74 | |
| 00:04:44,000 --> 00:04:45,000 | |
| After and this is iPhone. | |
| 75 | |
| 00:04:45,000 --> 00:04:50,000 | |
| It is going to take 15 hours or I'll see two days. | |
| 76 | |
| 00:04:50,000 --> 00:04:53,000 | |
| So you can put in the days or maybe in the hours. | |
| 77 | |
| 00:04:53,000 --> 00:04:54,000 | |
| So I take an example. | |
| 78 | |
| 00:04:54,000 --> 00:04:54,000 | |
| Okay. | |
| 79 | |
| 00:04:54,000 --> 00:04:56,000 | |
| You want to put in the form of hours. | |
| 80 | |
| 00:04:57,000 --> 00:04:57,000 | |
| Okay. | |
| 81 | |
| 00:04:57,000 --> 00:05:00,000 | |
| Here on the right hand side, you are getting show more fields. | |
| 82 | |
| 00:05:01,000 --> 00:05:03,000 | |
| I just click on this here. | |
| 83 | |
| 00:05:03,000 --> 00:05:05,000 | |
| You can put your estimation. | |
| 84 | |
| 00:05:05,000 --> 00:05:12,000 | |
| So I'm putting my estimation is 15 at which is 15 hours saved. | |
| 85 | |
| 00:05:12,000 --> 00:05:15,000 | |
| So it shows one seminar by four. | |
| 86 | |
| 00:05:15,000 --> 00:05:18,000 | |
| It takes eight are four a day. | |
| 87 | |
| 00:05:18,000 --> 00:05:19,000 | |
| But this is configurable. | |
| 88 | |
| 00:05:19,000 --> 00:05:20,000 | |
| You can change it. | |
| 89 | |
| 00:05:21,000 --> 00:05:22,000 | |
| Project admin can change it. | |
| 90 | |
| 00:05:23,000 --> 00:05:27,000 | |
| So as of now, original estimation is one day and 7 hours. | |
| 91 | |
| 00:05:28,000 --> 00:05:32,000 | |
| So I can see we have created a task, assign it to the tester. | |
| 92 | |
| 00:05:32,000 --> 00:05:34,000 | |
| And now estimated time has been given. | |
| 93 | |
| 00:05:36,000 --> 00:05:39,000 | |
| Now, as a tester, I have analyzed it. | |
| 94 | |
| 00:05:39,000 --> 00:05:40,000 | |
| I'll start working on this. | |
| 95 | |
| 00:05:41,000 --> 00:05:46,000 | |
| So when I'm starting this task, I'll just take it to the in progress. | |
| 96 | |
| 00:05:46,000 --> 00:05:49,000 | |
| Now, today, complete day. | |
| 97 | |
| 00:05:49,000 --> 00:05:52,000 | |
| I'm working on this task means I'm executing. | |
| 98 | |
| 00:05:52,000 --> 00:06:02,000 | |
| My task is I'm reporting my bug I verified fix issues I'm doing as bottom steps as a list acceptance | |
| 99 | |
| 00:06:02,000 --> 00:06:03,000 | |
| criteria. | |
| 100 | |
| 00:06:04,000 --> 00:06:04,000 | |
| Okay. | |
| 101 | |
| 00:06:04,000 --> 00:06:11,000 | |
| End of the day, this task is not completed, but I have invested total 8 hours in this task. | |
| 102 | |
| 00:06:11,000 --> 00:06:14,000 | |
| So previously we have defined estimated hours. | |
| 103 | |
| 00:06:15,000 --> 00:06:16,000 | |
| Now actual hours. | |
| 104 | |
| 00:06:16,000 --> 00:06:20,000 | |
| How many actual hours I have invested on this task? | |
| 105 | |
| 00:06:20,000 --> 00:06:21,000 | |
| I just go here. | |
| 106 | |
| 00:06:21,000 --> 00:06:27,000 | |
| You look at three dots, I just click on this log work as a tick on the log work. | |
| 107 | |
| 00:06:28,000 --> 00:06:30,000 | |
| It is asking for how many hours? | |
| 108 | |
| 00:06:30,000 --> 00:06:32,000 | |
| What is the time you invested on this? | |
| 109 | |
| 00:06:32,000 --> 00:06:37,000 | |
| You can put in the terms of hours or you can put in the terms of bids. | |
| 110 | |
| 00:06:37,000 --> 00:06:40,000 | |
| So I set one day I have already invested. | |
| 111 | |
| 00:06:40,000 --> 00:06:49,000 | |
| It will automatically calculate and show here 7 hours depending now what description you can define | |
| 112 | |
| 00:06:49,000 --> 00:07:00,000 | |
| like executed all functional cases, reported all books. | |
| 113 | |
| 00:07:01,000 --> 00:07:04,000 | |
| So these are the two task I have completed today. | |
| 114 | |
| 00:07:04,000 --> 00:07:05,000 | |
| I just save it. | |
| 115 | |
| 00:07:07,000 --> 00:07:08,000 | |
| You can check it. | |
| 116 | |
| 00:07:08,000 --> 00:07:11,000 | |
| Time tracking, one day logged and 7 hours remaining. | |
| 117 | |
| 00:07:12,000 --> 00:07:14,000 | |
| So today I started this task. | |
| 118 | |
| 00:07:14,000 --> 00:07:15,000 | |
| But it is not completed yet. | |
| 119 | |
| 00:07:15,000 --> 00:07:17,000 | |
| It is in the in progress. | |
| 120 | |
| 00:07:17,000 --> 00:07:18,000 | |
| I have reported my hours. | |
| 121 | |
| 00:07:19,000 --> 00:07:26,000 | |
| These hours are very important because by this anybody can understand how much you estimated and how | |
| 122 | |
| 00:07:26,000 --> 00:07:28,000 | |
| many hours you spent on a particular task. | |
| 123 | |
| 00:07:29,000 --> 00:07:30,000 | |
| So it's a good practice. | |
| 124 | |
| 00:07:30,000 --> 00:07:37,000 | |
| Whenever you are working on JIRA for task tracking, always put your hours in direct self. | |
| 125 | |
| 00:07:37,000 --> 00:07:42,000 | |
| So if you're managing one project, like how many hours you will do on a particular ticket or particular | |
| 126 | |
| 00:07:42,000 --> 00:07:45,000 | |
| task, he or she will not ask you. | |
| 127 | |
| 00:07:45,000 --> 00:07:48,000 | |
| They can just go directly on the JIRA and check it over here. | |
| 128 | |
| 00:07:49,000 --> 00:07:50,000 | |
| Okay. | |
| 129 | |
| 00:07:50,000 --> 00:07:53,000 | |
| Next day I come to my office and start working on this task again. | |
| 130 | |
| 00:07:54,000 --> 00:07:58,000 | |
| Now, today, end of the day, I have completed it. | |
| 131 | |
| 00:07:58,000 --> 00:08:01,000 | |
| So what I'll do is, first of all, I'll just go here. | |
| 132 | |
| 00:08:02,000 --> 00:08:02,000 | |
| Log work. | |
| 133 | |
| 00:08:03,000 --> 00:08:10,000 | |
| I have spent 6 hours even original estimation was I'll take one day and 7 hours. | |
| 134 | |
| 00:08:10,000 --> 00:08:12,000 | |
| But the task is completed in the 6 hours. | |
| 135 | |
| 00:08:12,000 --> 00:08:13,000 | |
| So. | |
| 136 | |
| 00:08:13,000 --> 00:08:14,000 | |
| One artist bending. | |
| 137 | |
| 00:08:15,000 --> 00:08:21,000 | |
| So it might be possible if you estimated the task for 20 hours, it will complete in the 20 hours. | |
| 138 | |
| 00:08:21,000 --> 00:08:26,000 | |
| But it also possible that if you estimate it for 20 hours, but the task is completed in 15 hours, | |
| 139 | |
| 00:08:27,000 --> 00:08:34,000 | |
| so you will put actual hours you spend on a task and sometimes it can take more than that as well. | |
| 140 | |
| 00:08:34,000 --> 00:08:41,000 | |
| Means you estimated it will take 20 hours, but in actual it took 25 hours. | |
| 141 | |
| 00:08:41,000 --> 00:08:44,000 | |
| So you should have your justification like previously. | |
| 142 | |
| 00:08:44,000 --> 00:08:47,000 | |
| While estimation I have given 20 hours. | |
| 143 | |
| 00:08:47,000 --> 00:08:49,000 | |
| But while working, we found this this problem. | |
| 144 | |
| 00:08:49,000 --> 00:08:51,000 | |
| Because of that, it took 24 hours. | |
| 145 | |
| 00:08:52,000 --> 00:08:53,000 | |
| So you should have your justification. | |
| 146 | |
| 00:08:54,000 --> 00:09:01,000 | |
| You can put less number of hours or more actual hours as compared to the estimated hours. | |
| 147 | |
| 00:09:01,000 --> 00:09:05,000 | |
| Okay, I'm saying task completed. | |
| 148 | |
| 00:09:06,000 --> 00:09:07,000 | |
| That is done. | |
| 149 | |
| 00:09:07,000 --> 00:09:13,000 | |
| I just click on the save task is completed, I'll just market them. | |
| 150 | |
| 00:09:13,000 --> 00:09:19,000 | |
| So here we have reported RS We have put our comments for each and every day. | |
| 151 | |
| 00:09:20,000 --> 00:09:22,000 | |
| No, my lead. | |
| 152 | |
| 00:09:22,000 --> 00:09:25,000 | |
| Want to check what exactly we have perform on this task. | |
| 153 | |
| 00:09:26,000 --> 00:09:28,000 | |
| So the lead will not ask me. | |
| 154 | |
| 00:09:28,000 --> 00:09:30,000 | |
| He or she will go to the JIRA. | |
| 155 | |
| 00:09:30,000 --> 00:09:34,000 | |
| So I'm just coming as a lead and I'm just searching for that. | |
| 156 | |
| 00:09:34,000 --> 00:09:39,000 | |
| But it was a file 13, which I just created. | |
| 157 | |
| 00:09:39,000 --> 00:09:41,000 | |
| So I'm just going for 13. | |
| 158 | |
| 00:09:42,000 --> 00:09:45,000 | |
| It's a F, I end 30. | |
| 159 | |
| 00:09:46,000 --> 00:09:46,000 | |
| Okay. | |
| 160 | |
| 00:09:46,000 --> 00:09:48,000 | |
| That was the task I have given to you. | |
| 161 | |
| 00:09:48,000 --> 00:09:49,000 | |
| You market done? | |
| 162 | |
| 00:09:49,000 --> 00:09:50,000 | |
| I want to check it. | |
| 163 | |
| 00:09:50,000 --> 00:09:55,000 | |
| I'll go to the task and here in the bottom you'll get a work log. | |
| 164 | |
| 00:09:55,000 --> 00:09:58,000 | |
| You can just click on this here. | |
| 165 | |
| 00:09:58,000 --> 00:10:02,000 | |
| You can check testing hours, which does put with the comments. | |
| 166 | |
| 00:10:03,000 --> 00:10:08,000 | |
| So first, it put one day executed, all test cases reported all. | |
| 167 | |
| 00:10:08,000 --> 00:10:12,000 | |
| But in the second day, he or she put 6 hours and the task is completed. | |
| 168 | |
| 00:10:13,000 --> 00:10:17,000 | |
| So as a lead, I'm not asking you what you have done on the day one, what you have done on the data. | |
| 169 | |
| 00:10:18,000 --> 00:10:21,000 | |
| We can just go and check it over here on the ticket itself. | |
| 170 | |
| 00:10:22,000 --> 00:10:24,000 | |
| Say here on that issue or task itself. | |
| 171 | |
| 00:10:25,000 --> 00:10:29,000 | |
| So that is that one page of using JIRA for the task management. | |
| 172 | |
| 00:10:29,000 --> 00:10:32,000 | |
| Now, Weber Communication is almost finished. | |
| 173 | |
| 00:10:33,000 --> 00:10:34,000 | |
| Mail communication is almost finished. | |
| 174 | |
| 00:10:34,000 --> 00:10:41,000 | |
| We are just doing everything here on the JIRA so anybody can track what exactly happening in the team | |
| 175 | |
| 00:10:41,000 --> 00:10:46,000 | |
| means, who is working on which ticket, what all the things are completed, what all the things are | |
| 176 | |
| 00:10:46,000 --> 00:10:48,000 | |
| pending, how many hours spent. | |
| 177 | |
| 00:10:48,000 --> 00:10:51,000 | |
| So everything can be tracked here on the JIRA itself. | |
| 178 | |
| 00:10:53,000 --> 00:11:00,000 | |
| So here in the session we have seen how we can go for estimation hours and then actual time logging. | |
| 179 | |
| 00:11:01,000 --> 00:11:04,000 | |
| That's all we have for decision tanks watching this video. | |