| Topic | Presenter | Summary | Duration |
| ------------------------------------ | --------- | -------------------------------------------------------------------------- | -------- |
| Updating Tickets and Daily Azure Use | Daniel O. | Daniel goes over updating tickets and daily azure use with new developers. | 28:38 |00:00:07.050 --> 00:00:08.454 I haven't done one of these00:00:08.454 --> 00:00:10.229 for any of you new folks yet,00:00:10.230 --> 00:00:12.222 so I want to just kind of quick00:00:12.222 --> 00:00:13.974 give you an overview of kind00:00:13.974 --> 00:00:15.762 of what my whole process is.00:00:15.770 --> 00:00:17.130 What I'm looking for,00:00:17.130 --> 00:00:19.970 and just sort of the best practices.00:00:19.970 --> 00:00:22.690 I'm very full aware that most of y'all,00:00:22.690 --> 00:00:23.450 if not all of you.00:00:23.450 --> 00:00:25.112 Hopefully all of you went through00:00:25.112 --> 00:00:26.650 training on this already earlier,00:00:26.650 --> 00:00:28.890 so this might just be a quick refresher.00:00:28.890 --> 00:00:30.130 And like I was saying,00:00:30.130 --> 00:00:33.784 right when we started in here that.00:00:33.790 --> 00:00:34.918 I I really don't expect this00:00:34.918 --> 00:00:36.030 taking more than 30 minutes,00:00:36.030 --> 00:00:37.910 but if you guys have questions and stuff,00:00:37.910 --> 00:00:41.690 do not feel a hamstring by that 30 minutes.00:00:41.690 --> 00:00:45.114 So start off with kind of what I do.00:00:45.120 --> 00:00:49.620 So one of the major goals of my position00:00:49.620 --> 00:00:53.690 and what I do here is tracking the00:00:53.690 --> 00:00:57.190 ongoing work that's done in the spring00:00:57.190 --> 00:00:59.990 and that is achieved by all my silly00:00:59.990 --> 00:01:02.021 little metrics that you guys hear00:01:02.021 --> 00:01:04.400 me talking about on a daily basis.00:01:04.400 --> 00:01:08.015 So what we have here on this page is00:01:08.015 --> 00:01:11.410 an ongoing update of what Azure says00:01:11.410 --> 00:01:14.859 your work is at at that given day.00:01:14.860 --> 00:01:16.448 This is burned down,00:01:16.448 --> 00:01:18.433 so when everyone talks about,00:01:18.440 --> 00:01:22.970 burn down, burn down is just.00:01:22.970 --> 00:01:24.080 The work assigned.00:01:26.120 --> 00:01:26.610 Remaining.00:01:28.670 --> 00:01:30.110 That's the extent of it.00:01:30.110 --> 00:01:33.687 It decreases by your A by your00:01:33.687 --> 00:01:35.538 billable goal, a day, right?00:01:40.120 --> 00:01:41.664 Which for all of you is 7 hours.00:01:44.090 --> 00:01:45.710 What I'm looking for on this,00:01:45.710 --> 00:01:48.006 a perfect burn down and let's see.00:01:48.010 --> 00:01:49.330 We've always got Mr Jonathan Lee,00:01:49.330 --> 00:01:52.026 who's always generally pretty close is00:01:52.026 --> 00:01:54.938 gonna be hitting just about exactly at00:01:54.938 --> 00:01:57.850 that seven hour mark the whole time.00:01:57.850 --> 00:02:02.116 Now that would be if your work that you00:02:02.116 --> 00:02:06.234 were doing fully met the estimates, right?00:02:06.234 --> 00:02:08.970 So let's say it took two hours and the00:02:09.042 --> 00:02:12.010 estimate was two hours and that you had no00:02:12.010 --> 00:02:13.800 other interruptions and everything was cool.00:02:13.800 --> 00:02:17.088 Now we get clarity and leadership.00:02:17.090 --> 00:02:19.010 Everyone down through the project managers.00:02:19.010 --> 00:02:20.890 Everybody knows that that's00:02:20.890 --> 00:02:22.300 not necessarily realistic,00:02:22.300 --> 00:02:23.630 but that would be what it is.00:02:25.930 --> 00:02:28.258 So what we also track over00:02:28.258 --> 00:02:32.460 here is burn up burn up is.00:02:34.830 --> 00:02:36.670 Actual completed.00:02:38.950 --> 00:02:43.758 Work. Unrelated to what's remaining.00:02:46.450 --> 00:02:49.150 So if you have a task that was supposed00:02:49.150 --> 00:02:52.170 to take 2 hours and it took you 7 hours,00:02:52.170 --> 00:02:54.018 you know that's a whole other00:02:54.018 --> 00:02:55.959 conversation that we have to have00:02:55.959 --> 00:02:58.234 related to where the tickets at budgetary00:02:58.234 --> 00:02:59.847 concerns etc etc down the line.00:02:59.850 --> 00:03:01.194 But at the end of the day,00:03:01.200 --> 00:03:04.430 that's what I'm tracking here.00:03:04.430 --> 00:03:06.100 So we have burnt up, burned down.00:03:06.100 --> 00:03:08.050 The ultimate goal is for burn00:03:08.050 --> 00:03:10.029 up and burn down to match.00:03:10.030 --> 00:03:13.180 We want burn up to always match burn down.00:03:16.530 --> 00:03:17.738 Always equals burned down.00:03:20.080 --> 00:03:23.110 Now what does that mean in00:03:23.110 --> 00:03:25.140 like the specifics here, right?00:03:25.140 --> 00:03:28.150 So let's say that you had this task that went00:03:28.221 --> 00:03:30.891 over by 7 hours or went over by 5 hours.00:03:30.900 --> 00:03:32.608 You would make sure that your project00:03:32.608 --> 00:03:34.349 manager knew that day that happened when00:03:34.349 --> 00:03:36.019 actually you would want them to know00:03:36.019 --> 00:03:37.940 when you went over by like an hour or so,00:03:37.940 --> 00:03:39.140 or even like 30 minutes.00:03:39.140 --> 00:03:40.803 If you think it's gonna take longer, etc.00:03:40.803 --> 00:03:42.418 We've beaten that Internet phone,00:03:42.420 --> 00:03:44.064 get into that there,00:03:44.064 --> 00:03:47.250 but we would then want to reflex.00:03:47.250 --> 00:03:49.908 On the actual.00:03:49.910 --> 00:03:52.670 And that would mean we go through your00:03:52.670 --> 00:03:55.336 Sprint and remove tasks so that your00:03:55.336 --> 00:03:58.019 burned down is matching your burned up.00:04:00.440 --> 00:04:03.156 Now there are some issues with that,00:04:03.160 --> 00:04:05.165 of course, right. Sometimes a00:04:05.165 --> 00:04:07.960 developer will want to get more done.00:04:07.960 --> 00:04:09.720 Sometimes will have additional deadlines00:04:09.720 --> 00:04:12.740 where us PS will have to go argue about it.00:04:12.740 --> 00:04:14.819 Sometimes there are other block tasks that00:04:14.819 --> 00:04:17.092 we leave in there with the chance that00:04:17.092 --> 00:04:19.298 they might be able to get pushed out.00:04:19.300 --> 00:04:20.590 But like I was saying,00:04:20.590 --> 00:04:23.731 kind of the top at the end of the00:04:23.731 --> 00:04:27.236 Sprint burn up is how we determine the00:04:27.236 --> 00:04:30.300 effectiveness of a developer and burn.00:04:30.300 --> 00:04:34.792 Down is how we. Reflect on the, uh, useful.00:04:34.792 --> 00:04:36.496 Not useful, says not.00:04:36.500 --> 00:04:37.640 We'll say affection as well.00:04:37.640 --> 00:04:40.740 Effectiveness of a PM.00:04:40.740 --> 00:04:42.651 Now also on the sheet you'll see00:04:42.651 --> 00:04:44.910 I have my blocked columns here.00:04:44.910 --> 00:04:47.170 This is just for me to know so I can00:04:47.234 --> 00:04:49.304 check what's blocked with how much00:04:49.304 --> 00:04:51.627 block time and who's been in Pod A.00:04:51.630 --> 00:04:54.526 Sprints knows how much I've been harping00:04:54.526 --> 00:04:57.454 on a lot of the Biden athlete tickets.00:04:57.460 --> 00:04:59.826 And then we have our line item00:04:59.826 --> 00:05:02.039 here for extended estimation time.00:05:02.040 --> 00:05:03.433 This again is just for us to00:05:03.433 --> 00:05:04.320 keep track of that.00:05:04.320 --> 00:05:05.748 What projects are taking00:05:05.748 --> 00:05:06.819 longer than expected.00:05:09.500 --> 00:05:12.858 Sometimes if someone has a PTO00:05:12.858 --> 00:05:14.526 that happens in the middle of00:05:14.526 --> 00:05:16.097 the Sprint that wasn't reflected00:05:16.097 --> 00:05:18.137 at the beginning of the Sprint,00:05:18.140 --> 00:05:19.556 will add this here and that00:05:19.556 --> 00:05:20.970 gets added to your burn up.00:05:24.410 --> 00:05:25.566 This is, of course,00:05:25.566 --> 00:05:27.710 you know this is directly from Azure.00:05:27.710 --> 00:05:30.050 The completed work expected total work.00:05:30.050 --> 00:05:32.650 This is just the simple math equation of00:05:32.650 --> 00:05:35.555 how much it should be based on your daily00:05:35.555 --> 00:05:38.019 burn down that you're doing in a day.00:05:38.020 --> 00:05:40.240 This column here for logged is00:05:40.240 --> 00:05:42.800 how much time was logged in EP.00:05:42.800 --> 00:05:45.621 It's a great way for us to00:05:45.621 --> 00:05:47.660 track things that are off.00:05:47.660 --> 00:05:50.782 Meaning, if you had say 32 hours00:05:50.782 --> 00:05:54.910 logged in a or 30 hours logged in EP00:05:54.910 --> 00:05:57.605 and but 32 hours logged in Azure,00:05:57.610 --> 00:05:59.430 we would probably like OK,00:05:59.430 --> 00:06:01.770 we'll check back on that.00:06:01.770 --> 00:06:03.828 But then like let's find 1
00:06:03.828 --> 00:06:05.200 where it's the opposite,00:06:05.200 --> 00:06:07.927 I need one where it's more here with Mr.00:06:07.930 --> 00:06:09.568 Lion. We have 26 hours logged in,00:06:09.570 --> 00:06:11.886 EP only 20 hours. Logged in.00:06:11.890 --> 00:06:14.794 Azure will want to see what tickets and00:06:14.794 --> 00:06:17.809 other items went longer or additional work.00:06:17.810 --> 00:06:20.729 That happened that we need to make00:06:20.729 --> 00:06:23.457 sure it makes it to the board.00:06:23.460 --> 00:06:24.810 Now, does anyone have any questions00:06:24.810 --> 00:06:26.460 about this kind of general tracking?00:06:26.460 --> 00:06:29.141 That idea for me right now I00:06:29.141 --> 00:06:31.520 have zero hours logged in EP.00:06:31.520 --> 00:06:34.096 Is that because I'm not assigned to00:06:34.096 --> 00:06:35.959 any like particular project yet and00:06:35.959 --> 00:06:38.120 so like the hours that I have logged00:06:38.120 --> 00:06:40.094 in EP aren't assigned to anything?00:06:40.100 --> 00:06:40.810 You know what it is?00:06:40.810 --> 00:06:43.085 It's because you have 0 billable hours,00:06:43.090 --> 00:06:44.596 so it's just that flat number.00:06:44.600 --> 00:06:45.224 You're alright.00:06:45.224 --> 00:06:47.096 And especially like hero in your00:06:47.096 --> 00:06:49.452 first couple weeks here, don't get.00:06:49.452 --> 00:06:52.920 To you know, worried about anything on here?00:06:52.920 --> 00:06:55.120 Uhm, it's just as you get ramped up.00:06:55.120 --> 00:06:56.064 I like to make sure you guys know.00:06:56.070 --> 00:06:58.158 Kind of what we're looking for long term.00:06:58.160 --> 00:07:02.200 OK, gotcha, thanks of course.00:07:02.200 --> 00:07:04.499 So those are the big metrics there, uhm,00:07:04.499 --> 00:07:07.010 and then we do this also at the end,00:07:07.010 --> 00:07:09.899 which is the kind of groupings by front end,00:07:09.900 --> 00:07:11.248 back, end and pods.00:07:11.248 --> 00:07:12.933 As well as the exceeds,00:07:12.940 --> 00:07:14.755 we're taking these numbers to00:07:14.755 --> 00:07:17.453 see what the exceeds our of the00:07:17.453 --> 00:07:19.877 percentage actuals so that we can00:07:19.877 --> 00:07:21.939 hopefully long-term make some plans00:07:21.939 --> 00:07:23.914 for what works actually taking.00:07:23.920 --> 00:07:26.413 Now I'm sure you guys have all heard this.00:07:26.420 --> 00:07:27.660 In standups people will say,00:07:27.660 --> 00:07:27.999 hey,00:07:27.999 --> 00:07:30.372 I did a little extra work on00:07:30.372 --> 00:07:32.144 project ABCD or whatever but00:07:32.144 --> 00:07:34.517 I didn't have a ticket for it.00:07:34.520 --> 00:07:37.652 If you work on anything not00:07:37.652 --> 00:07:40.690 in your Sprint it is well,00:07:40.690 --> 00:07:43.140 it's your right and responsibility00:07:43.140 --> 00:07:46.650 to request a ticket from the00:07:46.650 --> 00:07:50.150 project manager or otherwise.00:07:50.150 --> 00:07:51.994 Who requested this work?00:07:51.994 --> 00:07:55.789 So for instance today for you guys I owe.00:07:55.790 --> 00:07:59.230 All four of you tickets for this meeting,00:07:59.230 --> 00:07:59.524 right?00:07:59.524 --> 00:08:01.288 Just gonna make one really quick,00:08:01.290 --> 00:08:02.514 but I will go through and make them all.00:08:09.290 --> 00:08:11.552 It said I'm going to try00:08:11.552 --> 00:08:13.779 and get this done with N.00:08:13.780 --> 00:08:15.540 Uh, within 30 minutes,00:08:15.540 --> 00:08:18.720 but I estimated this at an hour.00:08:18.720 --> 00:08:21.240 But it wasn't in the Sprint,00:08:21.240 --> 00:08:23.340 so because this wasn't in the Sprint,00:08:23.340 --> 00:08:24.168 the original estimate on00:08:24.168 --> 00:08:25.410 this is going to be 0.00:08:27.720 --> 00:08:30.618 Even if I do have an estimate for it,00:08:30.620 --> 00:08:32.125 it didn't make it into00:08:32.125 --> 00:08:34.050 the Sprint as a work item.00:08:34.050 --> 00:08:35.586 It got added to your Sprint,00:08:35.590 --> 00:08:37.814 so it's gonna have an original estimate zero.00:08:37.820 --> 00:08:39.941 The remaining is going to be the00:08:39.941 --> 00:08:42.180 total amount of work planned for it,00:08:42.180 --> 00:08:43.740 so if something gets added to your Sprint,00:08:43.740 --> 00:08:44.980 it's a one hour task.00:08:44.980 --> 00:08:46.452 It'll go in there.00:08:46.452 --> 00:08:48.292 You guys are not responsible00:08:48.292 --> 00:08:49.959 for creating tickets,00:08:49.960 --> 00:08:53.488 but you are also welcome to do so.00:08:53.490 --> 00:08:55.610 If you do need to create a ticket,00:08:55.610 --> 00:08:58.410 please just follow the kind of standard00:08:58.410 --> 00:09:00.571 naming convention where it is the00:09:00.571 --> 00:09:02.760 acronym for the project and then a00:09:02.760 --> 00:09:05.070 very short description of what it is.00:09:05.070 --> 00:09:07.142 Inside you also want to put a little00:09:07.142 --> 00:09:09.648 bit of a text in the description field.00:09:27.980 --> 00:09:28.430 Trap.00:09:33.490 --> 00:09:36.448 There it is. Happy working now.00:09:44.840 --> 00:09:46.175 Well, does anyone have any00:09:46.175 --> 00:09:47.510 questions about ZAP process there?00:09:51.650 --> 00:09:53.828 Should I be worried about creating00:09:53.828 --> 00:09:55.949 tickets for like all the like?00:09:55.950 --> 00:09:57.335 Various training stuff that I've00:09:57.335 --> 00:09:59.391 been doing or is that for the most00:09:59.391 --> 00:10:01.174 part OK for me to just kind of00:10:01.174 --> 00:10:02.629 since it's not billable anyway?00:10:02.630 --> 00:10:06.990 Yeah, that's a great question, so uhm.00:10:06.990 --> 00:10:08.555 The first question I would00:10:08.555 --> 00:10:11.077 have is do you have any ticket00:10:11.077 --> 00:10:12.845 that would encapsulate that?00:10:12.850 --> 00:10:14.010 Not all of it,00:10:14.010 --> 00:10:16.126 so like the trading tickets that I00:10:16.126 --> 00:10:18.289 have are like pretty specific to like.00:10:18.290 --> 00:10:20.439 A lesson or one of the things.00:10:22.550 --> 00:10:24.006 So I wouldn't say all of it.00:10:24.010 --> 00:10:24.958 Yeah, take a look.00:10:36.970 --> 00:10:39.559 Copy, copy, copy.00:10:39.560 --> 00:10:41.840 OK, so let's take a look at here.00:10:41.840 --> 00:10:43.784 So a kind of slide to00:10:43.784 --> 00:10:45.080 the next section here.00:10:45.080 --> 00:10:47.306 Have you guys all gotten used00:10:47.306 --> 00:10:49.630 to using Azure from this view?00:10:49.630 --> 00:10:51.334 Project we get kind of like00:10:51.334 --> 00:10:53.774 an overview of the view of the00:10:53.774 --> 00:10:55.358 Azure Sprint Board itself.00:11:00.630 --> 00:11:01.740 I've got to understand it.00:11:04.570 --> 00:11:05.530 Cool, I'm like waiting,00:11:05.530 --> 00:11:07.335 you know, but so no dude you00:11:07.335 --> 00:11:09.310 got it's all good it's all good.00:11:09.310 --> 00:11:11.366 OK so just kind of quick I'm gonna00:11:11.366 --> 00:11:13.558 send you with a few quick little00:11:13.558 --> 00:11:15.173 overview overview things on it00:11:15.235 --> 00:11:17.147 we won't go to in depth with it.00:11:17.150 --> 00:11:18.580 You always wanna make sure00:11:18.580 --> 00:11:20.010 this is all project backlog.00:11:20.010 --> 00:11:21.431 There is gonna be a time in00:11:21.431 --> 00:11:22.390 the relatively near future.00:11:22.390 --> 00:11:23.979 I would say probably by the end00:11:23.979 --> 00:11:25.559 of Q2 that we have everyone00:11:25.559 --> 00:11:27.245 split off to their specific pods00:11:27.245 --> 00:11:28.987 so you can look in that view,00:11:28.990 --> 00:11:31.387 but for the time being you're00:11:31.387 --> 00:11:32.989 always gonna do all project backlog.00:11:32.990 --> 00:11:34.558 So if you're ever like hey where's00:11:34.558 --> 00:11:37.518 all my stuff? Check this up here.00:11:37.520 --> 00:11:39.878 Second options of course column options.00:11:39.880 --> 00:11:46.672 You can add any other UM columns for00:11:46.672 --> 00:11:51.350 yourself. You can also, uh, going here.00:11:51.350 --> 00:11:53.177 You can check work in the next00:11:53.177 --> 00:11:54.549 Sprint right there and that'll00:11:54.549 --> 00:11:56.145 take you to the next Sprint.00:11:56.150 --> 00:11:57.470 Sometimes this is useful if00:11:57.470 --> 00:11:58.790 you wanna pull work forward.00:11:58.790 --> 00:12:01.206 Let's say you get really ahead of yourself.00:12:01.210 --> 00:12:04.020 You can pull work forward.00:12:04.020 --> 00:12:07.534 You can use this view to highlight00:12:07.534 --> 00:12:09.068 one person's work items, right?00:12:09.068 --> 00:12:10.353 So let's say I'm here.00:12:10.360 --> 00:12:11.080 Oh, I'm going here,00:12:11.080 --> 00:12:13.170 but in this case it would be like an app, me.00:12:19.390 --> 00:12:22.758 This way it keeps any user story level00:12:22.758 --> 00:12:26.406 open that you have a task assigned to it.00:12:26.410 --> 00:12:28.839 Sometimes this view is useful if you00:12:28.839 --> 00:12:31.308 wanna see what other people are working00:12:31.308 --> 00:12:34.030 on the same user story as yourself.00:12:34.030 --> 00:12:36.190 But you want to highlight00:12:36.190 --> 00:12:37.486 your task specifically.00:12:42.070 --> 00:12:43.942 Next up here you have the00:12:43.942 --> 00:12:46.050 group at by people or stories.00:12:46.050 --> 00:12:47.370 If I group this by people,00:12:47.370 --> 00:12:49.372 it's not gonna show me the user00:12:49.372 --> 00:12:51.608 stories that the task is associated to.00:12:51.610 --> 00:12:53.715 It's just gonna show me00:12:53.715 --> 00:12:54.978 my tasks specifically.00:12:57.950 --> 00:12:59.612 So my suggestion is always to00:12:59.612 --> 00:13:01.510 keep this at the story level,00:13:01.510 --> 00:13:02.896 but as you guys gonna get cozy00:13:02.896 --> 00:13:04.149 you'll kind of have your own.00:13:04.150 --> 00:13:08.110 Your own mileage will vary sort of situation.00:13:08.110 --> 00:13:09.762 The side pane we have to work00:13:09.762 --> 00:13:11.089 details which is right here,00:13:11.090 --> 00:13:12.420 which is your burn down.00:13:12.420 --> 00:13:15.244 You can get a glance at any time.00:13:15.250 --> 00:13:16.985 Or planning which is going00:13:16.985 --> 00:13:18.720 to be the Sprint view.00:13:18.720 --> 00:13:20.045 This is something you guys00:13:20.045 --> 00:13:21.370 will rarely if never use.00:13:21.370 --> 00:13:24.915 This is much more used by PMS.00:13:24.915 --> 00:13:27.878 I can drag work into next sprints if I want.00:13:33.880 --> 00:13:34.924 And like I said, you probably00:13:34.924 --> 00:13:36.318 want to keep it off at all times.00:13:36.320 --> 00:13:37.440 And then here's the filter.00:13:37.440 --> 00:13:38.992 The filter is cumulative,00:13:38.992 --> 00:13:42.938 so if I do CCS, it's gonna pull00:13:42.938 --> 00:13:46.934 up everything by that project CCS.00:13:46.940 --> 00:13:51.634 From every developer. If I do area,00:13:51.634 --> 00:13:55.390 it'll knock it down to one specific.00:13:55.390 --> 00:13:56.990 Area, path and Area path00:13:56.990 --> 00:13:58.590 is of course a project.00:13:58.590 --> 00:14:00.348 So if I do CCS here,00:14:00.350 --> 00:14:02.030 still going through that same00:14:02.030 --> 00:14:03.710 view of every CCS project.00:14:03.710 --> 00:14:05.523 But let's say I wanna look at00:14:05.523 --> 00:14:07.266 anything in CCS with check out so00:14:07.266 --> 00:14:09.309 I can see who else is working on.00:14:09.310 --> 00:14:11.529 Check out in the Sprint with me.00:14:11.530 --> 00:14:13.018 So I gotta check out functionality00:14:13.018 --> 00:14:13.514 for Brendan.00:14:13.520 --> 00:14:15.040 It looks like Tristan melted a little bit00:14:15.040 --> 00:14:16.649 of check out and then there's this here.00:14:16.650 --> 00:14:18.669 That's already up.00:14:18.670 --> 00:14:21.638 You can also do a sign to00:14:21.638 --> 00:14:23.426 write simple states of course,00:14:23.426 --> 00:14:24.986 is pretty straightforward tags if00:14:24.986 --> 00:14:26.700 you're looking for anything specific.00:14:26.700 --> 00:14:29.500 Another way to narrow down a project.00:14:31.640 --> 00:14:33.012 And they're like, OK,00:14:33.012 --> 00:14:35.810 so as you are going about your day,00:14:35.810 --> 00:14:39.072 the expectation is that your time logs00:14:39.072 --> 00:14:42.938 and your Azure is updated as you're going,00:14:42.940 --> 00:14:46.720 or at the very least by the end of the day.00:14:46.720 --> 00:14:48.520 So if you're working on tasks,00:14:48.520 --> 00:14:50.220 if you're working on tickets,00:14:50.220 --> 00:14:52.590 if you're working through things,00:14:52.590 --> 00:14:56.614 you should be updating them as you go.00:14:56.620 --> 00:14:57.700 So let's just kind of.00:14:57.700 --> 00:14:59.310 I'm gonna play with someone00:14:59.310 --> 00:15:01.280 ticket that won't mind too much.00:15:01.280 --> 00:15:03.616 Let me find a good one over here.00:15:03.620 --> 00:15:05.180 Unless Jeremy Larosas stuff here for00:15:05.180 --> 00:15:08.052 a second, so that's a documentation.00:15:08.052 --> 00:15:10.446 One. I need one that's a task.00:15:14.130 --> 00:15:16.010 Yeah, I must have locked jaws ticket here,00:15:16.010 --> 00:15:21.427 OK? So in the beginning of your day.00:15:21.430 --> 00:15:23.230 Uhm, you'll want to look through00:15:23.230 --> 00:15:25.089 and said we're picking on lockjaw.00:15:25.090 --> 00:15:26.910 I'm gonna pull this up.00:15:26.910 --> 00:15:28.890 You have your Sprint view where00:15:28.890 --> 00:15:30.623 it's just showing you your00:15:30.623 --> 00:15:32.338 user stories and your tasks.00:15:32.340 --> 00:15:33.996 You're looking at what you have to do.00:15:34.000 --> 00:15:34.969 You're saying, OK.00:15:34.969 --> 00:15:37.650 Here's everything I got on my board today.00:15:39.670 --> 00:15:41.182 I wanna start working on let's00:15:41.182 --> 00:15:42.850 say like we said we're gonna00:15:42.850 --> 00:15:44.345 mess with the Aqua tickets,00:15:44.350 --> 00:15:45.718 so let's mess with Aqua tickets.00:15:48.490 --> 00:15:50.236 I'm gonna work on this today00:15:50.240 --> 00:15:51.815 when you're ready to work on it.00:15:51.820 --> 00:15:54.194 First things first, you're gonna we're00:15:54.194 --> 00:15:56.814 gonna set this up you're gonna drag it00:15:56.814 --> 00:15:59.600 over to active and then you're gonna00:15:59.600 --> 00:16:02.330 make the state to end development.00:16:02.330 --> 00:16:04.940 That lets me know and your PM's know that00:16:04.940 --> 00:16:07.829 this is being worked on in the active column.00:16:07.830 --> 00:16:09.230 Leave it in new if you haven't00:16:09.230 --> 00:16:10.424 touched it yet. That's totally cool.00:16:10.424 --> 00:16:12.366 If you want to set up a few different00:16:12.366 --> 00:16:13.884 items for yourself on that day,00:16:13.890 --> 00:16:15.416 again, keep them in new until you00:16:15.416 --> 00:16:16.970 actually put your fingers on the code.00:16:16.970 --> 00:16:18.809 Move it over.00:16:18.810 --> 00:16:20.080 As you're working on it,00:16:20.080 --> 00:16:23.118 you're going to be decreasing the remaining.00:16:23.120 --> 00:16:24.548 And increasing the completed.00:16:26.760 --> 00:16:29.505 Let's say that that was the extent of it.00:16:29.510 --> 00:16:30.825 And you're ready for that00:16:30.825 --> 00:16:32.140 pull request to come in.00:16:32.140 --> 00:16:34.835 Drag it right over the pier created.00:16:34.840 --> 00:16:36.744 And get that pull request in there.00:16:38.870 --> 00:16:41.186 When that pull request is created,00:16:41.190 --> 00:16:44.389 you're gonna move it over to closed.00:16:44.390 --> 00:16:45.737 Once it's enclosed,00:16:45.737 --> 00:16:48.880 you're gonna want to change the state.00:16:48.880 --> 00:16:52.079 Now states that we use in development00:16:52.079 --> 00:16:54.815 so PM's developers etc are primarily00:16:54.815 --> 00:16:57.840 going to be living in the new.00:16:57.840 --> 00:17:00.890 Of course in development code00:17:00.890 --> 00:17:02.520 complete or deploy to QA.00:17:04.630 --> 00:17:07.108 That's the that's the extent of it.00:17:07.110 --> 00:17:09.528 If the code is in development,00:17:09.530 --> 00:17:11.350 of course we understand what that is.00:17:11.350 --> 00:17:14.188 It's a code, is code complete.00:17:14.190 --> 00:17:16.136 That means that the either pull request00:17:16.136 --> 00:17:18.426 is up or the code itself is done,00:17:18.430 --> 00:17:20.506 but it hasn't been pushed to00:17:20.506 --> 00:17:22.530 a QA environment for testing.00:17:22.530 --> 00:17:24.090 If it's deployed to QA,00:17:24.090 --> 00:17:26.939 that means it's up for testing and00:17:26.939 --> 00:17:29.299 it's officially off of your plate.00:17:29.300 --> 00:17:31.575 If you leave user stories and code,00:17:31.580 --> 00:17:32.916 complete project managers are00:17:32.916 --> 00:17:34.920 going to have to bother you.00:17:34.920 --> 00:17:36.819 They are going to have to track you down.00:17:36.820 --> 00:17:37.880 You're gonna have to make.00:17:37.880 --> 00:17:39.196 You're gonna have to go back through.00:17:39.200 --> 00:17:40.408 Check your code again.00:17:40.408 --> 00:17:42.520 It's gonna take more time for you.00:17:42.520 --> 00:17:45.504 So please as you're going through the00:17:45.504 --> 00:17:48.288 PR process and the deployment process,00:17:48.290 --> 00:17:49.745 make sure that you're tagging00:17:49.745 --> 00:17:51.200 things for deployed to QA.00:17:51.200 --> 00:17:51.742 Now.00:17:51.742 --> 00:17:54.994 Some projects have a pipeline that00:17:54.994 --> 00:17:58.768 works as such that you don't know.00:17:58.770 --> 00:18:01.199 When your code is actually moved from00:18:01.199 --> 00:18:03.856 code complete to deploy to QA because00:18:03.856 --> 00:18:05.786 there is some deployment process.00:18:05.790 --> 00:18:07.540 Maybe there's a larger PR00:18:07.540 --> 00:18:09.890 that needs to be sent across.00:18:09.890 --> 00:18:12.606 Maybe the solution needs to be rebuilt00:18:12.610 --> 00:18:14.450 a variety of different reasons,00:18:14.450 --> 00:18:15.382 that's OK,00:18:15.382 --> 00:18:18.644 but do your best to understand what00:18:18.644 --> 00:18:21.613 the pull request was on so that00:18:21.613 --> 00:18:24.709 when you do get asked about it,00:18:24.710 --> 00:18:27.370 you can answer with a PM that00:18:27.370 --> 00:18:29.070 should be deployed to QA.00:18:29.070 --> 00:18:30.340 It was on this PR.00:18:30.340 --> 00:18:31.550 They did a deployment recently.00:18:33.730 --> 00:18:35.980 Does anyone have any questions about00:18:35.980 --> 00:18:38.304 updating the UM, Azure tickets and00:18:38.304 --> 00:18:40.692 the whole kind of process there?00:18:40.700 --> 00:18:43.423 I've got like a hotfix ticket that00:18:43.423 --> 00:18:45.869 doesn't have like a state thing to00:18:45.869 --> 00:18:48.718 it is that is that what you meant by.00:18:48.720 --> 00:18:49.986 Like sometimes you can't know if00:18:49.986 --> 00:18:51.616 it's in code, complete or not.00:18:51.616 --> 00:18:53.600 Or yeah, let's check it. A look.00:18:53.600 --> 00:18:56.867 OK, so I think I moved it to the00:18:56.867 --> 00:18:59.528 ER created already right here.00:18:59.528 --> 00:19:01.761 Yeah, yeah, so there's no state for00:19:01.761 --> 00:19:03.860 that though, right? Got it so yeah,00:19:03.860 --> 00:19:08.640 this was QA failed originally.00:19:08.640 --> 00:19:11.776 In development, when it was inactive and00:19:11.776 --> 00:19:15.668 then is it pending a PR right now, yes,00:19:15.668 --> 00:19:18.664 I think actually it's it's done now.00:19:18.670 --> 00:19:20.230 I guess I got both cripples.00:19:20.230 --> 00:19:23.350 So OK, cool just happened.00:19:23.350 --> 00:19:26.257 Juno UM and you can do you wanna just00:19:26.257 --> 00:19:28.818 quick drop that uh PR and chat here00:19:28.818 --> 00:19:31.629 let me take a look at it no problem.00:19:31.630 --> 00:19:35.238 'cause I honestly don't know if I come.00:19:35.240 --> 00:19:40.900 If a QA is on a CICD branch or not,00:19:40.900 --> 00:19:42.070 or if it needs to be built.00:19:45.920 --> 00:19:46.350 See.00:20:03.500 --> 00:20:06.218 I just posted it, I think.00:20:06.220 --> 00:20:08.980 Yes, check it out.00:20:08.980 --> 00:20:11.290 Cool, so you posted it.00:20:11.290 --> 00:20:15.616 It got confirmed by James waiting for Jesse.00:20:15.616 --> 00:20:19.480 Yeah, I'm pretty sure I mean well,00:20:19.480 --> 00:20:21.790 he's the one that's been editing it,00:20:21.790 --> 00:20:23.414 so I'm pretty sure he'll approve it.00:20:23.420 --> 00:20:25.428 He probably just hasn't gotten to it yet,00:20:25.430 --> 00:20:29.035 but regardless, so. So this is very00:20:29.035 --> 00:20:34.950 firmly a PR created code complete. OK.00:20:34.950 --> 00:20:37.486 And then when that queue that PR goes00:20:37.486 --> 00:20:40.300 through, you know you'll find out.00:20:40.300 --> 00:20:44.580 You know, by asking essentially email. Yeah,00:20:44.580 --> 00:20:48.240 you'll also find out if it got built or not.00:20:48.240 --> 00:20:51.970 Oh, it did build it did build, yeah? OK.00:20:55.980 --> 00:20:57.756 I'm not sure why or how,00:20:57.760 --> 00:20:59.174 maybe just the front end got built.00:20:59.180 --> 00:21:02.362 Yeah, I don't think it got built yet. Or oh,00:21:02.362 --> 00:21:05.029 were you doing code changes directly to?00:21:05.030 --> 00:21:07.644 I think Jesse was. Yeah OK, OK,00:21:07.644 --> 00:21:09.436 so that'll be kind of a hanky one,00:21:09.440 --> 00:21:12.840 but we'll see if you do leave things in code,00:21:12.840 --> 00:21:15.498 complete one of two things happens.00:21:15.500 --> 00:21:17.636 Like I said, either PM bugs.00:21:17.640 --> 00:21:20.476 Yeah, until you can check or00:21:20.476 --> 00:21:22.252 someone goes and checks for you00:21:22.252 --> 00:21:24.257 and I'm going to check for you.00:21:24.260 --> 00:21:26.066 Does take a lot of time and00:21:26.066 --> 00:21:27.150 it's generally frowned upon.00:21:27.150 --> 00:21:29.950 So once everything is confirmed,00:21:29.950 --> 00:21:33.220 I should just go ahead and switch it to nqa.00:21:33.220 --> 00:21:35.000 It just deployed to QA,00:21:35.000 --> 00:21:36.432 deployed to QA OK.00:21:36.432 --> 00:21:37.506 Yeah so like,00:21:37.510 --> 00:21:38.896 let's say that this thing is here,00:21:38.900 --> 00:21:41.940 you know cart quick ad does not function.00:21:41.940 --> 00:21:43.536 You know if this is done,00:21:43.540 --> 00:21:45.416 just go to the site real quick.00:21:45.420 --> 00:21:46.964 Once the deployment happens00:21:46.964 --> 00:21:49.280 and make sure your works there.00:21:49.280 --> 00:21:50.726 Just a quick little call that00:21:50.726 --> 00:21:51.880 kind of like finishing up.00:21:51.880 --> 00:21:54.512 You can still put that in completed that's00:21:54.512 --> 00:21:56.400 still associated with the task itself,00:21:56.400 --> 00:21:58.304 but just do a quick round of QA00:21:58.304 --> 00:22:00.108 yourself just to make sure it's there.00:22:00.110 --> 00:22:02.987 It saves that 15 minutes of developer00:22:02.987 --> 00:22:04.640 quickly checking their work,00:22:04.640 --> 00:22:07.272 or five minutes of a developer quickly00:22:07.272 --> 00:22:09.932 checking their work can save a PM and00:22:09.932 --> 00:22:11.980 QA engineer upwards of like 2 hours.00:22:11.980 --> 00:22:13.890 OK, gotcha.00:22:13.890 --> 00:22:14.874 Thank you for asking.00:22:14.874 --> 00:22:16.726 So let's go into what he was00:22:16.726 --> 00:22:18.010 talking about earlier too,00:22:18.010 --> 00:22:23.280 with some development training that.00:22:23.280 --> 00:22:27.000 Wasn't, uh wasn't brought in here,00:22:27.000 --> 00:22:30.348 so you said you had some other stuff that00:22:30.348 --> 00:22:33.548 was not ticketed out for you right here.00:22:33.550 --> 00:22:35.842 Yeah, just like I mean few00:22:35.842 --> 00:22:37.370 random like miscellaneous things.00:22:37.370 --> 00:22:39.480 Nothing like.00:22:39.480 --> 00:22:42.255 It's just stuff that's like on my own.00:22:42.255 --> 00:22:45.305 Might like kind of like onboarding00:22:45.305 --> 00:22:47.780 certification course thing.00:22:47.780 --> 00:22:49.860 So like I owe like outside of this?00:22:49.860 --> 00:22:52.415 OK, that's just the full dev environmental00:22:52.420 --> 00:22:53.638 and it's just to react course OK?00:22:53.640 --> 00:22:54.282 Yeah, yeah,00:22:54.282 --> 00:22:56.850 so you can just say like you know.00:22:56.850 --> 00:22:59.874 Name it something similar like front end.00:22:59.880 --> 00:23:03.660 On boarding miscellaneous.00:23:03.660 --> 00:23:05.084 OK, so I can just make like a00:23:05.084 --> 00:23:06.269 bucket ticket for it essentially.00:23:06.270 --> 00:23:08.894 Yeah, you know if there's a few things00:23:08.894 --> 00:23:11.200 that kind of hit that same thing.00:23:11.200 --> 00:23:14.686 And it's about getting your time logged00:23:14.686 --> 00:23:18.119 and it doesn't have anything to do.00:23:18.120 --> 00:23:20.312 Specifically with like the00:23:20.312 --> 00:23:22.504 development of a feature.00:23:22.510 --> 00:23:24.880 You know?00:23:24.880 --> 00:23:25.458 You know,00:23:25.458 --> 00:23:27.192 the only time we really want00:23:27.192 --> 00:23:28.978 to really be tracking a task.00:23:28.980 --> 00:23:32.370 With very specific stuff is if00:23:32.370 --> 00:23:34.740 it's explicitly helping the00:23:34.740 --> 00:23:38.340 completion of a user story level.00:23:38.340 --> 00:23:40.489 So user story level is a bug.00:23:40.490 --> 00:23:43.980 User story, plan, documentation, etc.00:23:43.980 --> 00:23:45.261 But let's say.00:23:45.261 --> 00:23:47.823 If it had anything to do00:23:47.823 --> 00:23:50.100 with this specific bug,00:23:50.100 --> 00:23:52.728 you'd want to put that task on this one,00:23:52.730 --> 00:23:53.984 but if it's just kind of00:23:53.984 --> 00:23:54.820 like a general thing,00:23:54.820 --> 00:23:57.340 like I said with this dev training,00:23:57.340 --> 00:23:58.576 it's just it's we just want00:23:58.576 --> 00:23:59.400 to track that time.00:23:59.400 --> 00:24:01.780 So at the end of the Sprint,00:24:01.780 --> 00:24:04.780 PS aren't looking at devs and going like.00:24:04.780 --> 00:24:07.868 At least half 30 hours in the Sprint.00:24:07.870 --> 00:24:09.767 You're four days behind what's going on.00:24:09.770 --> 00:24:12.429 It's like, well, you know I am four00:24:12.429 --> 00:24:14.067 days behind what we originally planned,00:24:14.070 --> 00:24:16.170 but stuff comes up.00:24:16.170 --> 00:24:17.724 And if we know what it is,00:24:17.730 --> 00:24:19.340 we can plan for it ongoing rather00:24:19.340 --> 00:24:20.734 than just kind of waiting for00:24:20.734 --> 00:24:22.246 the end of the Sprint like OK,00:24:22.250 --> 00:24:23.756 So what did you actually do?00:24:27.270 --> 00:24:30.126 OK, perfect gotcha then so I can just00:24:30.126 --> 00:24:32.921 and should I just change the completed00:24:32.921 --> 00:24:35.753 to like whatever amount of hours I've00:24:35.753 --> 00:24:38.729 done and like not touch original or OK?00:24:38.730 --> 00:24:40.224 Yeah, this fully unplanned so we00:24:40.224 --> 00:24:41.922 don't know what we don't know what00:24:41.922 --> 00:24:44.374 to do with that perfect. Thanks man.00:24:44.374 --> 00:24:47.165 So yeah. So again just in general00:24:47.165 --> 00:24:49.320 updating tickets as they're going along,00:24:49.320 --> 00:24:51.390 putting them in active column as00:24:51.390 --> 00:24:54.200 you're doing them, updating EP with00:24:54.200 --> 00:24:58.330 your active time logs as you're going,00:24:58.330 --> 00:25:02.446 and that's really that. I'm cool,00:25:02.446 --> 00:25:07.200 so does anyone have any questions and if not,00:25:07.200 --> 00:25:09.020 let's just quick do a little kind00:25:09.020 --> 00:25:12.408 of going over session here.00:25:12.410 --> 00:25:15.094 Any questions Nate Dara.00:25:15.094 --> 00:25:18.339 Albert silent. None for me.00:25:18.340 --> 00:25:20.640 Think so cool, cool, cool.00:25:20.640 --> 00:25:23.376 So again, if you don't have any tickets00:25:23.376 --> 00:25:25.778 that are pertinent to your work,00:25:25.780 --> 00:25:27.850 you gotta ask for them.00:25:27.850 --> 00:25:29.362 Or make them yourself.00:25:29.362 --> 00:25:30.496 Both are fine.00:25:30.500 --> 00:25:32.354 I prefer you to ask for them as kind00:25:32.354 --> 00:25:34.477 of like the first step and then if00:25:34.477 --> 00:25:36.068 you're not getting what you need.00:25:36.070 --> 00:25:38.310 Reach out to me and we can get them for you.00:25:38.310 --> 00:25:40.086 And if they can't do it then feel00:25:40.086 --> 00:25:41.888 free to just make them yourself.00:25:41.890 --> 00:25:42.970 So let's just take a look.00:25:42.970 --> 00:25:44.554 So if we're looking at this right now.00:25:47.480 --> 00:25:48.820 What I do is alphabetically.00:25:48.820 --> 00:25:51.102 Brent 4235, Brett.00:25:51.102 --> 00:25:53.750 Do you just need to update your tickets00:25:53.814 --> 00:25:56.217 right now or is there work that we need00:25:56.217 --> 00:25:58.967 to get in here that wasn't on the Sprint?00:25:58.970 --> 00:26:03.299 Uhm, I think I I updated it this morning.00:26:03.300 --> 00:26:07.765 It was I originally had it as a TV to00:26:07.765 --> 00:26:10.390 be allocated OK, and then I changed00:26:10.390 --> 00:26:13.107 it this morning to the correct.00:26:13.110 --> 00:26:15.805 Ticket so it should be on there,00:26:15.810 --> 00:26:17.847 but I might have to double check.00:26:17.850 --> 00:26:20.022 Yeah 'cause I'm just saying it00:26:20.022 --> 00:26:23.818 about 7 hours behind, but 34 + 41.00:26:23.818 --> 00:26:28.170 It should be about 41.00:26:28.170 --> 00:26:29.994 So we're gonna take a look at EP.00:26:43.550 --> 00:26:45.098 29 to 222.00:26:50.560 --> 00:26:54.790 OK, and we have 28.5 there.00:26:54.790 --> 00:26:59.790 Billable let's go on over here.00:26:59.790 --> 00:27:00.986 And that matches up,00:27:00.986 --> 00:27:02.780 so you're burning up is matching00:27:02.841 --> 00:27:06.428 perfectly about you know less 1/4 hour,00:27:06.430 --> 00:27:08.670 so you're all cool and we just00:27:08.670 --> 00:27:10.870 have that 6.5 of overages.00:27:10.870 --> 00:27:13.990 Which we probably need to get00:27:13.990 --> 00:27:16.439 removed from your burndown,00:27:16.440 --> 00:27:18.699 but we saw you at about 6 hours behind,00:27:18.700 --> 00:27:22.996 which would be about 1 full day behind.00:27:23.000 --> 00:27:25.456 So what we'll need to do there is,00:27:25.460 --> 00:27:26.620 we need to move.00:27:29.200 --> 00:27:32.400 6.5 hours out 7.5 'cause I just put00:27:32.400 --> 00:27:33.758 a whole another one in here for you.00:27:36.910 --> 00:27:38.149 So we're just gonna have to scan00:27:38.149 --> 00:27:39.209 through and we have to find.00:27:39.210 --> 00:27:41.594 One thing I think I'll have to tell00:27:41.594 --> 00:27:44.090 Ben that this is getting kicked out.00:27:44.090 --> 00:27:45.110 And that's just kind of00:27:45.110 --> 00:27:45.926 how the process works.00:27:45.930 --> 00:27:47.390 Then I would go in.00:27:47.390 --> 00:27:48.640 I'd have to ask Ben.00:27:53.900 --> 00:27:56.220 Cool and this constant constant00:27:56.220 --> 00:27:57.148 constant communication.00:27:59.630 --> 00:28:01.345 OK guys, so if you have any00:28:01.345 --> 00:28:02.591 other questions about this please00:28:02.591 --> 00:28:04.187 feel free to hit me up again.00:28:04.190 --> 00:28:06.078 We just want to make sure that you're00:28:06.078 --> 00:28:07.784 not too stressed out about everything00:28:07.784 --> 00:28:09.848 in the Sprint if things go over00:28:09.848 --> 00:28:11.549 or people throw new work at you.00:28:11.550 --> 00:28:14.070 This is just to help us plan better.00:28:14.070 --> 00:28:17.507 So never be shy about this stuff.00:28:17.510 --> 00:28:18.548 Feel free to hit it up.00:28:18.550 --> 00:28:20.782 It's incredible boon to the whole00:28:20.782 --> 00:28:23.559 team if we have better planning.00:28:23.560 --> 00:28:24.463 Cool thank y'all.00:28:24.463 --> 00:28:25.667 Have a good day.