00:00:07.020 --> 00:00:09.160 Let's get into it.00:00:09.160 --> 00:00:14.159 Uhm, so in a kind of in a in a single word,00:00:14.160 --> 00:00:16.904 and this is a lifted directly from00:00:16.904 --> 00:00:19.710 Stephanie Azure is the developers plate.00:00:19.710 --> 00:00:22.335 This is what you guys have going00:00:22.335 --> 00:00:25.169 on in any particular Sprint.00:00:25.170 --> 00:00:27.474 This is the work you're expected to do.00:00:27.480 --> 00:00:30.600 This is the work that we're expecting to00:00:30.600 --> 00:00:33.218 be completed at the end of two weeks.00:00:33.220 --> 00:00:36.020 Now. With that being said,00:00:36.020 --> 00:00:38.939 you guys all do have a handful.00:00:38.940 --> 00:00:41.396 Of kind of odd aberrations in the like00:00:41.396 --> 00:00:44.060 and we'll get into those in a in a touch.00:00:44.060 --> 00:00:48.968 So if we're just looking at Azure as a whole.00:00:48.970 --> 00:00:52.558 Essentially exists on two different levels.00:00:52.560 --> 00:00:53.772 So I'm gonna just quick do00:00:53.772 --> 00:00:55.070 a little bit of creating.00:00:55.070 --> 00:00:57.600 Yeah, OK.00:00:57.600 --> 00:00:59.992 And it will be the task level which00:00:59.992 --> 00:01:02.518 are which is anything in these three00:01:02.518 --> 00:01:04.740 columns here and the user story level,00:01:04.740 --> 00:01:06.294 which is anything in this column here.00:01:06.300 --> 00:01:09.036 Now you will see that there are a handful00:01:09.036 --> 00:01:12.461 of different types of user story level items,00:01:12.461 --> 00:01:15.566 these ones which are meetings.00:01:15.570 --> 00:01:17.940 Maybe I should have a smaller00:01:17.940 --> 00:01:19.520 view rather than everybody.00:01:19.520 --> 00:01:21.510 Let's find some real work.00:01:21.510 --> 00:01:25.030 Here we go and then we'll have bugs.00:01:25.030 --> 00:01:27.798 User stories and that should be the bulk00:01:27.798 --> 00:01:30.879 of them are either bugs or user stories.00:01:30.880 --> 00:01:34.453 So we are going to kind of get into00:01:34.453 --> 00:01:37.075 this a touch so the very bottom,00:01:37.075 --> 00:01:38.200 bottom, bottom line,00:01:38.200 --> 00:01:41.488 base kind of competency on this is when00:01:41.488 --> 00:01:45.140 you start on a task you should be able to.00:01:45.140 --> 00:01:46.175 Either into it.00:01:46.175 --> 00:01:48.590 What you need to do within the00:01:48.672 --> 00:01:50.547 task by clicking into it.00:01:50.550 --> 00:01:53.496 And seeing what's in the description00:01:53.500 --> 00:01:56.010 if the description is lacking,00:01:56.010 --> 00:01:57.634 do check out the user story level,00:01:57.640 --> 00:01:59.509 which you'll find a link to right00:01:59.509 --> 00:02:01.526 here and see if there's all the00:02:01.526 --> 00:02:03.100 information laid out in there.00:02:03.100 --> 00:02:05.152 If you do not understand what00:02:05.152 --> 00:02:07.958 you are to do based on the task00:02:07.960 --> 00:02:11.638 that will follow up to the.00:02:11.640 --> 00:02:12.192 Project manager,00:02:12.192 --> 00:02:14.400 so let's say you go here and you00:02:14.465 --> 00:02:16.157 don't have enough information.00:02:16.160 --> 00:02:17.756 You click into the user story.00:02:17.760 --> 00:02:19.540 Still not enough information.00:02:19.540 --> 00:02:22.721 You are more than welcome to talk00:02:22.721 --> 00:02:25.289 to the project manager right away.00:02:25.290 --> 00:02:28.610 Not more than welcome encouraged you should00:02:28.610 --> 00:02:31.560 come, but let's see, OK, so we're here.00:02:31.560 --> 00:02:33.440 We have our tasks.00:02:33.440 --> 00:02:35.260 Updating them is relatively simple,00:02:35.260 --> 00:02:37.500 so as soon as you start a task,00:02:37.500 --> 00:02:39.600 whether this is something you're going OK,00:02:39.600 --> 00:02:40.780 cool, I'm sorry 6078.00:02:40.780 --> 00:02:42.550 You want to drag it over00:02:42.620 --> 00:02:43.968 to the active column.00:02:46.180 --> 00:02:47.839 That way we know that you are00:02:47.839 --> 00:02:49.019 starting to work on that,00:02:49.020 --> 00:02:50.840 and then as you're finishing,00:02:50.840 --> 00:02:52.044 or as you're working on the task,00:02:52.050 --> 00:02:53.170 you don't have to do this hour00:02:53.170 --> 00:02:54.440 by hour or anything like that.00:02:54.440 --> 00:02:57.014 But let's say that you put in a good00:02:57.014 --> 00:02:59.188 three hours on this task before00:02:59.188 --> 00:03:01.340 you start moving to another one.00:03:01.340 --> 00:03:03.587 You will change the remaining down to00:03:03.587 --> 00:03:06.134 what was left or what was reduced from00:03:06.134 --> 00:03:09.488 here and increase into the completed sign.00:03:09.490 --> 00:03:11.930 Real straightforward.00:03:11.930 --> 00:03:15.368 This will decrease your burndown here,00:03:15.370 --> 00:03:17.575 and this will give us an idea of how00:03:17.575 --> 00:03:20.016 the work is going in the Sprint. Now,00:03:20.016 --> 00:03:23.760 let's say that you spent three hours on this.00:03:23.760 --> 00:03:24.620 And that does it.00:03:24.620 --> 00:03:25.695 There's a 10 hour task,00:03:25.700 --> 00:03:27.457 but you did it in three hours.00:03:27.460 --> 00:03:28.360 That's great.00:03:28.360 --> 00:03:31.060 What you'll do is you'll drag00:03:31.060 --> 00:03:33.728 it over to the closed line.00:03:33.730 --> 00:03:36.610 And then you'll update the user story level.00:03:36.610 --> 00:03:38.794 So let's say this was one task00:03:38.794 --> 00:03:40.719 to A1 user story level.00:03:40.720 --> 00:03:42.864 You can go into that user story itself.00:03:46.160 --> 00:03:47.695 Change the state and let's00:03:47.695 --> 00:03:49.690 go to an actual user story.00:03:49.690 --> 00:03:50.946 For this I'm gonna use one of mine.00:03:57.400 --> 00:03:58.793 So that's it, say this one here00:03:58.793 --> 00:04:00.319 will say this just broke clean up.00:04:00.320 --> 00:04:02.876 Let's say Eric close this task all the way.00:04:02.880 --> 00:04:05.652 You wanna change that state to a00:04:05.652 --> 00:04:08.919 state that is pertinent to that task?00:04:08.920 --> 00:04:11.566 Now you also want to change the state when00:04:11.566 --> 00:04:14.098 you are moving into development on it,00:04:14.100 --> 00:04:15.420 so I guess this is kind00:04:15.420 --> 00:04:16.680 of a double sided thing,00:04:16.680 --> 00:04:18.584 so as soon as it's in development,00:04:18.590 --> 00:04:20.258 meaning that you're working on it,00:04:20.260 --> 00:04:23.020 you wanna change this tag right00:04:23.020 --> 00:04:24.860 here to end development.00:04:24.860 --> 00:04:26.340 Let's say that you have00:04:26.340 --> 00:04:27.820 completed the work on it,00:04:27.820 --> 00:04:30.340 but it's not pushed to any00:04:30.340 --> 00:04:31.600 specific environment yet.00:04:31.600 --> 00:04:34.936 You'll want to change that to code complete.00:04:34.940 --> 00:04:38.398 Once it is deployed to an environment,00:04:38.400 --> 00:04:41.760 whatever environment that may be and it00:04:41.760 --> 00:04:45.540 is ready or sorry when it's deployed,00:04:45.540 --> 00:04:47.094 we'll be going to deploy to QA.00:04:49.130 --> 00:04:51.402 Or every practice can be a little bit00:04:51.402 --> 00:04:53.034 different, so I don't want to get00:04:53.034 --> 00:04:54.719 too bogged down with entity gritty,00:04:54.720 --> 00:04:58.725 but you'll want to either do deploy to QA.00:04:58.730 --> 00:05:00.950 Or UAT, etc down the line.00:05:00.950 --> 00:05:04.830 Let's say that you have your code complete,00:05:04.830 --> 00:05:07.680 but it is not deployed.00:05:07.680 --> 00:05:08.912 You'll do code complete00:05:08.912 --> 00:05:10.452 once it's in code complete.00:05:10.460 --> 00:05:12.980 That kind of will fall back to the00:05:12.980 --> 00:05:15.300 project managers and what they will do is00:05:15.300 --> 00:05:17.529 go through the code completes and make00:05:17.529 --> 00:05:20.035 sure that things are getting pushed up.00:05:20.040 --> 00:05:24.960 That is, only if you do not have the, uh.00:05:24.960 --> 00:05:29.657 Ability to do that push to deployment.00:05:29.660 --> 00:05:30.682 So I'm gonna put this in development00:05:30.682 --> 00:05:33.640 and put it back where it goes, OK?00:05:33.640 --> 00:05:34.852 Further things,00:05:34.852 --> 00:05:37.590 let's go into Clint meeting00:05:37.590 --> 00:05:38.970 Mike Clint meeting.00:05:38.970 --> 00:05:39.938 I'm messing with OK.00:05:43.060 --> 00:05:47.749 Let's say with this task. That you are.00:05:47.749 --> 00:05:51.432 Working on it and you want to00:05:51.432 --> 00:05:53.700 kind of keep people appraised of00:05:53.786 --> 00:05:55.759 what's going on and that you'll00:05:55.759 --> 00:05:57.074 just use the discussion here.00:05:57.080 --> 00:05:59.768 Feel free to add specific project00:05:59.768 --> 00:06:01.790 managers, specific developers.00:06:05.560 --> 00:06:07.012 Whatever it may be,00:06:07.012 --> 00:06:08.464 the more communication you00:06:08.464 --> 00:06:11.021 have on these Azure level, uh,00:06:11.021 --> 00:06:14.267 resources, the more historic it is.00:06:14.270 --> 00:06:15.578 This is also information you'll want00:06:15.578 --> 00:06:17.179 to bring up to the PM via chat.00:06:17.180 --> 00:06:18.790 Also information that you want00:06:18.790 --> 00:06:20.866 to bring into the teams channel00:06:20.866 --> 00:06:22.486 for that specific project.00:06:22.490 --> 00:06:24.835 If you put it into the teams00:06:24.835 --> 00:06:26.460 channel that is enough,00:06:26.460 --> 00:06:27.797 but it's just gonna be quick thing00:06:27.797 --> 00:06:29.196 and you just want a quick side00:06:29.196 --> 00:06:30.600 chat the PM and it's something that00:06:30.600 --> 00:06:31.916 you just need a quick answer on.00:06:31.920 --> 00:06:32.880 That's one thing.00:06:32.880 --> 00:06:34.480 Anything larger you want to00:06:34.480 --> 00:06:36.209 bring into the teams channel.00:06:36.210 --> 00:06:37.587 So this is all kind of the basic stuff.00:06:37.590 --> 00:06:39.286 I'm sure you guys did all this in00:06:39.286 --> 00:06:42.208 the Azure training, is that correct?00:06:42.210 --> 00:06:43.221 Yes, OK cool,00:06:43.221 --> 00:06:45.580 I wanna just quick hit high level00:06:45.658 --> 00:06:47.680 stuff there but then let's get00:06:47.680 --> 00:06:50.040 into some of the nitty gritty.00:06:50.040 --> 00:06:52.386 OK, so we have our tasks.00:06:52.390 --> 00:06:54.710 We have our completed all that good stuff.00:06:54.710 --> 00:06:57.307 We wanna make sure it's on you.00:06:57.310 --> 00:06:59.602 Uhm few kind of best practices00:06:59.602 --> 00:07:02.551 as you'll want to kind of get00:07:02.551 --> 00:07:04.327 comfortable with this view.00:07:04.330 --> 00:07:06.245 Each developer has a specific00:07:06.245 --> 00:07:08.968 way they like to look at this.00:07:08.968 --> 00:07:11.392 The task Board of course is00:07:11.392 --> 00:07:13.370 the most popular one.00:07:13.370 --> 00:07:15.450 Uh, it's the cleanest one.00:07:15.450 --> 00:07:17.750 Everything like that you00:07:17.750 --> 00:07:20.625 have this filter up here.00:07:20.630 --> 00:07:22.597 Which you can get really granular with.00:07:25.870 --> 00:07:27.364 This one here. Of course you00:07:27.364 --> 00:07:28.850 can search by specific products,00:07:28.850 --> 00:07:30.692 projects or you can just bring00:07:30.692 --> 00:07:32.590 it down here to yourself.00:07:32.590 --> 00:07:34.438 Let's just go with Justin here.00:07:37.440 --> 00:07:40.464 And this will just show your specific00:07:40.464 --> 00:07:42.115 projects, your specific tasks,00:07:42.115 --> 00:07:44.545 everything you have on your plate.00:07:44.550 --> 00:07:46.454 This is the view I would suggest00:07:46.454 --> 00:07:48.300 for you guys to use the most.00:07:48.300 --> 00:07:50.574 Uhm, you can also let me00:07:50.574 --> 00:07:53.299 quick see how we can do this.00:07:53.300 --> 00:07:56.780 You can add different columns.00:07:56.780 --> 00:07:58.845 Uhm, and in these columns you can00:07:58.845 --> 00:08:00.659 name them specific things and you00:08:00.659 --> 00:08:02.682 can change pieces for what you want.00:08:05.720 --> 00:08:07.364 Like I said that get some00:08:07.364 --> 00:08:08.460 kind of configuration stuff.00:08:08.460 --> 00:08:10.086 You guys will kind of figure00:08:10.086 --> 00:08:11.779 out your workflow as things go.00:08:11.780 --> 00:08:15.137 This bar here of course is visible in here.00:08:15.140 --> 00:08:16.800 The planning one is outlining00:08:16.800 --> 00:08:18.128 all the next Sprint,00:08:18.130 --> 00:08:19.327 so you guys won't really use this.00:08:19.330 --> 00:08:21.580 That kind of falls that00:08:21.580 --> 00:08:23.830 falls fully on the PM.00:08:23.830 --> 00:08:26.908 So let's get into kind of what I track,00:08:26.910 --> 00:08:28.848 so you'll hear us talk about,00:08:28.850 --> 00:08:30.166 burn down, you'll hear us talk about,00:08:30.170 --> 00:08:34.146 burn up, and all of those good things.00:08:34.150 --> 00:08:36.450 The bottom line there is,00:08:36.450 --> 00:08:39.404 you guys are of course assigned a00:08:39.404 --> 00:08:42.300 specific amount of time in the Sprint.00:08:42.300 --> 00:08:43.532 Which generally equates to00:08:43.532 --> 00:08:45.072 about 7 hours a day.00:08:45.080 --> 00:08:46.940 Well, 7 hours a day exactly,00:08:46.940 --> 00:08:49.467 unless you have any sort of special00:08:49.467 --> 00:08:51.260 a consideration with management00:08:51.260 --> 00:08:53.136 and or if you're taking time off.00:08:53.140 --> 00:08:55.186 Of course you won't be expected00:08:55.186 --> 00:08:56.980 to work on those days.00:08:56.980 --> 00:08:59.752 What you will want to do throughout the day,00:08:59.760 --> 00:09:01.790 as you're updating tickets is00:09:01.790 --> 00:09:03.820 being incredibly honest about the00:09:03.892 --> 00:09:06.084 work that's going on in this task.00:09:06.084 --> 00:09:08.772 So let's say that Justin on this00:09:08.772 --> 00:09:11.300 task here and project meetings.00:09:11.300 --> 00:09:12.770 He only has one hour.00:09:12.770 --> 00:09:13.044 Uh,00:09:13.044 --> 00:09:14.688 assigned here and it should say00:09:14.688 --> 00:09:16.508 in here one hour for course.00:09:16.510 --> 00:09:18.456 Stand up now.00:09:18.456 --> 00:09:18.922 Justin,00:09:18.922 --> 00:09:21.718 from my understanding is you have00:09:21.718 --> 00:09:25.250 a bid meeting later today as well.00:09:25.250 --> 00:09:27.602 And I don't think that you have00:09:27.602 --> 00:09:29.090 a task for that.00:09:29.090 --> 00:09:32.838 So for you guys.00:09:32.840 --> 00:09:35.396 You are more than welcome to00:09:35.396 --> 00:09:38.129 create tasks for yourself if it's00:09:38.129 --> 00:09:40.021 something additional you worked00:09:40.021 --> 00:09:44.490 on so and we will reflect on that.00:09:44.490 --> 00:09:44.844 Uhm,00:09:44.844 --> 00:09:46.968 you also are more than welcome00:09:46.968 --> 00:09:49.180 to just continue to add stuff00:09:49.180 --> 00:09:50.620 to the completed column.00:09:50.620 --> 00:09:52.810 These what we would call exceeding00:09:52.810 --> 00:09:54.616 estimates and this information gets00:09:54.616 --> 00:09:56.344 tracked by me every single day,00:09:56.350 --> 00:09:59.296 sometimes multiple times throughout the day.00:09:59.300 --> 00:10:00.640 One thing to think about,00:10:00.640 --> 00:10:02.960 or one kind of small thing is if00:10:02.960 --> 00:10:05.318 you guys have a balancing ticket,00:10:05.320 --> 00:10:07.820 do not touch that one.00:10:07.820 --> 00:10:08.800 Don't change the remaining.00:10:08.800 --> 00:10:09.780 Don't change the completed.00:10:09.780 --> 00:10:11.820 I go through and I clean those up.00:10:11.820 --> 00:10:14.460 It's better practice to add00:10:14.460 --> 00:10:16.044 tickets yourself so.00:10:16.050 --> 00:10:18.800 We are trying to streamline00:10:18.800 --> 00:10:21.550 kind of the general UM.00:10:21.550 --> 00:10:23.514 Ticket situation because as00:10:23.514 --> 00:10:26.460 there are more than 800 tip,00:10:26.460 --> 00:10:28.304 well there's 800 tickets00:10:28.304 --> 00:10:30.609 in this Sprint right now.00:10:30.610 --> 00:10:32.274 If it gets to be more than 1000,00:10:32.280 --> 00:10:35.416 we cannot view anything in the Sprint.00:10:35.420 --> 00:10:38.507 So if you do have additional things,00:10:38.510 --> 00:10:41.597 and in this case we know that00:10:41.597 --> 00:10:44.309 Justin has another meeting today.00:10:44.310 --> 00:10:45.670 I believe it's a one hour bid meeting,00:10:45.670 --> 00:10:46.339 is that correct?00:10:50.300 --> 00:10:53.117 Uh, yes it is a one hour bid meeting.00:10:53.120 --> 00:10:56.774 I believe it's actually on tomorrow though.00:10:56.780 --> 00:10:57.656 Even better, even better,00:10:57.656 --> 00:10:59.340 so we can get ahead of this so00:10:59.340 --> 00:11:00.996 he can either do two things.00:11:01.000 --> 00:11:02.854 He can either let me know ahead of time00:11:02.854 --> 00:11:04.596 and we can get stuff moved in here.00:11:04.600 --> 00:11:06.358 That's of course the best option.00:11:06.360 --> 00:11:08.820 The more information we have relating00:11:08.820 --> 00:11:11.020 to things before they happen,00:11:11.020 --> 00:11:12.700 it's it's easier 'cause we can just click00:11:12.700 --> 00:11:14.596 do it and it's got 2 hours of meeting.00:11:14.600 --> 00:11:16.196 So much change that remaining to two.00:11:16.200 --> 00:11:17.994 I'm gonna leave the original estimate00:11:17.994 --> 00:11:20.347 exactly where it is because we want that.00:11:20.350 --> 00:11:23.190 To be kind of a historical view of what we00:11:23.266 --> 00:11:26.245 thought this was going to be in this Sprint.00:11:26.250 --> 00:11:28.418 This helps us reflex and learn on what00:11:28.418 --> 00:11:30.487 happened in the Sprint and next Sprint.00:11:30.490 --> 00:11:32.170 So he has two hours of meetings.00:11:32.170 --> 00:11:35.274 So far. We're gonna change that to two.00:11:35.280 --> 00:11:36.657 In this case, he would either holler at me.00:11:36.660 --> 00:11:37.188 Hey Daniel,00:11:37.188 --> 00:11:39.036 I have another hour of project meetings.00:11:39.040 --> 00:11:40.456 I added that to the remaining.00:11:40.460 --> 00:11:42.910 I can then go in and change.00:11:42.910 --> 00:11:45.088 His Sprint balancing.00:11:45.090 --> 00:11:48.348 Now let's say he doesn't have00:11:48.348 --> 00:11:49.434 Sprint balancing.00:11:49.440 --> 00:11:52.674 OK, we still want this information tracked,00:11:52.680 --> 00:11:55.165 so you'll still want to change that00:11:55.165 --> 00:11:57.236 remaining 'cause this is planned work right?00:11:57.240 --> 00:11:58.940 That big meeting is planned.00:11:58.940 --> 00:12:00.280 We know it's coming up.00:12:00.280 --> 00:12:03.416 It wasn't accounted for in your Sprint,00:12:03.420 --> 00:12:05.988 but we need to know what's gonna happen.00:12:05.990 --> 00:12:09.320 So as this time goes down, you will00:12:09.320 --> 00:12:11.495 have what's called exceeding estimates.00:12:11.500 --> 00:12:13.702 So conceding estimates is anytime either00:12:13.702 --> 00:12:16.000 the remaining work changes on a task for.00:12:16.000 --> 00:12:17.143 In this case,00:12:17.143 --> 00:12:19.336 we'll say project meetings, uhm?00:12:19.336 --> 00:12:21.334 Quick stand ups.00:12:21.334 --> 00:12:23.998 Anything that's client related.00:12:24.000 --> 00:12:25.614 You'll change that remaining or just00:12:25.614 --> 00:12:28.099 add it to the completed after the fact.00:12:28.100 --> 00:12:30.620 So let's say that end of day tomorrow00:12:30.620 --> 00:12:34.378 Justin has his bid meeting and00:12:34.378 --> 00:12:36.574 his core stamps will say that's00:12:36.574 --> 00:12:38.545 all done and that's two.00:12:38.545 --> 00:12:41.035 This task has now exceeded estimates,00:12:41.040 --> 00:12:42.840 and that's.00:12:42.840 --> 00:12:43.258 Not I,00:12:43.258 --> 00:12:45.479 I don't want to say it's not on you guys,00:12:45.480 --> 00:12:48.896 but ultimately it's not on you guys.00:12:48.900 --> 00:12:51.300 If it is a meeting ticket,00:12:51.300 --> 00:12:53.638 that's something that we PM's have caused.00:12:53.640 --> 00:12:56.800 Most likely if it is related to development,00:12:56.800 --> 00:12:58.336 we'll get into that in just a second,00:12:58.340 --> 00:12:59.214 but anything,00:12:59.214 --> 00:13:01.836 anytime anything is exceeded as them,00:13:01.840 --> 00:13:04.520 it's all we need to do is make sure that00:13:04.594 --> 00:13:07.546 completed is accurate to what you have done.00:13:07.550 --> 00:13:09.500 Let me take you into my sheet for a second00:13:09.553 --> 00:13:11.362 to kind of show you how this plays out.00:13:15.280 --> 00:13:15.570 OK.00:13:18.350 --> 00:13:21.059 So on my sheet I track a bunch of00:13:21.059 --> 00:13:22.652 different stuff. We'll see here.00:13:22.652 --> 00:13:24.236 This is just that basic burn00:13:24.236 --> 00:13:25.846 down day after day after day.00:13:25.850 --> 00:13:28.250 So if you guys aren't regularly00:13:28.250 --> 00:13:29.823 updating your tickets, UM,00:13:29.823 --> 00:13:32.061 like I think we've told your00:13:32.061 --> 00:13:33.950 handful of times thus far,00:13:33.950 --> 00:13:34.960 we're not gonna be tracking.00:13:34.960 --> 00:13:36.038 We're gonna be tracking guys through hard,00:13:36.040 --> 00:13:36.929 but we're not gonna be coming down00:13:36.929 --> 00:13:37.890 on you or anything like that.00:13:37.890 --> 00:13:39.821 It's just to kind of keep00:13:39.821 --> 00:13:43.076 things normal across the board.00:13:43.080 --> 00:13:44.802 Uhm, we'll be tracking that day after00:13:44.802 --> 00:13:46.681 day and this is gonna be the total00:13:46.681 --> 00:13:48.209 amount of work left in the day,00:13:48.210 --> 00:13:49.554 and the total amount of work00:13:49.554 --> 00:13:50.450 where we should be.00:13:50.450 --> 00:13:54.180 Is they able to show us kind of a bell curve?00:13:54.180 --> 00:13:58.056 Over here we check blocked time and we'll00:13:58.056 --> 00:14:00.120 get into that in a second with tasks.00:14:00.120 --> 00:14:02.485 We tracked the block tickets00:14:02.485 --> 00:14:04.850 that are specifically a done.00:14:04.850 --> 00:14:06.390 This is our meeting column.00:14:06.390 --> 00:14:08.934 This is for reflecting on any of the00:14:08.934 --> 00:14:11.108 meetings like I just did with Justin,00:14:11.110 --> 00:14:13.230 and this exceeded estimates column.00:14:13.230 --> 00:14:15.186 So right now we have Alex.00:14:15.190 --> 00:14:17.478 He has exceeded estimates too and hey Alex,00:14:17.480 --> 00:14:17.788 well,00:14:17.788 --> 00:14:19.636 let's get into your business specifically.00:14:19.640 --> 00:14:21.416 This would be nice,00:14:21.416 --> 00:14:23.345 so we have exceeded estimates we00:14:23.345 --> 00:14:24.578 have exceeded estimates, projects.00:14:24.578 --> 00:14:26.268 We have a balanced task.00:14:26.270 --> 00:14:27.950 We have a removed column.00:14:27.950 --> 00:14:30.650 This is if I remove time from your Sprint.00:14:30.650 --> 00:14:31.774 Altogether, UM,00:14:31.774 --> 00:14:35.708 and then we have our added time.00:14:35.710 --> 00:14:38.188 So if we're looking at exceeded estimates00:14:38.190 --> 00:14:39.408 and we're looking at Alex here.00:14:52.190 --> 00:14:55.070 OK so I can go over here and we can00:14:55.161 --> 00:14:58.377 quick see what tasks Alex went over on.00:15:02.720 --> 00:15:04.862 So there's a camp ticket to the00:15:04.862 --> 00:15:07.978 tune of six hours, so I'll slide00:15:07.978 --> 00:15:10.700 that over here. Camping here.00:15:13.070 --> 00:15:14.645 And we're gonna take a look at his balance.00:15:14.650 --> 00:15:17.842 So he has right now some extra time00:15:17.842 --> 00:15:20.470 related to just unplanned work.00:15:20.470 --> 00:15:21.220 It's unplanned work.00:15:21.220 --> 00:15:23.450 We have extra time in his Sprint for this.00:15:23.450 --> 00:15:25.406 We know everything is gonna happen,00:15:25.410 --> 00:15:27.090 but we still have this one camp00:15:27.090 --> 00:15:28.889 task that has exceeded estimates.00:15:28.890 --> 00:15:30.402 In this case I'm just going00:15:30.402 --> 00:15:31.760 to do some right here.00:15:31.760 --> 00:15:34.536 He's gonna be fine and his Sprint is00:15:34.536 --> 00:15:37.709 going to reflect the actual work he did.00:15:37.710 --> 00:15:39.509 Now, let's say he didn't have this,00:15:39.510 --> 00:15:43.084 and he's just six hours over my role in00:15:43.084 --> 00:15:45.388 that point is going to step in and try00:15:45.388 --> 00:15:47.708 and move out additional work for you guys.00:15:47.710 --> 00:15:50.218 So you guys heard us talking00:15:50.218 --> 00:15:51.472 about that yesterday.00:15:51.480 --> 00:15:54.366 Or sorry Tuesday long day yesterday.00:15:54.370 --> 00:15:56.130 UM where we are going to be a00:15:56.130 --> 00:15:58.088 bit more aggressive on any tasks00:15:58.088 --> 00:15:59.540 that did exceed estimates,00:15:59.540 --> 00:16:01.904 we're gonna be attempting to move00:16:01.904 --> 00:16:04.190 workout to make weight for that.00:16:04.190 --> 00:16:06.752 Now there is a secondary piece on00:16:06.752 --> 00:16:09.327 that and this is gonna be pretty00:16:09.327 --> 00:16:12.229 reliant on you guys as new dudes as00:16:12.229 --> 00:16:14.729 you guys are kind of getting ramped00:16:14.729 --> 00:16:16.763 up as you're getting comfortable with00:16:16.763 --> 00:16:19.224 a lot of items you might go over00:16:19.224 --> 00:16:21.499 a couple hours on a couple tasks.00:16:21.500 --> 00:16:22.880 And when I come through,00:16:22.880 --> 00:16:24.040 you might say, like, oh,00:16:24.040 --> 00:16:28.065 I worked later come into the night.00:16:28.070 --> 00:16:29.974 And you know, I did go long,00:16:29.980 --> 00:16:31.231 but I ended up doing like 12 hour day00:16:31.231 --> 00:16:32.666 for it to make sure it got done whatever.00:16:32.670 --> 00:16:34.890 Whatever your whatever your00:16:34.890 --> 00:16:37.364 Steves maybe if that's the case,00:16:37.364 --> 00:16:39.069 I'm still gonna remove tasks.00:16:39.070 --> 00:16:40.659 But what will need from you guys00:16:40.659 --> 00:16:42.848 is to be really communicative about00:16:42.850 --> 00:16:45.586 when you're running low on work.00:16:47.680 --> 00:16:49.545 OK, so with exceeding estimates00:16:49.545 --> 00:16:51.780 the second thing that I just00:16:51.780 --> 00:16:53.859 want to make sure is almost a.00:16:56.900 --> 00:16:59.276 Word for it shouted from the00:16:59.276 --> 00:17:00.860 rooftops more than anything.00:17:00.860 --> 00:17:02.295 So if we're looking down these tasks,00:17:02.300 --> 00:17:03.596 we have a few of these have gone over.00:17:03.600 --> 00:17:05.100 So for this task here,00:17:05.100 --> 00:17:10.358 Alex 77908 at that .5 hour over.00:17:10.360 --> 00:17:12.948 Is that task complete?00:17:12.950 --> 00:17:15.746 Yeah, I'm just waiting on a PR. Oh cool.00:17:15.746 --> 00:17:18.707 OK, so let's put this in development.00:17:18.710 --> 00:17:20.490 Will say actually code complete.00:17:20.490 --> 00:17:23.986 Are you waiting for the PR to resolve?00:17:23.990 --> 00:17:26.206 Uh, I think I have a merge conflict.00:17:26.210 --> 00:17:28.073 Oh yeah. OK.00:17:28.073 --> 00:17:31.178 So the code is complete,00:17:31.180 --> 00:17:32.164 but you're going to have to00:17:32.164 --> 00:17:33.070 do some cleanup on there.00:17:37.580 --> 00:17:39.460 Take a look at what's going on yet.00:17:39.460 --> 00:17:42.360 Prove the poll request.00:17:42.360 --> 00:17:46.500 Oh OK, I'll let you get into that later,00:17:46.500 --> 00:17:48.628 UM, but we're gonna keep that inactive00:17:48.628 --> 00:17:50.676 then we're gonna still leave it as00:17:50.676 --> 00:17:52.673 code complete even though he is gonna00:17:52.673 --> 00:17:54.482 clean up that merge conflict anytime00:17:54.482 --> 00:17:56.418 that you have a task that goes over.00:17:56.420 --> 00:17:58.016 You do have to make sure that00:17:58.016 --> 00:17:59.399 the developer or the PM knows.00:17:59.400 --> 00:18:02.250 So for these camp tickets Alex,00:18:02.250 --> 00:18:03.800 we just it's all camp.00:18:03.800 --> 00:18:05.270 I'm sure Stephanie knows about it, right?00:18:08.140 --> 00:18:11.611 Uhm, I believe so. OK cool.00:18:11.611 --> 00:18:13.237 The biggest thing you guys might00:18:13.237 --> 00:18:15.021 do is specially is your new and00:18:15.021 --> 00:18:16.401 kind of getting used to stuff.00:18:16.410 --> 00:18:18.321 If you get to about the halfway00:18:18.321 --> 00:18:20.158 mark on any of these tasks,00:18:20.160 --> 00:18:23.920 just holler at the PM if you're at.00:18:23.920 --> 00:18:25.936 1/2 hour and you're like there's no way I'm00:18:25.936 --> 00:18:27.766 gonna finish this in another 30 minutes.00:18:27.770 --> 00:18:29.658 Let us know as you guys are new,00:18:29.660 --> 00:18:30.368 we're gonna be.00:18:30.368 --> 00:18:31.548 There's a lot more leeway00:18:31.548 --> 00:18:32.770 for those kind of things.00:18:32.770 --> 00:18:35.250 It's just more important for us to know.00:18:35.250 --> 00:18:37.074 OK, so exceeding estimates.00:18:37.074 --> 00:18:38.898 We're moving estimates from00:18:38.898 --> 00:18:41.468 balance or removing tickets from a00:18:41.470 --> 00:18:42.856 Sprint's based on what's going on.00:18:45.020 --> 00:18:48.580 OK, and then this column here is burned00:18:48.580 --> 00:18:52.958 up so we have burned down over here and00:18:52.958 --> 00:18:56.584 this is just the work that's happening.00:18:56.590 --> 00:18:59.128 Or that was planned in Sprint.00:18:59.130 --> 00:19:02.642 Now we know for a fact now that00:19:02.642 --> 00:19:06.158 I remove that balance from Alex.00:19:06.160 --> 00:19:10.356 From Alex is a balance ticket and you'll00:19:10.356 --> 00:19:13.212 see that it does ultimately kind of00:19:13.212 --> 00:19:16.788 hurt the burn up rate because we're just00:19:16.788 --> 00:19:19.717 removing time based on what was worked.00:19:19.720 --> 00:19:21.052 So we have the six hours00:19:21.052 --> 00:19:21.718 of exceeding estimates.00:19:21.720 --> 00:19:22.976 Or maybe this just needs to be refreshed.00:19:22.980 --> 00:19:26.535 Part of me before I say anything like that.00:19:26.540 --> 00:19:28.290 And all of this is just working00:19:28.290 --> 00:19:30.040 off of data that's in Azure.00:19:30.040 --> 00:19:33.370 I have a just an integration into Excel here.00:20:01.500 --> 00:20:06.288 OK. That should just populate up in00:20:06.288 --> 00:20:09.300 here for the completed work, yeah?00:20:12.100 --> 00:20:14.930 OK. So we have six hours.00:20:14.930 --> 00:20:16.890 We're down one and then here we have00:20:16.890 --> 00:20:19.009 him 10 hours off because we did do00:20:19.009 --> 00:20:21.290 that change for the RE estimates.00:20:21.290 --> 00:20:22.620 Actually something sinkey here, huh?00:20:38.890 --> 00:20:41.095 It'd be already removed that three hours.00:20:48.550 --> 00:20:50.909 That was OK. I'll do it against00:20:50.909 --> 00:20:53.540 this and see why the work is off.00:20:53.540 --> 00:20:56.123 But you really would like by the end of00:20:56.123 --> 00:20:59.060 the Sprint for these numbers to match.00:20:59.060 --> 00:21:02.452 You would really want your burn up to00:21:02.452 --> 00:21:06.139 match your burn down as close as possible.00:21:06.140 --> 00:21:07.756 If they aren't a one to one match,00:21:07.760 --> 00:21:10.135 it either means you went00:21:10.135 --> 00:21:12.035 over on tasks significantly,00:21:12.040 --> 00:21:15.015 which would cause your completed work to00:21:15.015 --> 00:21:17.979 be very different than your burned down,00:21:17.980 --> 00:21:20.580 and that might not necessarily00:21:20.580 --> 00:21:22.660 be your fault specifically,00:21:22.660 --> 00:21:23.756 and it might be that you guys got.00:21:23.760 --> 00:21:26.105 Pulled in a lot of different directions00:21:26.105 --> 00:21:28.131 on different tasks that weren't planned00:21:28.131 --> 00:21:31.670 out ahead of time, and that's OK.00:21:31.670 --> 00:21:34.260 That's a perfectly understandable thing,00:21:34.260 --> 00:21:35.660 and as long as we know about it,00:21:35.660 --> 00:21:36.155 like I say,00:21:36.155 --> 00:21:37.310 you'll hear me say this 35 times00:21:37.349 --> 00:21:38.399 as long as we know about it,00:21:38.400 --> 00:21:39.310 we can reflect for it.00:21:42.340 --> 00:21:44.068 Like I said, the goal is gonna be to00:21:44.068 --> 00:21:45.997 move out tasks as they're coming through.00:21:46.000 --> 00:21:49.654 So you guys don't have to worry about that.00:21:49.660 --> 00:21:51.949 OK, so that's kind of the crux00:21:51.949 --> 00:21:54.582 of a lot of it here. Does anyone00:21:54.582 --> 00:21:56.187 have any questions about anything?00:21:58.320 --> 00:22:00.768 Yes, just so that I'm understanding00:22:00.768 --> 00:22:03.215 the burned out burned down so00:22:03.215 --> 00:22:05.508 burned down is the estimated hours00:22:05.508 --> 00:22:07.639 for this print, correct, correct?00:22:07.639 --> 00:22:10.012 And the burn up is basically the00:22:10.012 --> 00:22:12.798 hours that you have to take away from00:22:12.798 --> 00:22:14.646 other projects because of exceeding00:22:14.646 --> 00:22:17.342 hours on the estimated spirits, right?00:22:17.342 --> 00:22:19.897 Kind of kind of yeah.00:22:19.900 --> 00:22:23.158 So burned down is the plan to work right?00:22:23.160 --> 00:22:27.219 Burned out like I said in a perfect world.00:22:27.220 --> 00:22:29.284 And it's going to kind of seem kind00:22:29.284 --> 00:22:31.601 of odd with your guys tasks as you00:22:31.601 --> 00:22:33.929 have them right now because there are.00:22:33.930 --> 00:22:38.580 A fair amount of, uh?00:22:38.580 --> 00:22:40.302 The Sprint balancing tasks for you00:22:40.302 --> 00:22:42.260 guys right now they're a little weird,00:22:42.260 --> 00:22:45.860 but in an ideal world.00:22:45.860 --> 00:22:47.834 You guys would start your Sprint with00:22:47.834 --> 00:22:50.016 the 70 hours of work you would work00:22:50.016 --> 00:22:51.768 those those specific 70 hours and00:22:51.768 --> 00:22:53.578 there would be nothing different.00:22:53.580 --> 00:22:55.820 The burn up is just the realistic00:22:55.820 --> 00:22:57.790 view of what's actually done.00:22:59.820 --> 00:23:00.270 OK.00:23:04.830 --> 00:23:07.020 I have a question regarding mine00:23:07.020 --> 00:23:08.308 specifically. Yeah, so how?00:23:08.308 --> 00:23:10.450 How was I six hours over 'cause00:23:10.526 --> 00:23:12.446 I'm looking at my camp tickets00:23:12.446 --> 00:23:14.888 and I'm only two hours over here.00:23:14.890 --> 00:23:16.366 Interesting, let's see what's going on.00:23:16.370 --> 00:23:18.075 Maybe there's something wrong with00:23:18.075 --> 00:23:20.614 my math and that would actually make00:23:20.614 --> 00:23:22.539 the three hour difference here.00:23:22.540 --> 00:23:23.626 Make more sense.00:23:23.626 --> 00:23:25.436 So let's see what's happening.00:23:25.440 --> 00:23:26.124 Maybe there's something wrong00:23:26.124 --> 00:23:26.808 with the pivot table.00:23:31.290 --> 00:23:33.100 Yeah, actually.00:23:40.290 --> 00:23:43.888 What's going on? Let's see what's happening.00:23:46.610 --> 00:23:47.500 You know what it was, Alex.00:23:47.500 --> 00:23:48.800 I'm seeing it right now.00:23:48.800 --> 00:23:51.038 Six was the total of time,00:23:51.040 --> 00:23:52.515 not the total of over. Just.00:23:52.515 --> 00:23:54.034 There's nothing wrong with my, uh,00:23:54.034 --> 00:23:55.498 some wrong with my pivot table.00:23:55.500 --> 00:23:56.940 I just had to reconfigure it,00:23:56.940 --> 00:23:59.496 so that's 100% on me. So it is 3.00:23:59.496 --> 00:24:01.590 We'll move that balance up to 12.5.00:24:03.840 --> 00:24:04.880 And yeah, now you're straight.00:24:04.880 --> 00:24:09.400 There we go. What's up, OK?00:24:09.400 --> 00:24:10.180 Let's see what's going00:24:10.180 --> 00:24:11.155 on with that pivot table.00:24:11.160 --> 00:24:12.050 I'll get into that later.00:24:20.050 --> 00:24:22.306 Cool, does anyone else have any00:24:22.306 --> 00:24:23.810 other questions about anything?00:24:23.810 --> 00:24:26.785 Yeah, I got one more so regarding utashe.00:24:26.785 --> 00:24:29.035 You said there are times that00:24:29.035 --> 00:24:31.466 we might have to create a task.00:24:31.470 --> 00:24:33.519 Great question, yeah.00:24:36.220 --> 00:24:37.880 Basically, for what I'm00:24:37.880 --> 00:24:38.710 understanding incorrectly,00:24:38.710 --> 00:24:40.300 correct me if I'm misunderstanding.00:24:40.300 --> 00:24:42.022 Basically, we would need a task00:24:42.022 --> 00:24:43.836 for almost every little thing that00:24:43.836 --> 00:24:45.678 we're doing that's at least billable00:24:45.678 --> 00:24:47.357 and meeting included like internal00:24:47.357 --> 00:24:50.430 meetings and all that, right?00:24:50.430 --> 00:24:55.126 Any client related stuff will need a task,00:24:55.130 --> 00:25:00.754 and in this case core is a client.00:25:00.760 --> 00:25:02.690 Uhm, Jeremy I believe are00:25:02.690 --> 00:25:04.234 you gonna be working?00:25:04.240 --> 00:25:06.376 Connect at all I'm I talked to Eric00:25:06.376 --> 00:25:08.429 and I'm supposed to be but I have00:25:08.429 --> 00:25:10.458 a lot of core stuff right now.00:25:10.460 --> 00:25:14.196 OK, so cores the client connects the client,00:25:14.200 --> 00:25:15.940 the HIPAA portals, the client.00:25:15.940 --> 00:25:18.140 There's a handful of internal00:25:18.140 --> 00:25:19.900 projects that are technically00:25:19.900 --> 00:25:21.656 clients as we look at them,00:25:21.660 --> 00:25:23.770 which will require tickets but00:25:23.770 --> 00:25:26.230 internal meetings so like stand ups.00:25:29.220 --> 00:25:32.034 One on ones this kind of work.00:25:32.040 --> 00:25:34.218 This won't necessarily need a ticket,00:25:34.220 --> 00:25:35.060 but for you guys today.00:25:35.060 --> 00:25:36.604 For this I'm just going to solve y'all00:25:36.604 --> 00:25:38.160 all of y'all's balancing tickets.00:25:38.160 --> 00:25:42.390 Buy one before it. OK.00:25:42.390 --> 00:25:44.486 OK, so question related to that then yeah,00:25:44.490 --> 00:25:47.476 I uh, I met with Eric. Uh Brandon,00:25:47.476 --> 00:25:50.717 for like an hour regarding a ticket,00:25:50.720 --> 00:25:51.450 should I put that in?00:25:51.450 --> 00:25:53.530 Then I put an hour into that ticket.00:25:53.530 --> 00:25:55.290 Then that's a great question.00:25:55.290 --> 00:25:56.580 Yes, OK?00:25:58.730 --> 00:26:00.719 Yeah, you'll want to put that into that task.00:26:00.720 --> 00:26:02.280 Any work you're doing relating00:26:02.280 --> 00:26:04.442 to a task will wanna get you00:26:04.442 --> 00:26:06.050 wanna log it to the ticket?00:26:06.050 --> 00:26:09.400 OK, perfect. Where is beating?00:26:09.400 --> 00:26:12.525 Communicating with the PM, whatever it is,00:26:12.525 --> 00:26:15.015 that's all timed to that ticket.00:26:15.020 --> 00:26:20.009 Act as far as like. He broke here.00:26:20.010 --> 00:26:21.503 But your little quiet there, sorry.00:26:21.503 --> 00:26:22.568 Can you hear me now?00:26:22.570 --> 00:26:24.682 Yeah, there it is.00:26:24.682 --> 00:26:26.370 Sorry that counts for them, right?00:26:26.370 --> 00:26:27.912 If they are in like paired00:26:27.912 --> 00:26:28.940 programming sessions and they're00:26:28.986 --> 00:26:30.246 working on a specific ticket.00:26:32.470 --> 00:26:34.960 And that's something you guys will00:26:34.960 --> 00:26:37.250 wanna be pretty cognizant of guys.00:26:37.250 --> 00:26:39.798 And like I said right now these00:26:39.798 --> 00:26:43.330 first few weeks. Not a huge uh.00:26:43.330 --> 00:26:46.120 Not a huge deal and I actually.00:26:46.120 --> 00:26:49.040 I don't want to say I huge deal, not a deal.00:26:49.040 --> 00:26:51.000 Just something to keep in mind and00:26:51.063 --> 00:26:53.351 maybe you wanna make it like a good00:26:53.351 --> 00:26:55.505 spending on how you guys are as like.00:26:55.510 --> 00:26:56.020 Learners like me,00:26:56.020 --> 00:26:57.699 I'm a kind of person like I want to00:26:57.699 --> 00:26:58.809 take things seriously right away.00:26:58.810 --> 00:27:00.142 'cause if I don't then I'm00:27:00.142 --> 00:27:01.410 like I'll develop bad habits.00:27:01.410 --> 00:27:02.682 But everyone is a little different00:27:02.682 --> 00:27:04.092 and I'm not one to prescribe00:27:04.092 --> 00:27:07.550 those things to other people, but.00:27:07.550 --> 00:27:09.678 We'll want to make sure that in any00:27:09.678 --> 00:27:11.830 kind of paired programming thing,00:27:11.830 --> 00:27:13.762 anything along those lines,00:27:13.762 --> 00:27:15.694 any meeting you're in.00:27:15.700 --> 00:27:18.485 You wanna be super cognizant00:27:18.485 --> 00:27:21.270 of yourself in that meeting.00:27:21.270 --> 00:27:23.222 See you guys go to a paired programming00:27:23.222 --> 00:27:24.579 session and they're working on00:27:24.579 --> 00:27:26.490 something that you have no context on.00:27:26.490 --> 00:27:30.109 You're not really there for for anything,00:27:30.110 --> 00:27:31.405 you're just gonna brought in 'cause like,00:27:31.410 --> 00:27:32.730 Oh yeah, you know I'm new.00:27:32.730 --> 00:27:34.470 They invited me to this thing00:27:34.470 --> 00:27:36.030 I wanna be part of it.00:27:36.030 --> 00:27:38.412 If it's something that you aren't00:27:38.412 --> 00:27:40.835 getting value out of you won't00:27:40.835 --> 00:27:43.097 wanna just sit around in there.00:27:43.100 --> 00:27:43.835 Because your time,00:27:43.835 --> 00:27:46.120 unless you want to work it longer in the day,00:27:46.120 --> 00:27:46.584 that's up to you.00:27:46.584 --> 00:27:47.280 At the end of the day,00:27:47.280 --> 00:27:48.755 and especially as your training00:27:48.755 --> 00:27:49.935 that might be necessary.00:27:49.940 --> 00:27:51.620 But once you guys kind of get more00:27:51.620 --> 00:27:53.399 ramped up on projects and are cruising00:27:53.399 --> 00:27:55.250 along on things you really want to00:27:55.250 --> 00:27:56.708 make sure that you're getting the00:27:56.708 --> 00:27:58.330 work that was assigned to you done.00:28:03.010 --> 00:28:03.688 That makes sense.00:28:07.200 --> 00:28:10.240 Daniel, I guess I had one question too.00:28:10.240 --> 00:28:13.168 Like for this instance I knew.00:28:13.170 --> 00:28:15.546 I know that I have a balancing ticket00:28:15.546 --> 00:28:17.766 and when like that bid meeting came00:28:17.766 --> 00:28:19.921 up so we increased it an hour and00:28:19.921 --> 00:28:21.818 then took that off the balancing.00:28:21.820 --> 00:28:23.809 But as I move along and say I didn't00:28:23.809 --> 00:28:25.298 have that balancing that would00:28:25.298 --> 00:28:27.110 be an instance where I message00:28:27.171 --> 00:28:28.900 you and let you know about that.00:28:28.900 --> 00:28:30.856 Our meeting that came up that00:28:30.856 --> 00:28:32.160 wasn't originally planned for00:28:32.223 --> 00:28:33.939 at the beginning of the Sprint,00:28:33.940 --> 00:28:37.772 100 percent, 100% and also guys00:28:37.772 --> 00:28:40.330 feel free to push back on PMS.00:28:40.330 --> 00:28:42.689 Not just me, but your individual PM's00:28:42.689 --> 00:28:44.748 for those individual projects as well.00:28:44.750 --> 00:28:47.006 'cause let's say that they wanna00:28:47.006 --> 00:28:49.380 pull you aside to start working on00:28:49.380 --> 00:28:51.410 a task that is for the project.00:28:51.410 --> 00:28:53.962 But let's say you have a task that00:28:53.962 --> 00:28:56.379 is about like hooking up an API.00:28:56.380 --> 00:28:57.820 Like oh while you're in that real quick,00:28:57.820 --> 00:29:00.010 can you?00:29:00.010 --> 00:29:02.530 Also, you know, I mean this is.00:29:02.530 --> 00:29:04.084 This would be a pretty drastic thing,00:29:04.090 --> 00:29:05.210 but could you also update00:29:05.210 --> 00:29:06.106 the schema you know?00:29:06.110 --> 00:29:06.476 But like,00:29:06.476 --> 00:29:07.757 let's say whatever it is they're asking00:29:07.757 --> 00:29:09.085 for the kind of another quick thing.00:29:09.090 --> 00:29:11.202 It was something that you think you can00:29:11.202 --> 00:29:13.229 accomplish in that same amount on the task.00:29:13.230 --> 00:29:14.211 Go for it.00:29:14.211 --> 00:29:15.519 Use your best discretion.00:29:15.520 --> 00:29:17.344 But do remember at the end of the00:29:17.344 --> 00:29:19.042 day you guys are held responsible00:29:19.042 --> 00:29:20.522 for this work in here.00:29:20.530 --> 00:29:23.575 So the closer you Hugh to what is00:29:23.575 --> 00:29:26.270 actually on the board to what you're00:29:26.270 --> 00:29:27.780 doing it, the better you'll do.00:29:30.150 --> 00:29:30.620 OK.00:29:34.530 --> 00:29:37.242 And every single PM in this00:29:37.242 --> 00:29:39.050 company has been told.00:29:39.050 --> 00:29:41.250 At least once? Yeah, totally.00:29:41.250 --> 00:29:42.444 I can told you that just00:29:42.444 --> 00:29:43.640 quick make me a ticket.00:29:43.640 --> 00:29:44.912 So you won't be like the00:29:44.912 --> 00:29:46.000 first person was like man,00:29:46.000 --> 00:29:47.476 these new guys are stuck up.00:29:47.480 --> 00:29:49.336 You said Daniel told me to do it.00:29:49.340 --> 00:29:52.653 They told me if if you know he's judging me00:29:52.653 --> 00:29:55.422 every week and I'm working on all this other00:29:55.422 --> 00:29:57.774 side stuff and it's not getting tracked.00:29:57.780 --> 00:29:59.220 You know, like you guys,00:29:59.220 --> 00:30:01.050 gotta make sure that you guys00:30:01.050 --> 00:30:02.940 are safe on your side too.00:30:02.940 --> 00:30:03.972 Absolutely cool. Yeah,00:30:03.972 --> 00:30:07.620 I've had to do that with my previous project,00:30:07.620 --> 00:30:08.568 which is actually.00:30:08.568 --> 00:30:10.880 So yeah, I know I don't feel well,00:30:10.880 --> 00:30:13.496 yeah yeah it's not cool and you know00:30:13.496 --> 00:30:16.139 I will say completely earnestly.00:30:16.140 --> 00:30:18.709 No ones ever doing it out of00:30:18.709 --> 00:30:20.250 any malice or any.00:30:20.250 --> 00:30:22.105 It's just the common strive00:30:22.105 --> 00:30:24.716 to get things done now, like.00:30:24.716 --> 00:30:28.360 With that being said, you know,00:30:28.360 --> 00:30:31.790 let's say you guys are going like.00:30:31.790 --> 00:30:34.107 So you're hustling on one specific project,00:30:34.110 --> 00:30:35.734 and you have a handful of other projects00:30:35.734 --> 00:30:37.468 that are kind of like in the background.00:30:37.470 --> 00:30:39.367 That's really when I come into play,00:30:39.370 --> 00:30:41.664 so you can just straight up say like a,00:30:41.664 --> 00:30:43.068 you know, include me and the00:30:43.068 --> 00:30:44.650 PM who were involved in it.00:30:44.650 --> 00:30:45.216 Like, hey,00:30:45.216 --> 00:30:45.782 you know,00:30:45.782 --> 00:30:47.480 I went along on Clint project00:30:47.546 --> 00:30:49.112 for three hours because we had00:30:49.112 --> 00:30:51.009 to do this push to production.00:30:51.010 --> 00:30:52.768 I'm over by three hours on00:30:52.768 --> 00:30:53.647 my exceeding estimates,00:30:53.650 --> 00:30:55.816 and I think that this this00:30:55.816 --> 00:30:57.660 ticket from Daniels project can00:30:57.660 --> 00:30:59.280 get moved to next Sprint.00:30:59.280 --> 00:31:01.247 I don't believe it's a high priority.00:31:01.250 --> 00:31:02.160 Those kind of things are00:31:02.160 --> 00:31:03.070 more insight you guys happen.00:31:18.480 --> 00:31:21.890 Hello. Hey can you go see me?00:31:21.890 --> 00:31:24.490 You think Daniels make cut00:31:24.490 --> 00:31:26.440 out or something? Yeah.00:31:36.360 --> 00:31:37.890 Daniel, can you hear us?00:31:40.910 --> 00:31:43.282 I can hear you guys. Hey guys, no,00:31:43.282 --> 00:31:45.340 I think my my teams crashed there.00:31:45.340 --> 00:31:48.166 How y'all done OK? What, what?00:31:48.166 --> 00:31:50.112 What did I get dropped off on?00:31:56.610 --> 00:31:58.280 You were talking about the.00:32:01.550 --> 00:32:06.740 Pulling you in. That's what we did.00:32:06.740 --> 00:32:10.886 Basically contacting you about about a.00:32:10.890 --> 00:32:13.070 The project, yeah yeah yeah.00:32:13.070 --> 00:32:15.806 Telling the project manager and uh,00:32:15.810 --> 00:32:18.198 knowing like everything you have on00:32:18.198 --> 00:32:21.028 your plate you know is an incredibly00:32:21.030 --> 00:32:24.168 important thing to have going on.00:32:24.170 --> 00:32:27.395 And I really suggest you know honestly, even00:32:27.395 --> 00:32:30.570 doing like a daily like if I were you guys,00:32:30.570 --> 00:32:32.982 the very first thing I would do is just00:32:32.982 --> 00:32:35.639 take a look at everything you got going on.00:32:35.640 --> 00:32:38.392 You know, OK, cool, I got these two00:32:38.392 --> 00:32:41.006 projects which let's put those back there.00:32:41.010 --> 00:32:42.693 Getting a good luck just kind of going down,00:32:42.700 --> 00:32:43.870 just checking out all your tickets.00:32:43.870 --> 00:32:45.694 You know making sure you're paying00:32:45.694 --> 00:32:46.910 attention to those priorities,00:32:46.910 --> 00:32:50.414 seeing what you need to do per day.00:32:50.420 --> 00:32:51.818 Daniel, are you meaning to be,00:32:51.820 --> 00:32:53.880 UM, not sharing your screen?00:32:53.880 --> 00:32:56.220 No, I'm not. Thank you.00:32:56.220 --> 00:32:57.956 Yeah, no problem. Thank you thank you.00:32:57.960 --> 00:33:02.750 OK, so yeah, yeah right.00:33:02.750 --> 00:33:04.454 So kind of going through and00:33:04.454 --> 00:33:05.922 just making sure like, OK, cool,00:33:05.922 --> 00:33:06.918 I got these things you know,00:33:06.920 --> 00:33:09.083 OK, I got these couple of high00:33:09.083 --> 00:33:10.010 priority tasks here.00:33:10.010 --> 00:33:12.810 I'll probably get those knocked out today.00:33:12.810 --> 00:33:13.806 Kind of going down the line,00:33:13.810 --> 00:33:15.160 just making sure you understand00:33:15.160 --> 00:33:16.510 everything that's happening like oh,00:33:16.510 --> 00:33:18.410 I've got that big meeting00:33:18.410 --> 00:33:19.930 on Thursday or Friday.00:33:19.930 --> 00:33:21.856 Let me make sure that I.00:33:21.860 --> 00:33:23.912 Kind of get some questions about00:33:23.912 --> 00:33:24.938 these tasks right.00:33:24.940 --> 00:33:26.314 The more insight you guys have00:33:26.314 --> 00:33:27.420 into what your work is,00:33:27.420 --> 00:33:30.040 the more successful you'll be.00:33:30.040 --> 00:33:31.426 You know it's kind of looking00:33:31.426 --> 00:33:32.860 through and like you know what,00:33:32.860 --> 00:33:34.141 I always suggest,00:33:34.141 --> 00:33:34.568 UM,00:33:34.568 --> 00:33:37.130 for communication and for the sort00:33:37.210 --> 00:33:39.496 of like a broad work strategy,00:33:39.500 --> 00:33:41.844 here is it's really easy to get pulled00:33:41.844 --> 00:33:44.410 in these different directions so.00:33:47.010 --> 00:33:48.726 A couple different things about it,00:33:48.730 --> 00:33:50.971 and this is kind of what going away from00:33:50.971 --> 00:33:53.124 Azure and more to sort of work strategy00:33:53.124 --> 00:33:55.165 in general is call out a couple tasks at00:33:55.165 --> 00:33:58.680 the beginning of the day, right like?00:33:58.680 --> 00:34:00.017 You have to set up two locals,00:34:00.020 --> 00:34:01.868 Justin and I bet you probably don't00:34:01.868 --> 00:34:04.280 want to do both of those back to back,00:34:04.280 --> 00:34:06.464 but maybe you wanna set up your core00:34:06.464 --> 00:34:08.750 local and that'll take you know five hours00:34:08.750 --> 00:34:11.176 of the day and after you get set up,00:34:11.180 --> 00:34:12.612 let's do this ticket here, right?00:34:12.612 --> 00:34:13.700 Or this one typewriter.00:34:13.700 --> 00:34:17.064 So let's do this 74887 and you know I00:34:17.064 --> 00:34:18.469 don't think there's anything necessarily00:34:18.469 --> 00:34:20.471 wrong with kind of setting your sights a00:34:20.471 --> 00:34:22.436 little low 'cause it's a bit more realistic,00:34:22.440 --> 00:34:23.820 but cool, that's six hours.00:34:23.820 --> 00:34:25.340 I got 7 hours billable.00:34:25.340 --> 00:34:26.708 If those two things get done,00:34:26.710 --> 00:34:27.630 then maybe I'll start on00:34:27.630 --> 00:34:28.790 this next one down the line.00:34:28.790 --> 00:34:30.650 But I'm just gonna have a00:34:30.650 --> 00:34:31.580 full core day-to-day.00:34:31.580 --> 00:34:33.542 Getting these one kind of project00:34:33.542 --> 00:34:36.129 days for you to sort of cruising on00:34:36.129 --> 00:34:38.641 one project at a time per day will00:34:38.641 --> 00:34:40.874 get you guys a lot better results.00:34:40.880 --> 00:34:41.280 Uhm,00:34:41.280 --> 00:34:43.693 it will let the PM's know a00:34:43.693 --> 00:34:45.319 lot more explicitly what it is00:34:45.319 --> 00:34:47.442 you're working on and also it a.00:34:47.442 --> 00:34:49.869 It's just kind of better for the00:34:49.869 --> 00:34:52.379 development and deployment in general.00:34:55.970 --> 00:34:58.226 Hey Daniel, not to shift gears,00:34:58.230 --> 00:35:00.264 but I did just have one of the questions00:35:00.264 --> 00:35:02.396 that I wanted to ask and I think that what00:35:02.396 --> 00:35:04.449 you just said was really helpful, but.00:35:04.449 --> 00:35:06.822 If there's a user story and there's00:35:06.822 --> 00:35:08.877 three tasks for that user story,00:35:08.880 --> 00:35:11.200 and I move one to active, I changed,00:35:11.200 --> 00:35:13.440 I still change the whole user story00:35:13.440 --> 00:35:17.890 to in development, exactly OK.00:35:17.890 --> 00:35:20.690 Yeah, and this user story.00:35:20.690 --> 00:35:25.970 UM, management is incredibly helpful, UM.00:35:25.970 --> 00:35:28.672 I mean it's it's necessary and it's00:35:28.672 --> 00:35:30.398 something that you know we've just00:35:30.398 --> 00:35:32.354 started kind of paying a much closer eye00:35:32.354 --> 00:35:34.290 to the Sprint over the past few months.00:35:34.290 --> 00:35:35.991 I'm trying to get a bit more00:35:35.991 --> 00:35:37.533 integrity on there and you guys00:35:37.533 --> 00:35:39.304 will see in these next couple weeks.00:35:39.310 --> 00:35:42.895 Definitely by the end of Q4 that we're00:35:42.895 --> 00:35:45.015 gonna be doing logs on the user story00:35:45.015 --> 00:35:47.136 levels as well for everything that's new.00:35:50.060 --> 00:35:54.229 OK. In the case of where one user story has,00:35:54.230 --> 00:35:58.188 say, three tasks like I have 17615
00:35:58.188 --> 00:35:59.616 or five, that's the user story00:36:01.830 --> 00:36:03.535 76156706. Yeah, it's a user00:36:03.535 --> 00:36:06.070 story, then there's like.00:36:06.070 --> 00:36:07.610 If I'm reading it correctly,00:36:07.610 --> 00:36:10.378 I see we task related to that story.00:36:14.200 --> 00:36:15.568 773-827-7383 and 384.00:36:18.190 --> 00:36:19.880 Let's see, let's put it on bad boy, yeah.00:36:21.930 --> 00:36:23.590 Might just be best to00:36:23.590 --> 00:36:25.620 search the assign to, yeah?00:36:29.100 --> 00:36:32.978 OK, but it's this user story here.00:36:32.980 --> 00:36:38.228 Yeah, so basically. I see three tasks00:36:38.228 --> 00:36:41.350 for that in the new column, so.00:36:43.870 --> 00:36:47.284 If I'm working on one, say I complete00:36:47.284 --> 00:36:50.210 the code for one of those tasks.00:36:50.210 --> 00:36:52.432 How do I need to set up? Like?00:36:52.432 --> 00:36:53.944 Do I say it's in development00:36:53.944 --> 00:36:55.200 or code complete like how?00:36:55.200 --> 00:36:56.436 I guess? How does that statement?00:36:56.440 --> 00:36:57.490 Yeah, OK, cool.00:36:57.490 --> 00:36:59.940 So that's a great great great question.00:36:59.940 --> 00:37:02.524 So for 76156 as you guys can see00:37:02.524 --> 00:37:05.097 now Chris has these and I'm sorry.00:37:05.100 --> 00:37:07.350 Do you prefer Chris or Christopher?00:37:07.350 --> 00:37:08.430 Chris is fine, Chris.00:37:08.430 --> 00:37:12.760 OK, so Chris has these three tasks here.00:37:12.760 --> 00:37:15.080 Let's say that you do start with one,00:37:15.080 --> 00:37:17.180 you know, drag it over the active.00:37:17.180 --> 00:37:19.580 You know these two are in the hopper.00:37:19.580 --> 00:37:21.638 You won't do code complete until everything00:37:21.638 --> 00:37:23.810 on the user story is code complete.00:37:28.120 --> 00:37:29.030 Great question.00:37:31.210 --> 00:37:34.063 Now I would assume that would also be the.00:37:34.070 --> 00:37:37.388 Now what about for late in development?00:37:37.390 --> 00:37:38.554 In development, as soon as you're00:37:38.554 --> 00:37:39.919 starting to work on the user story,00:37:39.920 --> 00:37:42.260 it's in development. OK, cool.00:37:45.570 --> 00:37:47.327 Now there can be some hinky stuff00:37:47.327 --> 00:37:49.077 here and this is again when you00:37:49.077 --> 00:37:50.810 would just kind of flag me down.00:37:50.810 --> 00:37:53.690 Let's say that Chris is working00:37:53.690 --> 00:37:56.100 on this user story and.00:37:58.570 --> 00:38:00.264 Jeremy is working on this user story.00:38:00.270 --> 00:38:01.810 Chris is doing a front end piece,00:38:01.810 --> 00:38:03.274 you know and Jeremy is doing00:38:03.274 --> 00:38:04.639 a back end piece on it.00:38:04.640 --> 00:38:05.620 It's two tasks related00:38:05.620 --> 00:38:06.845 to the same user story.00:38:06.850 --> 00:38:09.118 You guys don't want to coordinate00:38:09.118 --> 00:38:11.940 with each other as much as possible.00:38:11.940 --> 00:38:13.540 To kind of make sure that your work00:38:13.540 --> 00:38:15.184 is getting synced up and your PR is00:38:15.184 --> 00:38:16.550 getting kind of close in together.00:38:16.550 --> 00:38:18.598 But once you do your PR for that00:38:18.598 --> 00:38:20.523 task you know it's still going00:38:20.523 --> 00:38:21.867 to be in development,00:38:21.870 --> 00:38:23.410 but you'll kind of want to just00:38:23.410 --> 00:38:25.680 do that like you know.00:38:25.680 --> 00:38:28.380 Saying goodbye on the way out.00:38:28.380 --> 00:38:31.656 Holler up in the user story like.00:38:31.660 --> 00:38:32.368 Go in there.00:38:34.630 --> 00:38:36.694 Oh, look at what a nice what a00:38:36.694 --> 00:38:38.509 nice seen sitting on a couch.00:38:38.510 --> 00:38:42.150 All these books you know, Paul.00:38:42.150 --> 00:38:45.810 Front end work complete.00:38:45.810 --> 00:38:46.558 And this, you know,00:38:46.558 --> 00:38:47.910 be more specific than front end work,00:38:47.910 --> 00:38:50.409 but you know, like you wanna make00:38:50.409 --> 00:38:52.389 sure everything about that task is,00:38:52.390 --> 00:38:53.659 uh, outlined there.00:38:56.200 --> 00:38:59.680 OK into that case.00:38:59.680 --> 00:39:01.620 So the way that obviously,00:39:01.620 --> 00:39:03.252 the way that I'm looking at my screen00:39:03.252 --> 00:39:05.014 right now is that I have it assigned to.00:39:05.020 --> 00:39:07.692 Every test is assigned to me, filtered at.00:39:07.692 --> 00:39:10.322 I had every test filter00:39:10.322 --> 00:39:12.600 that is assigned to me.00:39:12.600 --> 00:39:16.548 To know, let's just say 76156.00:39:16.548 --> 00:39:19.476 Let's just say Jeremy's got a.00:39:19.480 --> 00:39:21.280 You know, one task on that,00:39:21.280 --> 00:39:22.820 and to your point, how?00:39:22.820 --> 00:39:24.708 I guess what would you suggest that I00:39:24.708 --> 00:39:26.756 set this up to be able to tell when a00:39:26.756 --> 00:39:28.679 back end developer is working on that,00:39:28.680 --> 00:39:31.434 so that I don't put it to code complete00:39:31.440 --> 00:39:33.078 by accident when there's still more00:39:33.078 --> 00:39:35.000 tests being done for that user story?00:39:35.000 --> 00:39:35.946 Great question,00:39:35.946 --> 00:39:39.257 just clicking into the user story here.00:39:39.260 --> 00:39:40.590 So I'll just give you your view.00:39:44.480 --> 00:39:47.090 So let's say that we have00:39:47.090 --> 00:39:49.568 our our. Zero ten view here.00:39:57.100 --> 00:39:59.858 And we're looking at 76156
00:39:59.858 --> 00:40:01.170 with these three tasks.00:40:01.170 --> 00:40:02.752 And let's say that Chris falls finishes00:40:02.752 --> 00:40:04.388 all three of these are all closed.00:40:04.390 --> 00:40:06.514 He's like cool, my code is00:40:06.514 --> 00:40:08.342 complete on this before you00:40:08.342 --> 00:40:10.247 change it to code complete.00:40:10.250 --> 00:40:12.315 Uhm, just do a quick check in00:40:12.315 --> 00:40:14.179 here and you'll see all of00:40:14.179 --> 00:40:16.270 the children of that task. OK.00:40:21.020 --> 00:40:23.720 Alright cool, that makes sense.00:40:23.720 --> 00:40:25.568 And I want to give you guys another00:40:25.568 --> 00:40:27.318 edge case that totally can happen.00:40:27.320 --> 00:40:29.468 And this is another best practice.00:40:32.060 --> 00:40:33.890 Let's say I'm going to mess.00:40:33.890 --> 00:40:34.996 I don't want to mess with Stephanie.00:40:35.000 --> 00:40:35.900 I can mess with Stephanie stuff.00:40:35.900 --> 00:40:36.779 With some reason.00:40:36.779 --> 00:40:38.830 This says this is deployed to QA.00:40:41.310 --> 00:40:44.253 So let's go in here. Now. Let's say00:40:44.253 --> 00:40:48.688 that we had on this task. Make a menu.00:40:51.170 --> 00:40:53.580 And I had 12 hours.00:40:53.580 --> 00:40:55.620 On it, let's say you had that task00:40:55.620 --> 00:40:57.954 and you knew about that task and00:40:57.954 --> 00:40:59.714 you're working through that task.00:40:59.720 --> 00:41:00.640 And let's just say,00:41:00.640 --> 00:41:02.345 for instance, that this task,00:41:02.345 --> 00:41:05.839 even though it's 12 hours you look at it,00:41:05.840 --> 00:41:07.825 makes perfect sense to you're00:41:07.825 --> 00:41:09.810 able to crush through it.00:41:09.810 --> 00:41:12.463 The best practice can be on anything00:41:12.463 --> 00:41:14.648 that really is over 4 hours,00:41:14.650 --> 00:41:17.688 and ideally you guys will never get00:41:17.688 --> 00:41:20.947 a task that's more than four hours.00:41:20.950 --> 00:41:22.140 That's kind of the goal.00:41:22.140 --> 00:41:24.604 I mean, five is kind of OK00:41:24.604 --> 00:41:27.470 pushing it 4 is really the goal.00:41:27.470 --> 00:41:29.535 You guys are more than welcome to00:41:29.535 --> 00:41:31.568 hit this little green button here.00:41:31.570 --> 00:41:33.778 And you know, like.00:41:33.780 --> 00:41:35.826 Kind of outline the next kind00:41:35.826 --> 00:41:37.620 of couple steps of work.00:41:41.760 --> 00:41:44.032 For that piece and kind of break that00:41:44.032 --> 00:41:46.697 task out into smaller chunks for yourself.00:41:46.700 --> 00:41:48.980 So like cool, you know make a menu,00:41:48.980 --> 00:41:52.956 we'll just leave 9 hours in that still.00:41:52.960 --> 00:41:53.835 Actually, you never want to00:41:53.835 --> 00:41:54.535 change your original right?00:41:54.540 --> 00:41:55.770 And I leave the original,00:41:55.770 --> 00:41:58.930 but you know this is gonna take Me 2 hours.00:41:58.930 --> 00:42:01.828 And this is going to take me one hour.00:42:01.830 --> 00:42:03.366 I strongly suggest this00:42:03.366 --> 00:42:05.670 style of breaking out a task,00:42:05.670 --> 00:42:07.270 even if it's like a four hour 1,00:42:07.270 --> 00:42:08.365 but you can kind of say like, OK,00:42:08.365 --> 00:42:10.245 well I gotta make a schema for that.00:42:10.250 --> 00:42:12.242 And then I gotta hook up the front00:42:12.242 --> 00:42:14.350 end to that schema and then I wanna00:42:14.350 --> 00:42:16.102 make sure I have just like a good00:42:16.102 --> 00:42:17.904 like 45 minutes for QA or something00:42:17.904 --> 00:42:19.329 like that like whatever it is.00:42:19.330 --> 00:42:23.425 If it helps you guys get the job done.00:42:23.430 --> 00:42:25.230 More succinctly and kind of00:42:25.230 --> 00:42:26.670 keep yourself more organized,00:42:26.670 --> 00:42:28.060 we are all for it.00:42:30.950 --> 00:42:34.210 Remember this is your plate.00:42:34.210 --> 00:42:35.590 So in cases like that.00:42:37.620 --> 00:42:39.476 Should if we have to do that shaping00:42:39.476 --> 00:42:41.381 you or the project manager to let00:42:41.381 --> 00:42:43.213 them know that hey, you know we're00:42:43.213 --> 00:42:45.266 kind of dividing this up so that they00:42:45.266 --> 00:42:47.134 kind of understand what's going on.00:42:47.134 --> 00:42:49.194 Yeah yeah. Let the project00:42:49.194 --> 00:42:51.234 manager know anything with Azure.00:42:51.234 --> 00:42:53.442 Feel free to loop me in,00:42:53.450 --> 00:42:54.626 especially like any problems,00:42:54.626 --> 00:42:57.186 but you don't have to let me know if00:42:57.186 --> 00:42:58.908 it's like you just doing your thing00:42:58.964 --> 00:43:00.566 and you're kind of cruising along00:43:00.566 --> 00:43:02.852 and you guys are not less of a.00:43:02.852 --> 00:43:05.771 Less of a a babysitter on this more of00:43:05.771 --> 00:43:08.670 kind of just like a traffic cop, OK?00:43:22.890 --> 00:43:23.240 Cool.00:43:26.080 --> 00:43:29.237 Hey guys any any other questions or00:43:29.237 --> 00:43:32.081 anything like that? Quick go through.00:43:32.081 --> 00:43:34.566 And let's update some tasks.00:43:37.740 --> 00:43:38.850 OK, looks like guys been doing00:43:38.850 --> 00:43:40.080 a little bit of it already.00:43:40.080 --> 00:43:42.726 Beautiful, beautiful. I love to see it.00:43:44.970 --> 00:43:47.315 So Chris, do you have any tasks00:43:47.315 --> 00:43:50.918 to update here? Yes, right now.00:43:50.920 --> 00:43:52.360 Yeah, I haven't even touched a00:43:52.360 --> 00:43:54.754 single task to be honest. Oh sure,00:43:54.754 --> 00:43:58.890 so I'm sure there's a busy day yesterday.00:43:58.890 --> 00:44:00.726 Well, I I just didn't notice00:44:00.726 --> 00:44:02.370 that there were meeting tasks.00:44:02.370 --> 00:44:03.914 Sure sure. Sure sure.00:44:03.914 --> 00:44:06.230 I mean obviously the project tasks.00:44:06.230 --> 00:44:07.760 I'm still trying to get just00:44:07.760 --> 00:44:09.358 got access to this stuff repost00:44:09.358 --> 00:44:10.906 so where you set that up?00:44:10.910 --> 00:44:13.976 But yeah, I mean we can if you want00:44:13.976 --> 00:44:15.866 to do like a live demo or something00:44:15.866 --> 00:44:18.710 we can do the have like an all00:44:18.710 --> 00:44:21.025 internal and external meetings on00:44:21.025 --> 00:44:24.580 Clarabelle work and 76 oh, 67.00:44:27.380 --> 00:44:31.160 2667 OK yeah, your task number 77856 Yep.00:44:34.420 --> 00:44:36.880 OK, and so for this one.00:44:36.880 --> 00:44:39.190 And here we have a one hour00:44:39.190 --> 00:44:41.648 course stand up and an hour of00:44:41.648 --> 00:44:42.808 row meetings and you know what,00:44:42.808 --> 00:44:43.799 I'll just do for all of you guys.00:44:43.800 --> 00:44:44.900 I think I reduced.00:44:44.900 --> 00:44:46.000 I just reduced everyone00:44:46.000 --> 00:44:47.259 balancing by one for this,00:44:47.260 --> 00:44:49.136 but that probably wasn't the best practice.00:44:49.140 --> 00:44:50.030 Will do it differently now.00:44:58.400 --> 00:44:59.960 Cool, so we have that one.00:44:59.960 --> 00:45:01.100 And then let's let's talk00:45:01.100 --> 00:45:02.012 about yesterday so Chris,00:45:02.020 --> 00:45:05.100 would you get into yesterday?00:45:05.100 --> 00:45:06.884 Yeah, so that I think I was yesterday.00:45:11.340 --> 00:45:12.540 Yeah, I I. Let's see.00:45:12.540 --> 00:45:14.040 I had a podbay Sprint00:45:14.040 --> 00:45:14.940 planning session yesterday.00:45:14.940 --> 00:45:16.950 It was about to have had00:45:16.950 --> 00:45:17.955 the crosspad planning.00:45:17.960 --> 00:45:19.740 That was half an hour.00:45:19.740 --> 00:45:21.210 You were part of both of00:45:21.210 --> 00:45:21.945 those yesterday morning.00:45:24.390 --> 00:45:27.090 And I had a shadow,00:45:27.090 --> 00:45:30.340 Tristan, I think that one.00:45:30.340 --> 00:45:31.668 Project was at 40.00:45:31.668 --> 00:45:35.671 Gosh, I can't remember 7. Sorry 7884.00:45:35.671 --> 00:45:37.177 I think it's what it was.00:45:37.180 --> 00:45:39.868 I think that's the task number.00:45:39.870 --> 00:45:44.238 So I cannot read a step up maybe.00:45:44.240 --> 00:45:47.692 OK sife yeah. OK, cool,00:45:47.692 --> 00:45:50.289 you don't have any tickets for sife,00:45:50.290 --> 00:45:52.070 so for what I'm gonna00:45:52.070 --> 00:45:53.850 make you guys right now.00:45:58.600 --> 00:46:03.080 Do you guys have on your calendars, UM?00:46:03.080 --> 00:46:05.174 Do you have anything on your00:46:05.174 --> 00:46:07.824 calendars that you know are like kind00:46:07.824 --> 00:46:09.794 of planned working with sessions?00:46:09.800 --> 00:46:13.280 I have a shadowing session with00:46:13.280 --> 00:46:16.680 David at 3:00 PM Eastern Time.00:46:16.680 --> 00:46:20.848 OK, does it have a project specific for it?00:46:20.850 --> 00:46:22.826 It's probably going to be the road project.00:46:22.830 --> 00:46:25.836 I'm a sui. Which by the way,00:46:25.836 --> 00:46:27.180 I do like yesterday there was00:46:27.229 --> 00:46:28.657 a rose start of Sprint tag up.00:46:28.660 --> 00:46:30.886 I was in that for 30 minutes.00:46:30.890 --> 00:46:33.858 OK so that one you do have here00:46:33.858 --> 00:46:37.020 you have one hour for ROH tag UPS.00:46:37.020 --> 00:46:40.228 So just kind of change that time 1.5.00:46:40.230 --> 00:46:40.570 Boom00:46:43.400 --> 00:46:44.792 and then I'm going to make a little00:46:44.792 --> 00:46:46.186 bit of this for all y'all guys.00:46:46.190 --> 00:46:47.898 I think pretty much everyone Alex are00:46:47.898 --> 00:46:50.010 you out of the shadow training world?00:46:50.010 --> 00:46:51.802 Or are you kind of just in00:46:51.802 --> 00:46:53.090 the full hustling Now yeah,00:46:53.090 --> 00:46:55.050 I'm just mainly just doing my tasks.00:46:55.050 --> 00:46:58.850 OK, cool. Life comes at you quick.00:46:58.850 --> 00:47:00.386 OK, I'm gonna ask you guys.00:47:00.390 --> 00:47:03.310 5 hour kind of we call this a bucket ticket.00:47:03.310 --> 00:47:04.895 Bucket tickets are not something00:47:04.895 --> 00:47:06.163 we like to do,00:47:06.170 --> 00:47:07.710 but they're necessary so often.00:47:07.710 --> 00:47:08.886 But let me click make each of00:47:08.886 --> 00:47:10.020 you guys a bucket ticket.00:47:10.020 --> 00:47:11.970 That's called training and shadowing.00:47:11.970 --> 00:47:15.237 So you said you did an hour of cyfa00:47:15.237 --> 00:47:17.540 shadowing with Tristan yesterday.00:47:17.540 --> 00:47:20.288 There's an hour and a half.00:47:20.290 --> 00:47:21.190 Maybe I should make this 10.00:47:21.190 --> 00:47:21.838 Let's make this 10.00:47:25.600 --> 00:47:26.695 Yeah, I've done quite a00:47:26.695 --> 00:47:27.790 bit of shadowing as well.00:47:27.790 --> 00:47:29.030 Oh cool. Cool cool, cool.00:47:29.030 --> 00:47:30.927 And actually the first day I did.00:47:35.350 --> 00:47:38.719 Two hour 2.25.00:47:38.720 --> 00:47:42.656 Our session with Brandon. First day.00:47:42.660 --> 00:47:44.796 Oh, that was on Tuesday though.00:47:44.800 --> 00:47:49.110 Yeah, OK, yeah last week, who cares?00:47:49.110 --> 00:47:53.170 We're in we're in a whole new world now, man.00:47:53.170 --> 00:47:56.386 Resting on Fridays at my so sure sure00:47:56.386 --> 00:47:58.354 Wednesday Wednesday yeah my wife,00:47:58.354 --> 00:48:01.070 my ex-wife company does Friday to Friday00:48:01.145 --> 00:48:03.926 and I am so jealous of it because it's00:48:03.926 --> 00:48:06.210 just such a kind of a nice clean thing.00:48:06.210 --> 00:48:07.494 And then on those Fridays on00:48:07.494 --> 00:48:08.350 their dumbest Sprint plan,00:48:08.350 --> 00:48:09.630 they just take the rest of day off.00:48:09.630 --> 00:48:13.230 But internal companies man.00:48:13.230 --> 00:48:15.422 Upsides and downsides abound.00:48:15.422 --> 00:48:18.666 OK, so we'll call that00:48:18.666 --> 00:48:20.688 internal external meetings.00:48:20.690 --> 00:48:22.626 Let's quick make everyone and it's 10 hours.00:48:22.630 --> 00:48:24.804 Let's look at the all 10 hours and00:48:24.804 --> 00:48:27.282 what we're gonna do with that one00:48:27.282 --> 00:48:29.876 is just be really on top of it.00:48:29.880 --> 00:48:34.784 So anytime you get pulled into any training.00:48:34.790 --> 00:48:39.056 Shadowing etc. If you don't have.00:48:39.060 --> 00:48:42.504 Uh. Tasks or anything else for it.00:48:44.870 --> 00:48:47.510 Just throw them up on here.00:48:47.510 --> 00:48:49.604 And should that also include, like the00:48:49.604 --> 00:48:52.278 front end pair programming training as well?00:48:52.280 --> 00:48:53.960 Yeah, so like I was saying with those,00:48:53.960 --> 00:48:56.224 I think probably your first couple of weeks00:48:56.224 --> 00:48:58.644 you should just go to them and just absorb00:48:58.644 --> 00:49:00.780 and pay attention and everything like that.00:49:00.780 --> 00:49:02.553 So for those that just make sure going there,00:49:02.560 --> 00:49:04.570 we put them on to here.00:49:04.570 --> 00:49:07.250 But then as you guys get a bit00:49:07.250 --> 00:49:09.350 more like actionable work.00:49:09.350 --> 00:49:11.342 You want to be a bit more specific00:49:11.342 --> 00:49:12.987 about those 'cause they are not.00:49:12.990 --> 00:49:14.754 You know it can just be kind of a00:49:14.754 --> 00:49:16.597 time suck for you for the whole day.00:49:16.600 --> 00:49:19.048 OK, it could be working on actual tasks.00:49:24.050 --> 00:49:25.230 For them, when they're useful,00:49:25.230 --> 00:49:26.558 I'm very against them.00:49:26.558 --> 00:49:29.420 When they turn into kind of just like a.00:49:29.420 --> 00:49:30.806 Hang out party 'cause then everyone00:49:30.806 --> 00:49:32.479 then like next thing you know like oh00:49:32.479 --> 00:49:34.128 man that was two hours and I'm 2 hours00:49:34.128 --> 00:49:36.007 behind of my tasks and that kind of00:49:36.007 --> 00:49:39.649 kind of what does snowball pretty.00:49:39.650 --> 00:49:40.420 Pretty severely.00:49:54.480 --> 00:49:55.540 I hate this so much.00:49:55.540 --> 00:49:57.904 What's going on here?00:49:57.904 --> 00:50:00.670 Oh no. That is not good.00:50:00.670 --> 00:50:01.855 Oh my goodness,00:50:01.860 --> 00:50:02.988 that's really bad, OK?00:50:11.000 --> 00:50:13.128 So and here this is actually a great00:50:13.128 --> 00:50:15.486 already did Chris let me Justin nice Justin.00:50:29.800 --> 00:50:32.400 OK, so a quick just kind of call out here00:50:32.465 --> 00:50:34.742 and I think Jeremy I saw it was you.00:50:41.080 --> 00:50:43.156 These kind of tasks right here.00:50:43.160 --> 00:50:45.085 These two ones are these00:50:45.085 --> 00:50:47.010 scariest tasks you can have.00:50:49.840 --> 00:50:52.960 And of course this is not on you at all.00:50:52.960 --> 00:50:54.286 And I know you have plans00:50:54.286 --> 00:50:55.640 for both of these already,00:50:55.640 --> 00:50:57.000 so this is definitely not,00:50:57.000 --> 00:50:58.135 and I'll probably let's just00:50:58.135 --> 00:50:59.560 be a bit more blunt here.00:50:59.560 --> 00:51:00.721 These athlete tickets00:51:00.721 --> 00:51:02.269 here are terrifying me.00:51:05.280 --> 00:51:07.302 'cause you have to think about00:51:07.302 --> 00:51:09.520 anytime in the Sprint. Is.00:51:11.560 --> 00:51:13.105 Potential work right?00:51:13.105 --> 00:51:18.390 So if I see this and I'm Michael Perez,00:51:18.390 --> 00:51:20.500 I'm dividing this by. Actually,00:51:20.500 --> 00:51:21.984 I think he's a slightly lower allocation.00:51:21.990 --> 00:51:24.138 I think it's allocation 6A day.00:51:24.140 --> 00:51:26.836 That's a almost two week and weekend a00:51:26.836 --> 00:51:29.994 day or a week and two days of work that00:51:29.994 --> 00:51:33.150 I don't have any idea what it's gonna be.00:51:33.150 --> 00:51:36.710 Sure, so if I'm looking at a Sprint,00:51:36.710 --> 00:51:40.476 you know we're 9 to the 21st.00:51:40.480 --> 00:51:42.475 That's one. Basically he's gonna00:51:42.475 --> 00:51:46.480 run out of work tomorrow. Right?00:51:46.480 --> 00:51:48.405 So if you have these balancing tickets00:51:48.405 --> 00:51:51.776 and I I can even show you like our buddy,00:51:51.776 --> 00:51:54.616 our buddy our buddy. Josh stover.00:51:54.616 --> 00:51:56.387 He had one of these today too.00:51:56.390 --> 00:51:58.806 That's definitely a time when you want like00:51:58.806 --> 00:52:01.408 pull the ripcord sound the alarms. You know,00:52:01.408 --> 00:52:03.860 hit me up as much as you want Daniel.00:52:03.860 --> 00:52:04.991 I have this.00:52:04.991 --> 00:52:07.540 I have this 47 hour task and00:52:07.540 --> 00:52:09.220 I have no work on it.00:52:09.220 --> 00:52:10.940 I don't know what I'm supposed to do.00:52:10.940 --> 00:52:11.988 'cause if that does,00:52:11.988 --> 00:52:14.292 let's say I didn't catch this right now00:52:14.292 --> 00:52:16.332 'cause I haven't heard anything about00:52:16.332 --> 00:52:18.170 this specifically from Michael or Eric.00:52:18.170 --> 00:52:19.458 I'm gonna kind of go berserk as soon00:52:19.458 --> 00:52:20.908 as I'm off this phone with you guys.00:52:20.910 --> 00:52:22.696 My berserk, by the way, is relatively.00:52:22.696 --> 00:52:25.537 It's more like come on guys, uh,00:52:25.537 --> 00:52:29.400 but uh, when? The end of day Friday.00:52:29.400 --> 00:52:30.930 If he wakes up on Monday,00:52:30.930 --> 00:52:33.178 goes to look at his work and doesn't00:52:33.178 --> 00:52:34.967 notice this big Ole Honker here.00:52:34.970 --> 00:52:39.638 He could very easily lose time.00:52:39.640 --> 00:52:41.278 Which when you guys are trying to00:52:41.278 --> 00:52:42.575 get your billable and you guys00:52:42.575 --> 00:52:45.296 are that affects you guys.00:52:45.296 --> 00:52:47.310 Performance bonuses and all those00:52:47.310 --> 00:52:49.113 other things is your historical00:52:49.113 --> 00:52:51.339 billable and kind of how you're00:52:51.339 --> 00:52:53.297 performing on projects and the like.00:52:53.300 --> 00:52:55.050 You wanna just make sure00:52:55.050 --> 00:52:56.450 you're ahead of that.00:52:56.450 --> 00:52:56.958 OK, yeah,00:52:56.958 --> 00:52:58.990 I think those got assigned to me yesterday.00:52:58.990 --> 00:52:59.564 Sprint planning.00:52:59.564 --> 00:53:02.479 I don't even know what they are to be honest.00:53:02.480 --> 00:53:05.224 Yeah, and like I said new as new,00:53:05.230 --> 00:53:06.860 you know?00:53:06.860 --> 00:53:08.988 I don't wanna like scare you guys for00:53:08.988 --> 00:53:10.876 this Sprint at all like this Sprint.00:53:10.880 --> 00:53:11.888 Don't worry about it.00:53:11.888 --> 00:53:13.400 Even next Sprint you know like00:53:13.454 --> 00:53:14.906 do a little bit better than00:53:14.906 --> 00:53:16.319 this Sprint and you'll be fine.00:53:16.320 --> 00:53:17.922 But you know couple months down00:53:17.922 --> 00:53:19.758 the line when you guys are like00:53:19.760 --> 00:53:22.070 a bit more established you know00:53:22.070 --> 00:53:23.610 everything that's going on.00:53:23.610 --> 00:53:24.948 These kind of things should terribly,00:53:24.950 --> 00:53:27.146 but Jeremy for your two things,00:53:27.150 --> 00:53:28.305 those ones like.00:53:28.305 --> 00:53:32.044 I know bid you're going to do a Co00:53:32.044 --> 00:53:34.434 Co programming session with Taylor,00:53:34.440 --> 00:53:35.646 so for something like that you'll00:53:35.646 --> 00:53:37.140 just want to hit up and let me00:53:37.140 --> 00:53:38.318 show you guys just kind of like00:53:38.318 --> 00:53:39.678 a good example of how to do this.00:53:43.660 --> 00:53:47.926 Jeremy Labros and Kevin Klos OK.00:53:54.120 --> 00:53:55.583 So this is another good kind of00:53:55.583 --> 00:53:56.920 best practices for go over just a00:53:56.920 --> 00:53:58.394 second guys and I do have to bounce00:53:58.394 --> 00:53:59.678 as soon as possible after that.00:53:59.680 --> 00:54:02.256 So let's say you notice something like this.00:54:02.260 --> 00:54:04.766 I have a 15 hour task with00:54:04.766 --> 00:54:06.160 nothing assigned to it.00:54:06.160 --> 00:54:07.840 That's roughly 2 days of work that00:54:07.840 --> 00:54:09.538 I don't know what I'm gonna do.00:54:09.540 --> 00:54:11.070 You just have this with PJ.00:54:13.720 --> 00:54:15.960 On teams guys, you're going to see00:54:15.960 --> 00:54:18.078 these little three dots on your chat.00:54:18.080 --> 00:54:19.778 You don't wanna find this app.00:54:19.780 --> 00:54:21.884 I suggest you all doing this right away.00:54:21.890 --> 00:54:25.215 You're gonna want to add Azure DevOps.00:54:25.220 --> 00:54:26.452 I already have it.00:54:26.452 --> 00:54:28.300 It's a quick little configuration thing.00:54:28.300 --> 00:54:30.623 If you need any help with it let me know.00:54:30.623 --> 00:54:31.528 Actually I can tell her00:54:31.528 --> 00:54:32.309 somewhere around just ahead.00:54:45.310 --> 00:54:46.894 So you wanna pull in the task and00:54:46.894 --> 00:54:48.685 to here and once I just do this00:54:48.685 --> 00:54:50.110 example real quick and then we'll00:54:50.110 --> 00:54:51.562 kind of go through setting this00:54:51.562 --> 00:54:53.334 up with one of you guys when you00:54:53.334 --> 00:54:55.149 guys if you want to get ready to00:54:55.149 --> 00:54:56.920 share your screen in just a minute.00:54:56.920 --> 00:54:58.486 We can show you setting this00:54:58.486 --> 00:54:59.920 up so put in the task number.00:55:02.620 --> 00:55:03.270 And here.00:55:06.590 --> 00:55:07.438 Drop it in there.00:55:09.750 --> 00:55:10.560 Add the PM.00:55:24.830 --> 00:55:25.738 And anything like this.00:55:25.738 --> 00:55:27.379 Feel free to holler me in there00:55:27.379 --> 00:55:28.765 too if you don't get answers.00:55:28.770 --> 00:55:30.261 If you know you're kind of like00:55:30.261 --> 00:55:31.948 I ask Kevin 'cause BMS get busy.00:55:31.950 --> 00:55:35.060 They just it's nothing ever.00:55:35.060 --> 00:55:37.280 Personal, but it, you know,00:55:37.280 --> 00:55:38.240 feel free to pull me in.00:55:38.240 --> 00:55:39.675 I'm I'm not a not a hammer00:55:39.675 --> 00:55:41.151 guy I'm just gonna like OK00:55:41.151 --> 00:55:42.496 let's get this figured out.00:55:45.590 --> 00:55:47.070 You'll wanna bring these00:55:47.070 --> 00:55:49.290 things up as soon as possible,00:55:49.290 --> 00:55:51.378 so I'm just gonna hit up both these guys.00:55:51.380 --> 00:55:55.377 Oh, and actually Jeremy, were you in00:55:55.377 --> 00:55:58.130 that cmoc chat earlier this morning?00:55:58.130 --> 00:55:59.396 Yeah, yeah, I saw that they00:55:59.396 --> 00:56:00.710 made a meeting for tomorrow.00:56:00.710 --> 00:56:03.850 OK, cool and let me make00:56:03.850 --> 00:56:05.590 sure you're in on that one.00:56:05.590 --> 00:56:07.150 Oh, you are you are you are OK00:56:07.150 --> 00:56:08.843 cool ummul want to just kind of be00:56:08.843 --> 00:56:10.349 kind of pestering on these things?00:56:10.350 --> 00:56:12.436 'cause what this is saying to me00:56:12.436 --> 00:56:14.310 is this is like we said we don't00:56:14.310 --> 00:56:15.561 generally like to do buckets where00:56:15.561 --> 00:56:16.681 they're specific to projects and00:56:16.681 --> 00:56:18.208 you'll see what it kind of killed.00:56:18.210 --> 00:56:19.520 A lot of those yesterday.00:56:22.090 --> 00:56:25.234 I'd rather them just be those00:56:25.234 --> 00:56:26.806 broad balancing tickets.00:56:26.810 --> 00:56:28.651 And that way anyone can use them00:56:28.651 --> 00:56:30.488 for any project if they're needed.00:56:30.490 --> 00:56:31.278 So, like Josh Dover,00:56:31.278 --> 00:56:32.950 he's at this 25 hours in balancing.00:56:32.950 --> 00:56:34.862 He's at 39 hours this morning I was00:56:34.862 --> 00:56:36.847 able to find him 14 hours of work.00:56:36.850 --> 00:56:38.270 It's just kind of like00:56:38.270 --> 00:56:39.406 cruising through right away.00:56:39.410 --> 00:56:42.272 Danny, I'm able to find him some more work.00:56:42.280 --> 00:56:43.420 Alex looks like you're doing OK,00:56:43.420 --> 00:56:44.500 but we can still get you00:56:44.500 --> 00:56:45.649 more work going on here too.00:56:48.200 --> 00:56:51.023 But the more kind of generic these are, the00:56:51.023 --> 00:56:54.130 easier it is for them to kind of pull out.00:56:54.130 --> 00:56:56.188 Another kind of just best practice00:56:56.188 --> 00:56:58.676 guys is gonna be kind of figuring00:56:58.676 --> 00:57:01.119 out the projects that you're on and00:57:01.196 --> 00:57:03.815 knowing them at like the drop of a hat.00:57:03.820 --> 00:57:06.114 OK, let's quick quick quick.00:57:06.114 --> 00:57:08.301 I wanna be you guys who wants to share if00:57:08.301 --> 00:57:10.159 you didn't already set up the Azure thing?00:57:10.160 --> 00:57:13.427 Or did you guys all set up the Azure?00:57:13.430 --> 00:57:15.486 Plug in and have no issue at all.00:57:15.490 --> 00:57:16.505 Maybe all set up and no issue.00:57:16.510 --> 00:57:17.614 That's all cool.00:57:17.614 --> 00:57:19.454 Let's make sure everyone has00:57:19.454 --> 00:57:21.787 it on their on their teams.00:57:21.790 --> 00:57:23.326 Yeah, send it up right now.00:57:23.330 --> 00:57:24.518 Organization quite Adventures Project00:57:24.518 --> 00:57:26.590 which I put in for their yeah,00:57:26.590 --> 00:57:28.190 do I share your screen and I can00:57:28.190 --> 00:57:29.661 walk you through just because it's00:57:29.661 --> 00:57:31.250 the same question I was gonna have.00:57:33.520 --> 00:57:39.010 Noice OK so hit that drop down for project.00:57:39.010 --> 00:57:40.767 And you're just going to find Seth,00:57:40.770 --> 00:57:42.060 so you can type ahead, Seth.00:57:44.720 --> 00:57:47.870 And it's gonna be self product OK perfect.00:57:56.740 --> 00:57:57.848 Why you not work?00:58:00.060 --> 00:58:02.358 Maybe let's see the drop down again,00:58:02.360 --> 00:58:03.160 maybe I got it wrong.00:58:03.160 --> 00:58:07.030 That's a little. Scroll around sev.00:58:07.030 --> 00:58:10.340 Just going up for me, it's the touch.00:58:10.340 --> 00:58:12.060 Should just be self product.00:58:12.060 --> 00:58:12.968 Let me quick check.00:58:12.968 --> 00:58:14.180 Give me one second. Yep.00:58:16.290 --> 00:58:19.618 Of those things. I should write00:58:19.618 --> 00:58:21.388 this down so much of what I do.00:58:21.390 --> 00:58:22.510 It's like no. It's just like this.00:58:22.510 --> 00:58:24.250 OK, sorry it's Sev Dash.00:58:24.250 --> 00:58:26.720 Try all product all project.00:58:30.060 --> 00:58:32.216 It comes up no. That's iteration pass.00:58:32.220 --> 00:58:33.850 The product is always interesting.00:58:33.850 --> 00:58:34.650 Give me one second.00:58:40.150 --> 00:58:42.698 Pretty sure Seth product.00:58:42.700 --> 00:58:45.420 It is the bug on the thing itself.00:58:45.420 --> 00:58:47.118 I think it is. Seth prod.00:58:47.120 --> 00:58:50.466 Yeah product it is. Yeah so product.00:58:58.900 --> 00:58:59.260 Yeah.00:59:04.010 --> 00:59:09.748 OK well. It says no. No sorry man.00:59:12.300 --> 00:59:13.424 Error logging no way.00:59:13.424 --> 00:59:14.829 Jose you're not getting it.00:59:14.830 --> 00:59:16.258 This is not going to do it.00:59:16.260 --> 00:59:17.732 Mind your own business.00:59:17.732 --> 00:59:19.680 Keep on get the stuff in buddy.00:59:19.680 --> 00:59:21.367 OK, does anyone else having this product00:59:21.367 --> 00:59:23.368 or is it working for anybody else?00:59:23.370 --> 00:59:26.180 It did work for me.00:59:26.180 --> 00:59:28.371 Stef product I did Scroll down on00:59:28.371 --> 00:59:30.647 the drop list and not type it in.00:59:30.650 --> 00:59:32.954 I don't know if that'll make a difference.00:59:32.960 --> 00:59:34.790 Hey, that's the kind of that's00:59:34.790 --> 00:59:39.130 the kind of QA work we need, yeah?00:59:39.130 --> 00:59:43.770 No, not Eddie aberrant behaviors.00:59:43.770 --> 00:59:45.240 Hey guys I have to get going00:59:45.240 --> 00:59:46.510 to the next thing here.00:59:46.510 --> 00:59:48.058 Thank you all for your time.00:59:48.060 --> 00:59:51.749 Please at anytime you guys need anything.00:59:51.750 --> 00:59:52.814 I know everyone is kind of saying00:59:52.814 --> 00:59:53.986 this in general to you guys right now,00:59:53.990 --> 00:59:55.691 so it's probably a lot of like man who00:59:55.691 --> 00:59:57.818 do I who do I even talk to about this stuff?00:59:57.820 --> 00:59:59.227 13 different people like tell me if00:59:59.227 --> 01:00:00.919 you have an issue it's like who do01:00:00.919 --> 01:00:02.270 I start with anything with Azure.01:00:02.270 --> 01:00:03.858 Anything with assigned work,01:00:03.858 --> 01:00:05.843 anything with PMS in general.01:00:05.850 --> 01:00:07.768 I am the PM manager and Scrum01:00:07.768 --> 01:00:09.197 master so anything along those01:00:09.197 --> 01:00:13.050 lines that I can help with please.01:00:13.050 --> 01:00:15.474 It's never a bad thing to call someone01:00:15.474 --> 01:00:18.246 out if something is not working right.01:00:18.250 --> 01:00:20.392 You know the more honest you can be with01:00:20.392 --> 01:00:22.649 each other with our failings and the like,01:00:22.650 --> 01:00:23.994 the more productive we can be as01:00:23.994 --> 01:00:25.310 a whole rather than can be like,01:00:25.310 --> 01:00:26.619 oh, I'm gonna give him a chance01:00:26.619 --> 01:00:27.809 to kind of get this out.01:00:27.810 --> 01:00:28.846 Don't slag anyone off.01:00:28.846 --> 01:00:30.869 Don't be mean about it like hey man,01:00:30.870 --> 01:00:32.382 like I always pick on myself for Clint01:00:32.382 --> 01:00:33.886 first just in case you guys don't know,01:00:33.890 --> 01:00:35.114 Clint and I are very close friends so01:00:35.114 --> 01:00:36.310 whenever you hear me making fun of Clint,01:00:36.310 --> 01:00:37.778 it's always with love.01:00:37.778 --> 01:00:39.980 Anything like clicks not doing his01:00:40.051 --> 01:00:41.872 job at all. I need tickets for.01:00:41.872 --> 01:00:43.540 I need tickets for this project01:00:43.598 --> 01:00:45.201 that he's on and you know he01:00:45.201 --> 01:00:46.924 just had this big bucket and he's01:00:46.924 --> 01:00:48.833 not getting back to me on him.01:00:48.833 --> 01:00:49.699 You know,01:00:49.699 --> 01:00:50.998 that's totally OK.01:00:51.000 --> 01:00:53.190 Just let me know and I can help with that01:00:53.251 --> 01:00:55.177 and it won't be like a big old deal.