00:00:03.222 --> 00:00:06.132 Is burned down, is 13 hours behind.
00:00:06.632 --> 00:00:06.962 OK.
00:00:08.492 --> 00:00:11.670 Like I said, with these are the individual dates and these are
00:00:11.670 --> 00:00:14.242 gonna be the expected time and this is the actual.
00:00:15.682 --> 00:00:16.132 OK.
00:00:19.872 --> 00:00:21.312 Trenton what's the story point?
00:00:24.012 --> 00:00:29.096 Isn't it like, like how many hours are assigned to like a
00:00:29.096 --> 00:00:30.762 certain user story?
00:00:31.922 --> 00:00:37.266 Essentially, yeah, great point. So a story point is essentially
00:00:37.266 --> 00:00:42.610 the top level estimation for the work for that user story to be
00:00:42.610 --> 00:00:47.454 complete. So if we're looking at this bid bug and they're
00:00:47.454 --> 00:00:52.965 two-story points assigned to it, the overall conceit is that this
00:00:52.965 --> 00:00:56.472 entire bug can be completed in two hours.
00:00:58.082 --> 00:00:58.412 OK.
00:01:00.132 --> 00:01:03.483 And it goes down the line. So when you guys are making new
00:01:03.483 --> 00:01:06.721 user stories, you want the full estimate to complete the
00:01:06.721 --> 00:01:10.413 entirety of the user story to be the story points on there. Now,
00:01:10.413 --> 00:01:13.708 we could break that out to 17 tasks if we want each be 25
00:01:13.708 --> 00:01:16.775 minutes long, if that's something that was necessary,
00:01:16.775 --> 00:01:20.240 rarely would be, but that's me. The total time for that user
00:01:20.240 --> 00:01:21.092 story, Jessica.
00:01:22.662 --> 00:01:26.345 I've heard both, so I want your opinion. Is this something that
00:01:25.782 --> 00:01:26.372 Yeah, go for it.
00:01:26.345 --> 00:01:29.856 we are guesstimating for the devs or is it something that we
00:01:29.856 --> 00:01:33.424 it would be best to ask them directly? Hey, what is your best
00:01:33.424 --> 00:01:36.992 guess animation on how long this is gonna take you the second
00:01:36.772 --> 00:01:39.362 Yes. Yeah, we do not make these.
00:01:36.992 --> 00:01:37.222 one?
00:01:39.612 --> 00:01:39.902 OK.
00:01:41.202 --> 00:01:45.348 And as with most things, sadly there is going to be a very
00:01:45.348 --> 00:01:46.472 small exception.
00:01:47.322 --> 00:01:49.922 And that would be if a bug comes in.
00:01:50.842 --> 00:01:53.856 You can set it at 2 right away until you can get a developer's
00:01:53.856 --> 00:01:56.439 attention, but the better suggestion would be just to
00:01:56.439 --> 00:01:59.405 never get a story point unless that estimation is coming from
00:01:59.405 --> 00:02:01.941 the developer who's going to do the work or from the
00:02:01.941 --> 00:02:02.802 architecture team.
00:02:03.522 --> 00:02:06.692 I've gotten one from from Brendan on a GFS. He told me
00:02:06.272 --> 00:02:06.562 Cool.
00:02:06.692 --> 00:02:10.266 this will take me. I think he said it was like 8 hours or 12.
00:02:10.266 --> 00:02:14.012 It was 12 hours and we broke it out into four different tickets.
00:02:14.432 --> 00:02:15.082 Love it.
00:02:14.772 --> 00:02:17.272 For him to do it so, OK, cool. That makes sense.
00:02:16.362 --> 00:02:18.372 Excellent job. Excellent job, Trenton.
00:02:19.932 --> 00:02:23.402 So for non bug tickets like whenever you're just doing like
00:02:23.402 --> 00:02:24.732 a standard story point.
00:02:24.952 --> 00:02:25.262 Mm-hmm.
00:02:26.612 --> 00:02:29.967 You said don't make them or don't put story point numbers
00:02:29.967 --> 00:02:32.802 unless you get them from a developer or from the
00:02:32.802 --> 00:02:36.389 architecture team. So what does that mean? It could come from
00:02:36.389 --> 00:02:39.802 the FSD, like the estimates on on user stories in the FSD.
00:02:40.152 --> 00:02:43.286 100% that sort of button, 90% of them should come from, unless
00:02:43.286 --> 00:02:43.982 it's new work.
00:02:48.822 --> 00:02:54.109 Cool. So story points are again, kind of a more abstraction of
00:02:54.109 --> 00:02:58.641 time and then the task completion time, anything time
00:02:58.641 --> 00:03:03.929 based exceeds etcetera. That's the reality, right? So if I put
00:03:03.929 --> 00:03:07.202 say 20 story points into Clint Sprint.
00:03:08.042 --> 00:03:11.883 And he takes a look at him. He had already proved his estimates
00:03:11.883 --> 00:03:15.425 or whatever, and there's 20 hours of associated tasks. But
00:03:15.425 --> 00:03:19.146 let's say Clint's Rat as hell, and he manages to knock it all
00:03:19.146 --> 00:03:22.567 out in 14 hours. Boy, for him, we're doing good history.
00:03:22.567 --> 00:03:25.688 Percent percentage. Sorry, sorry. Percent complete.
00:03:25.688 --> 00:03:29.470 Percentage is doing great. We're happy for them. But now let's
00:03:29.470 --> 00:03:32.951 say that me. I'm the other developer, and I have 20 story
00:03:32.951 --> 00:03:36.492 points in the Sprint, but it takes me 40 hours to do them.
00:03:37.282 --> 00:03:40.540 That helps us get into that data because it could be a couple of
00:03:40.540 --> 00:03:43.648 different things. It could just be a training issue that they
00:03:43.648 --> 00:03:46.505 need more information about these tasks, maybe they need
00:03:46.505 --> 00:03:49.663 more specific training. Let's say I'm always beefing it on the
00:03:49.663 --> 00:03:52.771 catalog, so I need more help on the catalog next time I get a
00:03:52.771 --> 00:03:55.779 catalog task, maybe it's there were way underestimated. All
00:03:55.779 --> 00:03:58.586 this stuff helps us get information to help make Kyle's
00:03:58.586 --> 00:04:01.593 job more efficient at those estimations from the get go and
00:04:01.593 --> 00:04:04.701 our architecture team have a better understanding of it. Yes,
00:04:04.701 --> 00:04:05.102 Charlie.
00:04:06.012 --> 00:04:10.553 So in a scenario where unfortunately we don't complete
00:04:10.553 --> 00:04:15.755 an entire user story in a Sprint and we wind up carrying tasks
00:04:15.755 --> 00:04:21.040 across, do we update the story point in the new Sprint for only
00:04:21.040 --> 00:04:23.682 the work on the remaining tasks?
00:04:24.072 --> 00:04:27.364 Great question and no, you'll leave the story points exactly
00:04:25.852 --> 00:04:26.182 OK.
00:04:27.364 --> 00:04:30.710 what they are, and that is one of those things that hopefully
00:04:30.710 --> 00:04:34.002 it just kind of comes out in the wash and from the reporting
00:04:31.672 --> 00:04:31.952 Yep.
00:04:34.002 --> 00:04:37.348 we've done in the past four or five, maybe long six months or
00:04:37.348 --> 00:04:40.478 so on story points, it has worked like let's say I have a
00:04:40.478 --> 00:04:44.040 really bump Sprint because a lot of stuff came at me and I had 20
00:04:44.040 --> 00:04:47.332 story points. I only finished five of them this Sprint, that
00:04:47.332 --> 00:04:50.679 next Sprint I might do 35 or something like that. And so when
00:04:50.162 --> 00:04:50.532 OK.
00:04:50.679 --> 00:04:54.025 I do my reporting, I don't just take the take the snapshot of
00:04:54.025 --> 00:04:54.942 just that Sprint.
00:04:55.042 --> 00:04:59.066 But then I also take a 3 Sprint long snapshot to get a better
00:04:59.066 --> 00:05:01.792 idea of how their overall performance is.
00:04:59.562 --> 00:05:00.952 Got it. Yeah.
00:05:02.212 --> 00:05:02.722 Sweet, thanks.
00:05:03.422 --> 00:05:03.912 Course.
00:05:06.612 --> 00:05:10.604 OK. So that right there is story points. So like I said, it's an
00:05:10.604 --> 00:05:14.473 abstraction of time that more equates to completion. So one of
00:05:14.473 --> 00:05:17.913 the big things on it is let's say someone has a general
00:05:17.913 --> 00:05:21.782 support ticket, right. There are no story points associated to
00:05:21.782 --> 00:05:25.590 that and that's why you'll see some of these things where you
00:05:25.590 --> 00:05:29.214 have people with a ton of story points like Mr Lynch here.
00:05:29.214 --> 00:05:33.022 That's probably because some of those tasks have followed him
00:05:33.022 --> 00:05:36.829 for a handful of sprints. They also see some people with very
00:05:36.829 --> 00:05:38.242 few story points total.
00:05:38.322 --> 00:05:39.412 39 right.
00:05:40.842 --> 00:05:44.023 And that's because they might have a lot of assist tickets or
00:05:44.023 --> 00:05:47.203 other things, so they're not being judged against their total
00:05:47.203 --> 00:05:50.589 time to completion, right? We're expecting everyone, let's say, a
00:05:50.589 --> 00:05:53.615 70 hour allocation is standard for two weeks Sprint. We're
00:05:53.615 --> 00:05:56.693 expecting to have 70 hours of story points complete because
00:05:56.693 --> 00:05:59.925 they might actually only get, say, 35 hours of story points or
00:05:59.925 --> 00:06:03.003 Tayler Duncan, this case, 39 hours story points. So they're
00:06:03.003 --> 00:06:06.183 not always gonna be a one to one, but we do hope that the end
00:06:06.183 --> 00:06:09.569 of that Sprint, there's 39 hours of completed work, right, rather
00:06:09.569 --> 00:06:10.082 than just.
00:06:10.252 --> 00:06:14.122 70 hours of time. That doesn't necessarily mean anything.
00:06:15.962 --> 00:06:18.362 Cool. Does anyone have any questions about story points? I
00:06:18.362 --> 00:06:20.762 know it's an interesting kind of abstraction and we don't.
00:06:20.852 --> 00:06:21.542 Umm.
00:06:22.492 --> 00:06:26.768 Uh, this give you an example of where I want to go, especially
00:06:26.768 --> 00:06:31.112 for some of our newer folks. My ultimate goal is that we do get
00:06:31.112 --> 00:06:34.980 towards a story point based Sprint so that there's a bit
00:06:34.980 --> 00:06:36.202 more incentive to.
00:06:36.852 --> 00:06:40.851 Complete your work at a rate that is befitting for the story
00:06:40.851 --> 00:06:44.915 point, and that way they can, you know, a developer hopefully
00:06:44.915 --> 00:06:48.192 will have a little bit of higher quality of life.
00:06:48.802 --> 00:06:51.709 Umm so that they can kind of have more. What's what I'm
00:06:51.709 --> 00:06:52.332 looking for?
00:06:58.152 --> 00:07:01.687 What should when you want something? What is it? Whatever.
00:07:01.687 --> 00:07:05.581 They get better incentive. Thank you, Charlie. So they have more
00:07:02.122 --> 00:07:02.712 Incentive.
00:07:05.581 --> 00:07:09.356 incentive to be like, cool. If I can knock this bad boy out in
00:07:09.356 --> 00:07:12.052 three hours and QA it and ship it, I'm good.
00:07:12.412 --> 00:07:15.318 You know, I don't think I would intentionally takes longer, but
00:07:15.318 --> 00:07:17.725 I think if someone has that incentive, so they could
00:07:17.725 --> 00:07:20.631 potentially have a shorter week, maybe a few hours extra in the
00:07:20.631 --> 00:07:23.583 back end of the day, maybe there was schedule gets a little more
00:07:23.583 --> 00:07:26.172 befitting for them. So don't just have to kind of grind,
00:07:26.172 --> 00:07:26.762 grind, grind.
00:07:29.042 --> 00:07:31.572 OK, someone knows where my head is on that. So story points.
00:07:31.572 --> 00:07:34.102 That's why I've been tracking them. Hopefully someday we can
00:07:34.102 --> 00:07:36.591 get to the concept of a story point based Sprint, but we're
00:07:36.591 --> 00:07:39.204 not quite there yet because we haven't had the data to back it
00:07:39.204 --> 00:07:41.112 up. That makes it look like something that's.
00:07:42.422 --> 00:07:45.651 Advantageous for business, right? OK. Block time. Everyone
00:07:45.651 --> 00:07:47.402 makes everyone understands that.
00:07:49.162 --> 00:07:51.612 I hope this is just the time that's blocked again.
00:07:52.452 --> 00:07:54.772 Well, let's talk exceeds so.
00:07:56.102 --> 00:07:59.748 Exceeds are overages are the time that the developers
00:07:59.748 --> 00:08:03.867 exceeded on their tickets. Now we saw around at those go out
00:08:03.867 --> 00:08:04.272 today.
00:08:05.982 --> 00:08:08.814 Where in. Sorry, Charlie, that it happened to be your guys
00:08:08.814 --> 00:08:10.302 because they were already full.
00:08:10.762 --> 00:08:10.902 I.
00:08:11.322 --> 00:08:14.412 Ohh good. Like I got it cause I earned it.
00:08:11.682 --> 00:08:13.692 But I thought it kept that comment.
00:08:15.172 --> 00:08:18.656 We didn't earn it. They did. But that's kind of part of The thing
00:08:18.656 --> 00:08:21.560 is end of the day we're responsible for the budgets of
00:08:21.560 --> 00:08:24.886 these projects. So when these tickets exceed it's incumbent on
00:08:24.886 --> 00:08:28.212 us to find out what happened, right? Why are they over now try
00:08:28.212 --> 00:08:31.433 this case for these things he knew because they're both CMMC
00:08:31.433 --> 00:08:34.864 based, I believe no one was, but he knew about that one too. But
00:08:34.864 --> 00:08:36.712 you know about it so that you can.
00:08:37.582 --> 00:08:40.658 Already hopefully have a plan now, seem sees paying it's all
00:08:40.658 --> 00:08:43.834 good, but let's say that it's a smaller client, like let's say
00:08:43.834 --> 00:08:47.111 what's one of my smaller clients like GLV or something like that
00:08:47.111 --> 00:08:50.388 and all I had in the Sprint was four hours for Jesse and they're
00:08:50.388 --> 00:08:53.665 very tight on their budget. They essentially know where every 15
00:08:53.665 --> 00:08:56.590 minute goes and he went six hours. But I didn't know that
00:08:56.590 --> 00:08:59.615 that means it's gonna be a couple phone calls for me. So we
00:08:59.615 --> 00:09:02.539 have to be tracking these exceeds really specifically now
00:09:02.539 --> 00:09:05.312 what I would like to see with exceeds as they come in.
00:09:06.672 --> 00:09:09.597 And let's just say we can probably find someone for an
00:09:09.597 --> 00:09:10.022 example.
00:09:12.702 --> 00:09:14.782 For owing to find people who have exceeds right now.
00:09:23.452 --> 00:09:27.522 OK, let's talk about Jesse. So Jesse has three hours of exceeds
00:09:27.522 --> 00:09:31.529 and then we also can see here through my equation that there's
00:09:31.529 --> 00:09:35.408 3 1/2 hours that needs to be removed from a Sprint. What I'm
00:09:35.408 --> 00:09:39.414 going to do then is let you the PMS know in that squad channel
00:09:39.414 --> 00:09:43.548 with that developer. Hey, here's where developer exceeded it was
00:09:43.548 --> 00:09:47.682 on, let's say that it was on one of my projects. He went over on
00:09:47.682 --> 00:09:51.243 this ticket for one of your projects and we're going to
00:09:51.243 --> 00:09:54.232 leave it up to the PM, Who's project exceeded.
00:09:54.302 --> 00:09:57.652 Case so that they know and B so that.
00:09:58.802 --> 00:10:02.369 They will have to take that work out from one of their sprints if
00:10:02.369 --> 00:10:05.828 it's something that absolutely can't budge, then we can go back
00:10:05.828 --> 00:10:09.341 to the group as a whole and find out. But I want us as a PM team
00:10:09.341 --> 00:10:12.584 to essentially have a variance Max of about five hours on a
00:10:12.584 --> 00:10:15.934 Sprint for the first part and then really, I'd really like to
00:10:15.934 --> 00:10:19.393 get it down to about one or two hours so that we're not kicking
00:10:19.393 --> 00:10:22.474 so many tickets at the end of the Sprint because we just
00:10:22.474 --> 00:10:25.933 exceeded tasks. We are actively kicking those tickets ourselves
00:10:25.933 --> 00:10:29.338 based on our own projects and we're communicating that back to
00:10:29.338 --> 00:10:29.932 the client.
00:10:30.262 --> 00:10:33.948 Let's say, like I said, I'll keep on using Jesse and me.
00:10:33.948 --> 00:10:37.052 Let's say he has three different tasks for GLV.
00:10:37.692 --> 00:10:41.043 Each one's four hours and he went over by three hours on one.
00:10:41.043 --> 00:10:44.394 That should then become on me to tell GLV. Hey, he went three
00:10:44.394 --> 00:10:47.907 hours over on this one task. I'm gonna have only had 12 hours in
00:10:47.907 --> 00:10:51.095 the Sprint for your work. I'm going to have to kick one of
00:10:51.095 --> 00:10:54.284 your tasks into the next Sprint. If we can lock down these
00:10:54.284 --> 00:10:57.527 sprints, we're going to have much better delivery rates for
00:10:57.527 --> 00:11:00.878 all clients, which is the end goal rather than kind of always
00:11:00.878 --> 00:11:03.742 having that one project. That's really just kind of.
00:11:04.602 --> 00:11:07.725 Bullying us essentially, and you know there's always kind of a
00:11:07.725 --> 00:11:10.502 flavor for the month. It's always been one or the other
00:11:10.502 --> 00:11:13.674 lately it's been CMMC. But I was in IIA, which was one of those
00:11:13.674 --> 00:11:15.112 for a very long time as well.
00:11:16.812 --> 00:11:18.292 You know, there's there's always a new one.
00:11:18.872 --> 00:11:21.581 Uh RX One was one for a long time, you know, et cetera, et
00:11:21.581 --> 00:11:21.902 cetera.
00:11:23.032 --> 00:11:25.622 Does that whole kind of process make sense for you guys?
00:11:29.892 --> 00:11:30.322 Yes.
00:11:30.042 --> 00:11:30.592 Yes.
00:11:30.952 --> 00:11:31.322 Yes.
00:11:31.192 --> 00:11:32.532 Well, excellent.
00:11:31.802 --> 00:11:32.012 Yes.
00:11:34.182 --> 00:11:34.752 Jessica.
00:11:37.672 --> 00:11:40.854 Makes sense. I was also going to say I appreciate you putting the
00:11:40.854 --> 00:11:43.890 ball in our court to decide what should be pushed and what can
00:11:41.692 --> 00:11:42.322 Ohh.
00:11:43.890 --> 00:11:45.192 stay and what can all that.
00:11:45.582 --> 00:11:49.179 And like I said, you might have a time where there's just
00:11:49.179 --> 00:11:52.775 nothing, right? You know, Mickey had to a terrible little
00:11:52.775 --> 00:11:56.744 Sophie's choice situation last Sprint, where it was Mr Tim Crum
00:11:56.744 --> 00:11:59.472 and three of her projects, Tasco Rydal and.
00:12:00.832 --> 00:12:04.232 Branford group, right, because she was just up a Creek.
00:12:05.332 --> 00:12:08.454 But at the end of the day, these guys can only work so much, so
00:12:08.454 --> 00:12:11.234 we have to just kick out work and we just have to make a
00:12:11.234 --> 00:12:14.307 decision and tell the client. And this is what's getting moved
00:12:14.307 --> 00:12:14.502 out.
00:12:15.292 --> 00:12:15.712 Charlie.
00:12:16.482 --> 00:12:21.550 I just tie it into that. The whole idea of squads and having
00:12:18.542 --> 00:12:18.892 Yeah.
00:12:21.550 --> 00:12:26.535 dedicated groups largely across a given PM makes it so much
00:12:26.535 --> 00:12:31.520 easier to do that right. Like I could make my own decisions
00:12:30.982 --> 00:12:31.522 Umm.
00:12:31.520 --> 00:12:36.256 about which of the little darlings to kill today instead
00:12:36.256 --> 00:12:41.490 of having to go begging to, you know, other projects and other
00:12:36.432 --> 00:12:37.052 Mm-hmm.
00:12:41.490 --> 00:12:46.392 clients and other PPM's. So just another plus one for the.
00:12:46.472 --> 00:12:48.022 Squad system. I'm loving it.
00:12:48.352 --> 00:12:50.782 Yeah. And I really do wish that the squads could be more
00:12:50.782 --> 00:12:53.382 tightened down to the individual PM that we used to do with.
00:12:54.972 --> 00:12:59.862 As a pods where it was 1:00 PM per pod or two pod, you know
00:12:59.862 --> 00:13:04.671 back in the day when it was Clint and I both had pod B, we
00:13:04.671 --> 00:13:05.812 could just go.
00:13:06.812 --> 00:13:10.232 But your knuckle brawl it if it needed to be some get kicked out
00:13:10.232 --> 00:13:10.442 but.
00:13:11.962 --> 00:13:14.887 Yeah, hopefully they will come soon where we can get it to be
00:13:14.887 --> 00:13:17.811 there or it's like Charlie's got squad one and two and he can
00:13:17.811 --> 00:13:20.548 kind of switch back and forth between the two of them and
00:13:20.548 --> 00:13:23.142 they're working as projects and maybe squad once more.
00:13:23.372 --> 00:13:26.972 A big on Project X and the other ones on Project et cetera.
00:13:27.852 --> 00:13:30.729 Someday, someday, keep on moving. Keep on putting that
00:13:30.729 --> 00:13:33.082 salt shaker back at the center of the table.
00:13:34.132 --> 00:13:34.472 Cool.
00:13:36.102 --> 00:13:36.482 OK.
00:13:37.442 --> 00:13:41.848 Any questions about that? It seems pretty clear. OK, so this
00:13:41.848 --> 00:13:46.255 difference here and burn down should be all this burned down
00:13:46.255 --> 00:13:50.589 should be is based on us. So like I said, that's the column
00:13:50.589 --> 00:13:55.212 that we gotta come after us. So if I see Scarlett is 4.75 hours
00:13:55.212 --> 00:13:59.402 behind on burn down, that's something that I know that we
00:13:59.402 --> 00:14:04.098 got to look at and it might seem a bit crazy because you're like
00:14:04.098 --> 00:14:08.576 she's only 3.75 hours behind on her burn up. Why do I have to
00:14:08.576 --> 00:14:09.732 move 4.75 hours.
00:14:10.452 --> 00:14:13.875 What that means is that there is just too much work in her
00:14:13.875 --> 00:14:15.732 Sprint. So if I open up scarlet.
00:14:17.452 --> 00:14:19.482 Here and I just go to all of her tickets.
00:14:24.032 --> 00:14:26.965 You know, we can take a look at these and then I'll organize my
00:14:26.965 --> 00:14:27.102 PM.
00:14:28.762 --> 00:14:31.875 And here we see that Amy and Clint. Ohh. And this little
00:14:31.875 --> 00:14:32.312 stinker.
00:14:33.352 --> 00:14:37.765 That's Amy now, but we're about that for now. We'd have to go
00:14:37.765 --> 00:14:42.391 through and see where that extra 3.75 hours came from. Now I can
00:14:42.391 --> 00:14:46.803 track it because I can look at this entered Sprint and we can
00:14:46.803 --> 00:14:47.942 see what got in.
00:14:49.332 --> 00:14:53.595 I see here. It looks like Amy did 2 hours of unplanned work.
00:14:53.595 --> 00:14:57.927 I'll completely on enter, so that's part 3.75 hours, and then
00:14:57.927 --> 00:15:01.980 there's just another hour .75 that got in here somewhere.
00:15:01.980 --> 00:15:06.312 Maybe she wasn't balance right off the bat. Maybe it was some
00:15:06.312 --> 00:15:10.715 other exceeds. Actually, it's that 2 hours. And then if we add
00:15:10.715 --> 00:15:12.252 that with the exceeds.
00:15:13.942 --> 00:15:16.652 Of two hours. And that's the same thing.
00:15:18.652 --> 00:15:21.492 OK, so it's only .75.
00:15:22.292 --> 00:15:25.362 That was uh over on the Sprint somewhere.
00:15:26.252 --> 00:15:29.429 So we can track this stuff. It's important. It's good. It's
00:15:29.429 --> 00:15:32.871 really helpful. And we have the data and we can use it. Jessica,
00:15:32.871 --> 00:15:33.242 go off.
00:15:35.892 --> 00:15:40.705 How do you guys decide how many hours to give to each developer?
00:15:40.705 --> 00:15:45.074 Is it kind of their experience? Is it just the size of the
00:15:45.074 --> 00:15:47.592 projects? Is it what? What is it?
00:15:48.232 --> 00:15:52.018 They're follow up question for you, do you mean full in the
00:15:48.402 --> 00:15:48.882 That he decided.
00:15:52.018 --> 00:15:54.542 Sprint or do you mean like per project?
00:15:55.062 --> 00:15:55.882 Both I guess.
00:15:56.352 --> 00:15:59.983 Sure. So fall in the Sprint is between the developer and
00:15:59.983 --> 00:16:03.869 they're hiring agreement. So you'll see most developers have
00:16:03.869 --> 00:16:04.442 a 7 hour.
00:16:04.572 --> 00:16:05.172 Umm.
00:16:06.602 --> 00:16:11.248 Daily capacity. Some developers work with leadership during
00:16:11.248 --> 00:16:16.280 their hiring agreements or even as they go on, maybe comes up in
00:16:16.280 --> 00:16:19.532 a quarterly to have a different capacity.
00:16:20.822 --> 00:16:24.689 And that, as always, will be between them them and those that
00:16:21.022 --> 00:16:21.372 Got it.
00:16:24.689 --> 00:16:27.994 pay their bills. Nothing. Nothing to do with us. UM,
00:16:25.402 --> 00:16:25.852 Mm-hmm.
00:16:27.994 --> 00:16:28.992 second question.
00:16:30.112 --> 00:16:34.982 What we do is mix the two, so we use that 1:00 PM dev allocation.
00:16:36.342 --> 00:16:39.612 And this is kind of where we we really need to get better at.
00:16:39.772 --> 00:16:40.502 Umm.
00:16:41.722 --> 00:16:45.523 More specific, uh, forecasting right where let's say that we
00:16:45.523 --> 00:16:49.449 have 100 hour project, 200 hour projects, 100 hour project and
00:16:49.449 --> 00:16:53.375 let's say we have Scarlett in there and Amy goes. Yo Daniel, I
00:16:53.375 --> 00:16:56.740 got this $100 project. It's using these two Erps that
00:16:56.740 --> 00:17:00.665 Scarlett already knows. I love working with her. Can I get her
00:17:00.665 --> 00:17:04.529 on there? We can then take a look at it and we can either say
00:17:04.529 --> 00:17:08.143 oh look, another project is winding down which be able to
00:17:08.143 --> 00:17:12.007 slot that in or maybe we'll just be like, hey, we can't quite
00:17:12.007 --> 00:17:12.692 foot it in.
00:17:12.762 --> 00:17:15.119 Right now to do say 20 hours of project, let's start off with
00:17:15.119 --> 00:17:17.552 10, tell the client that we have a little bit of a slow ramp up
00:17:17.552 --> 00:17:19.947 on it. But then in two weeks or whatever, we should be able to
00:17:19.947 --> 00:17:22.342 go full and for that 40 hours, a Sprint or whatever it may be.
00:17:23.912 --> 00:17:26.243 And then plan that out for say two or three sprints or that may
00:17:26.243 --> 00:17:26.352 be.
00:17:27.602 --> 00:17:28.102 Got it.
00:17:28.872 --> 00:17:29.082 Well.
00:17:29.092 --> 00:17:32.370 Which makes it really difficult with the exceeds right and also
00:17:32.370 --> 00:17:35.444 with kind of ongoing projects that don't have firm planning
00:17:35.444 --> 00:17:36.622 because then it's like.
00:17:37.812 --> 00:17:42.023 You know, I guess I'll put 20 hours in there and see what
00:17:42.023 --> 00:17:46.379 happens. And a lot of those numbers that we do do just come
00:17:46.379 --> 00:17:46.742 from.
00:17:47.922 --> 00:17:51.042 Come from the last Sprint and then checking in with folks. So
00:17:51.042 --> 00:17:54.112 like I know like hassling try like hey, how much time do you
00:17:54.112 --> 00:17:57.031 think for CMMC for these guys? And he was like, oh, look,
00:17:57.031 --> 00:18:00.252 Brent's done let's CMMC for now. But I'm definitely need Jeremy
00:18:00.252 --> 00:18:03.322 et cetera. So like cool. Let's get Brent off of this for our
00:18:03.322 --> 00:18:06.392 allocation and let's get him some new projects where he went
00:18:06.392 --> 00:18:07.952 over to Andrew Robe with Laura.
00:18:11.422 --> 00:18:12.752 All right. Thank you.
00:18:12.212 --> 00:18:12.772 Makes sense?
00:18:13.922 --> 00:18:17.428 Coca-Cola and just so you guys know with that that is our best
00:18:17.428 --> 00:18:17.762 guess.
00:18:19.182 --> 00:18:22.362 We are also talking about kind of doing a similar thing.
00:18:23.042 --> 00:18:26.378 With you guys, so you can kind of make your requests for
00:18:26.378 --> 00:18:29.596 people. We can do our tabulations and then like, let's
00:18:29.596 --> 00:18:33.341 say, because I'm not, Charlie, if he had his druthers, he'd say
00:18:33.341 --> 00:18:37.028 cool. Just give me 40 hours of JLR time. So I don't have to do
00:18:37.028 --> 00:18:40.539 all this, exceeds, et cetera time and then we would be able
00:18:40.539 --> 00:18:44.051 to look at that and say like, OK, look, he really does need
00:18:44.051 --> 00:18:45.572 this 40 hours of JLR time.
00:18:52.542 --> 00:18:53.712 Cool. OK.
00:18:55.832 --> 00:18:59.083 Back to this. OK, so that's that completed work expected total
00:18:59.083 --> 00:19:01.818 work. The difference that it burned down story point
00:19:01.818 --> 00:19:04.708 percentage completion and then let's take a look at the
00:19:04.708 --> 00:19:07.082 reporting show you guys what we do for y'all.
00:19:23.452 --> 00:19:23.872 OK.
00:19:24.582 --> 00:19:27.644 Has a report that goes out. We take a look at the story, point
00:19:27.644 --> 00:19:30.706 completion by developer. Like I said, we do it for that Sprint
00:19:30.706 --> 00:19:33.428 and then the three Sprint average so we can kind of see
00:19:33.428 --> 00:19:34.352 what it looks like.
00:19:35.672 --> 00:19:38.488 We look at the story point completion by PM like again
00:19:38.488 --> 00:19:41.560 that's so we can see how many story points are going in and
00:19:41.560 --> 00:19:44.632 how much are coming out over individual Sprint three Sprint
00:19:44.632 --> 00:19:45.042 average.
00:19:46.262 --> 00:19:49.483 Look at the story point completion by project. So this
00:19:49.483 --> 00:19:52.997 is ticketed work that has blue levels that's going into the
00:19:52.997 --> 00:19:56.452 sprints so we can see how much came in, how much came out.
00:19:59.062 --> 00:20:02.909 Then we look at the burn up chart and exceeds by estimate
00:20:02.909 --> 00:20:07.020 chart per squad. So we can say hey squad one look this Sprint
00:20:07.020 --> 00:20:08.612 they had a great little.
00:20:10.042 --> 00:20:13.595 Burn up right only an hour and a quarter behind. That's bad asss.
00:20:13.595 --> 00:20:16.340 That makes me so stoked. You know, 39% story point
00:20:16.340 --> 00:20:19.354 completion. Not the best. 39% exceeds not the best, but
00:20:19.354 --> 00:20:22.799 they're burnt up was really on point. So I can look at that and
00:20:22.799 --> 00:20:26.083 go, hey, maybe we need to get more concrete story points for
00:20:26.083 --> 00:20:29.420 the developers so we can see what they're doing, what's going
00:20:29.420 --> 00:20:32.273 on, make sure that we're following generational push
00:20:32.273 --> 00:20:32.542 pull.
00:20:33.962 --> 00:20:34.702 And the like.
00:20:36.482 --> 00:20:39.022 But then you know, we can just take a look at this. This is all
00:20:39.022 --> 00:20:41.522 historical. We have it for every Sprint going back for months.
00:20:43.572 --> 00:20:46.700 Here we have another new field we're doing, where it's just if
00:20:46.700 --> 00:20:49.579 someone had high confidence on the task and they exceeded
00:20:49.579 --> 00:20:52.012 estimates, what was up, what's going on with it?
00:20:54.132 --> 00:20:56.857 And then there's the general confidence level per developer.
00:20:56.857 --> 00:20:59.537 So we can kind of see where they're feeling at it. And this
00:20:59.537 --> 00:21:02.173 is gonna help us make sure that the developers are getting
00:21:02.173 --> 00:21:04.898 training where they need on specific things and how they can
00:21:04.898 --> 00:21:05.702 get trained on it.
00:21:07.622 --> 00:21:08.672 And that's every Sprint.
00:21:10.882 --> 00:21:11.842 Cool. OK.
00:21:13.822 --> 00:21:16.759 Any other questions about Azure? I know, Charlie, you did,
00:21:16.759 --> 00:21:19.944 Charlie. You asked me just kind of general questions about this
00:21:19.944 --> 00:21:22.532 chart, right? Did that answer all of those for you?
00:21:21.492 --> 00:21:24.271 Oh, it's super cool. Yeah. Yeah, yeah, yeah, it's awesome. Thank
00:21:23.462 --> 00:21:23.902 OK.
00:21:24.271 --> 00:21:24.442 you.
00:21:24.772 --> 00:21:28.122 Cool. And then, Jessica, you have questions about the chart
00:21:28.122 --> 00:21:31.082 and about Azure and general, did I get all of those?
00:21:32.442 --> 00:21:34.112 The chart, yes, that I.
00:21:35.032 --> 00:21:39.568 I'm getting there with that this this helped it. This explained a
00:21:36.432 --> 00:21:36.832 OK.
00:21:39.568 --> 00:21:42.592 lot of it that you that I was asking about.
00:21:42.672 --> 00:21:43.172 Umm.
00:21:43.002 --> 00:21:43.632 OK.
00:21:45.992 --> 00:21:47.462 Azure in general.
00:21:51.952 --> 00:21:54.794 Can you? Can you just walk through how to find this view
00:21:54.794 --> 00:21:57.886 right here? Because I like this view and I want to be able to
00:21:55.572 --> 00:21:56.072 Yeah.
00:21:57.886 --> 00:22:00.877 find it and look at it when I need it and pin it so I don't
00:22:00.742 --> 00:22:01.212 Sure.
00:22:00.877 --> 00:22:04.069 have to dig for it cuz I'm still slow and finding the different
00:22:04.069 --> 00:22:06.412 views queries I have down no problem but this.
00:22:04.692 --> 00:22:05.182 Totally.
00:22:05.852 --> 00:22:09.412 I heard I saw your post that that's great. So this is just.
00:22:08.762 --> 00:22:10.512 Yeah. Jessica is the query queen.
00:22:10.662 --> 00:22:14.176 Hell yeah. Now, Jessica, have you got them integrated into
00:22:14.176 --> 00:22:14.772 Excel yet?
00:22:15.812 --> 00:22:19.794 So I do have a video that I think I can't remember if it was
00:22:19.794 --> 00:22:21.622 Trent or Amy that shared it.
00:22:23.542 --> 00:22:27.881 On how to move things over to excel, but no, I don't have them
00:22:27.682 --> 00:22:27.932 OK.
00:22:27.881 --> 00:22:30.842 there just yet. Actually, no, I did. I do.
00:22:29.182 --> 00:22:32.993 Kyle Kyle change we had to do it like 2 1/2 years ago and it
00:22:32.993 --> 00:22:33.992 changed my life.
00:22:33.842 --> 00:22:36.427 Queries. Yes I do, because then I can go filter and I can change
00:22:36.427 --> 00:22:38.814 it. And I I did do that. I did something with Trent earlier
00:22:38.814 --> 00:22:41.120 this morning on it, but this view I like when you guys do
00:22:39.612 --> 00:22:40.102 Hell yeah.
00:22:41.120 --> 00:22:43.626 this and I wanna see. Hey, the developers. If I'm working with
00:22:43.542 --> 00:22:43.802 OK.
00:22:43.626 --> 00:22:45.933 Debbie and Brendan out of project do I need to pull KB do
00:22:45.933 --> 00:22:47.842 need pre Brendan like I just need to know like.
00:22:47.422 --> 00:22:47.982 Umm.
00:22:48.512 --> 00:22:49.572 OK. So yes.
00:22:49.482 --> 00:22:53.937 So open up your once you drop me a link about where you're at on
00:22:53.937 --> 00:22:56.952 the board right now in Azure, I should say.
00:22:57.182 --> 00:23:00.375 Ohh I have queries opened up everywhere so I'm just gonna
00:22:59.272 --> 00:23:00.392 OK. Yeah.
00:23:00.375 --> 00:23:02.632 start from the beginning and follow you.
00:23:01.392 --> 00:23:01.822 OK.
00:23:03.102 --> 00:23:05.742 Yeah. No, drop me like where you are. So that together. Or how
00:23:05.742 --> 00:23:08.214 about you share your screen instead of me sharing mine and
00:23:08.214 --> 00:23:09.052 we can help you out.
00:23:11.682 --> 00:23:14.922 No, that's going to be crazy, because I'm like, oh, no, a
00:23:14.922 --> 00:23:18.553 little down, a little left. I'll drive. Yeah. OK. So if you open
00:23:14.972 --> 00:23:17.226 Yeah, I don't do that. I'll just. I'll follow you. I'll
00:23:17.226 --> 00:23:18.112 follow you. It's fine.
00:23:18.553 --> 00:23:21.961 up the side, I do like to keep this minimized at all points,
00:23:21.961 --> 00:23:23.972 but open this bad boy up over here.
00:23:25.832 --> 00:23:27.152 I think you hit the sprints button.
00:23:30.062 --> 00:23:31.582 And that should give you this view here.
00:23:33.222 --> 00:23:37.152 OK. And you hit this all project backlog sprints?
00:23:34.242 --> 00:23:34.522 OK.
00:23:42.972 --> 00:23:45.962 And that will generally bring you to the most recent spread.
00:23:47.722 --> 00:23:47.992 Mm-hmm.
00:23:48.802 --> 00:23:51.872 So we're here to make sure you have the task board selected.
00:23:53.722 --> 00:23:54.762 And gives you this view.
00:23:53.972 --> 00:23:54.272 OK.
00:23:55.252 --> 00:23:55.672 Yep.
00:23:56.052 --> 00:24:00.033 And then also I always say just First things first open up this
00:24:00.033 --> 00:24:03.702 here for view options, make sure work details is selected.
00:24:05.462 --> 00:24:08.552 And that your grouping it by the stories, not by the people.
00:24:10.322 --> 00:24:11.422 Let me know when you're there.
00:24:13.762 --> 00:24:16.572 I lost you at grouping. I did the work details but the group
00:24:15.342 --> 00:24:15.622 OK.
00:24:16.572 --> 00:24:19.152 ohh grouping by stories. OK, I already have that great.
00:24:18.002 --> 00:24:18.442 Mm-hmm.
00:24:19.102 --> 00:24:21.952 Cool. And then you're gonna hit this little filter friend.
00:24:23.232 --> 00:24:23.612 OK.
00:24:24.072 --> 00:24:27.156 And that little filter friend is your best friend. And then I
00:24:27.156 --> 00:24:29.742 always minimize this. I want more screen less menu.
00:24:31.122 --> 00:24:34.002 And I can always open it up if I need to see things again. But.
00:24:33.912 --> 00:24:34.542 God.
00:24:35.602 --> 00:24:39.230 Get rid of that. So now, once you're here in this keyword
00:24:39.230 --> 00:24:42.732 filter by thing, you can type whatever you want, right?
00:24:42.612 --> 00:24:42.892 Umm.
00:24:43.972 --> 00:24:49.853 If I put bid and Sacco, it's gonna bring me just Justin's
00:24:49.853 --> 00:24:51.982 tasks for bid, right?
00:24:53.742 --> 00:24:58.021 Whether they're in the area path or not, it's the most robust use
00:24:58.021 --> 00:25:02.106 of everything here. Now you can get this information like five
00:25:02.106 --> 00:25:05.801 or six different ways, but really I would just always do
00:25:05.801 --> 00:25:09.432 the filter by keyword type in the name and the project.
00:25:10.492 --> 00:25:13.612 And I'll get you to the very specific thing. So if I do this
00:25:13.612 --> 00:25:16.732 without any querying without any fancy tools, I can say that
00:25:16.732 --> 00:25:19.699 Justin Sacco has four and 1/4 hours on Branford group for
00:25:19.699 --> 00:25:20.722 auditing. That's it.
00:25:21.892 --> 00:25:26.540 Could also say if I do WBS in here, I could say that there's
00:25:26.540 --> 00:25:28.902 only 21.25 hours that's active.
00:25:29.682 --> 00:25:32.959 Remember these little numbers you see at the top here? This
00:25:32.959 --> 00:25:34.652 doesn't include completed work.
00:25:35.402 --> 00:25:38.279 Closed work or anything like that. This is just what's active
00:25:38.279 --> 00:25:39.392 in the Sprint right now.
00:25:40.402 --> 00:25:43.908 So I could do the math and tabulate here how much work has
00:25:43.908 --> 00:25:47.710 been completed on it, but I know for a fact there's 21.25 hours
00:25:47.710 --> 00:25:48.542 left in there.
00:25:56.732 --> 00:26:00.074 Yeah. So that's amazing types. Like I say, you won't use that
00:26:00.074 --> 00:26:03.363 too often unless you're just looking for, like let's say you
00:26:03.363 --> 00:26:03.902 want bugs.
00:26:04.762 --> 00:26:07.532 For Dobbs, or whatever, none have a bid.
00:26:08.902 --> 00:26:11.904 Of the see all the bugs, but it won't show you the tasks
00:26:11.904 --> 00:26:15.116 associated with them, so it's kind of a drag. But then could
00:26:15.116 --> 00:26:18.380 also put in here to a failures and tasks and they'll show you
00:26:18.380 --> 00:26:21.593 all the bugs for bid. If you needed to do that in the Sprint
00:26:21.593 --> 00:26:24.805 view. Again, not the most useful because now when I did that
00:26:24.805 --> 00:26:28.122 tasks, it also brought in all the user stories, so don't worry
00:26:28.122 --> 00:26:28.912 about this one.
00:26:30.272 --> 00:26:33.937 Assigned to is a quick way for the same thing. Let's say you
00:26:33.937 --> 00:26:37.721 have more controls. Let's say you want to say Brent everything
00:26:37.721 --> 00:26:38.202 on West.
00:26:39.382 --> 00:26:41.972 That has to do with contacts.
00:26:43.832 --> 00:26:45.062 You can refine, refine, refine.
00:26:46.232 --> 00:26:49.092 States. Again. Yeah. No, no, no, please.
00:26:46.442 --> 00:26:49.426 This isn't ohh. I'm sorry. I'm sorry this is this is
00:26:49.426 --> 00:26:51.622 essentially a query, just more visual.
00:26:53.512 --> 00:26:55.302 And the queries you can save which.
00:26:54.432 --> 00:26:55.122 And quicker.
00:26:56.352 --> 00:26:56.762 Yes.
00:26:57.542 --> 00:27:01.517 Where is our very quick, but this will give you just that
00:27:01.517 --> 00:27:05.904 real time information right now, which is also annoying because
00:27:03.012 --> 00:27:03.262 Right.
00:27:05.904 --> 00:27:10.291 it also you can also edit things here right? Like let's say for
00:27:10.291 --> 00:27:10.702 Brent.
00:27:11.392 --> 00:27:15.160 I had a 2 hour meeting scheduled with him in the future and then
00:27:15.160 --> 00:27:18.812 my client cancelled. I can just quick change that in here, you
00:27:18.812 --> 00:27:19.102 know.
00:27:20.262 --> 00:27:22.412 Richard from whoops.
00:27:24.572 --> 00:27:25.542 3.5 OK.
00:27:36.752 --> 00:27:39.389 Cool. So that's here. Everything's here. Anyone have
00:27:39.389 --> 00:27:42.425 any questions? Other questions about Azure in general or the
00:27:42.425 --> 00:27:43.022 Sprint view?
00:27:53.882 --> 00:27:56.602 OK, so let's say we wanted to add.
00:28:00.062 --> 00:28:04.042 A four hour task to Brendan Flaherty Sprint.
00:28:04.872 --> 00:28:06.022 Is that possible, Trenton?
00:28:11.342 --> 00:28:16.626 Hold on. I'm looking. There he is. No, it would put him over by
00:28:12.732 --> 00:28:13.752 Yeah, yeah. Take your.
00:28:16.626 --> 00:28:17.452 two hours.
00:28:18.062 --> 00:28:19.722 Awesome 100%.
00:28:21.472 --> 00:28:24.774 So what Trenton did here is he just looked at these bars. We
00:28:24.774 --> 00:28:28.185 saw how much time they have in the Sprint. So burned. Flaherty
00:28:28.185 --> 00:28:31.758 has 75 of 77 hours. He's 2 hours ahead on his burned down. Great.
00:28:31.758 --> 00:28:32.462 Happy for it.
00:28:34.002 --> 00:28:37.534 That's a bit of a trick question there though. Trying to cuz we
00:28:37.534 --> 00:28:40.625 can take a look at Brendan Flaherty Sprint and although
00:28:40.625 --> 00:28:42.502 there's only the two hours there.
00:28:43.832 --> 00:28:46.822 We see that we also have 34 hours of balancing tickets.
00:28:48.862 --> 00:28:52.292 Hardy har har har har, so balancing tickets everybody.
00:28:54.212 --> 00:28:57.688 Let's get to that for just a second. Just because it's
00:28:57.688 --> 00:29:01.670 something I don't think everyone has. Uh, the full scope on it
00:29:01.670 --> 00:29:04.830 on. So if a ticket is a balancing, you'll see CVI
00:29:04.830 --> 00:29:08.495 balancing there and the user's name. This is time that is
00:29:08.495 --> 00:29:10.012 completely up for grabs.
00:29:11.482 --> 00:29:14.626 If Charlie had 17 hours for Taylor on bid, he could put that
00:29:14.626 --> 00:29:17.770 in there right now because of the talk to anybody other than
00:29:17.770 --> 00:29:20.863 Taylor. Probably to make sure that he knows it's coming in.
00:29:20.863 --> 00:29:23.182 But it's just there. Go for it. Go hog wild.
00:29:24.732 --> 00:29:25.672 That's all for grabs.
00:29:26.792 --> 00:29:30.601 If you get to it first believe for you. It's fantastic. So what
00:29:30.601 --> 00:29:34.172 you do when you want to reduce someone's balancing is gonna
00:29:34.172 --> 00:29:37.446 create them a new ticket, hopefully associated to user
00:29:37.446 --> 00:29:41.196 story. But if it's kind of an unplanned work, one you can just
00:29:41.196 --> 00:29:42.862 create the individual tasks.
00:29:44.282 --> 00:29:48.560 And then you'll reduce this. By the time you add it. So if I
00:29:48.560 --> 00:29:53.119 added a 7 hour task for Taylor, I would just reduce this down to
00:29:53.119 --> 00:29:54.592 10 and call it a day.
00:29:56.482 --> 00:29:59.540 So I don't ever wanna see completed work in any of the
00:29:59.540 --> 00:30:02.765 bucket tickets like this for balancing because that means
00:30:02.765 --> 00:30:06.435 that someone just kind of taking advantage of time. I'd rather be
00:30:06.435 --> 00:30:09.938 associated to a specific task so that we can see what the time
00:30:09.938 --> 00:30:13.107 was spent on doing and goal would be for EP and Azure to
00:30:13.107 --> 00:30:15.832 essentially be a one to one for most developers.
00:30:19.672 --> 00:30:19.942 Cool.
00:30:23.402 --> 00:30:26.481 Clint, do you have any tips or tricks for Azure? What are your
00:30:26.481 --> 00:30:28.582 thoughts on it? You love Azure. It's fast.
00:30:28.502 --> 00:30:34.245 The and granted this Stephanie taught me this one, querying for
00:30:34.245 --> 00:30:35.232 a specific.
00:30:35.972 --> 00:30:36.782 Sprint.
00:30:37.572 --> 00:30:41.474 Which is really just as simple as iteration path equals this
00:30:41.474 --> 00:30:41.922 Sprint.
00:30:42.652 --> 00:30:46.257 Area path equals the project will allow you to see all of the
00:30:46.257 --> 00:30:46.722 tickets.
00:30:47.572 --> 00:30:51.979 For that Sprint, the reason why that can be important is you can
00:30:51.979 --> 00:30:53.742 direct export that to CSV.
00:30:54.772 --> 00:30:55.062 Hmm.
00:30:56.322 --> 00:30:59.134 And you can send that to the client. The only downside I'll
00:30:59.134 --> 00:31:01.102 I'll call out. That's really annoying is.
00:31:02.402 --> 00:31:06.820 I can't find a way to export to an Excel and CSV's don't allow
00:31:06.820 --> 00:31:08.152 you to format them.
00:31:09.312 --> 00:31:12.902 So it's a little annoying, but you can just resave it as a or.
00:31:09.442 --> 00:31:09.942 Ohh.
00:31:14.262 --> 00:31:15.822 Bring over the information too.
00:31:16.682 --> 00:31:17.112 Uh.
00:31:19.342 --> 00:31:22.981 Excel. I don't know the way to you can open an excel but then
00:31:21.472 --> 00:31:21.962 So you.
00:31:22.981 --> 00:31:25.152 it tries to do this. So weird thing.
00:31:23.412 --> 00:31:24.222 Do you just?
00:31:25.572 --> 00:31:27.602 Do you just do like this Clint?
00:31:28.692 --> 00:31:31.822 Umm yeah, so I don't.
00:31:30.932 --> 00:31:33.642 You do that and you're just doing export to CSV.
00:31:34.222 --> 00:31:37.823 Correct. Now if when you open that query, what's gonna happen?
00:31:37.823 --> 00:31:41.481 Because it happens to me all the time. If you wanna like. Yeah,
00:31:41.481 --> 00:31:45.139 you can like, format that right. And you change, you make it so
00:31:45.139 --> 00:31:48.739 it's all viewable and then you save the file. Yeah. You put it
00:31:48.739 --> 00:31:52.454 in the table. Ohh, it's so nice. Ohh, look how pretty it is. And
00:31:52.332 --> 00:31:52.722 Mm-hmm.
00:31:52.454 --> 00:31:55.312 then you save it and then you exit and reopen it.
00:31:56.142 --> 00:31:57.072 Kind of that saves.
00:31:57.932 --> 00:32:00.122 Did you just do the save as and then do it as an Excel?
00:32:00.932 --> 00:32:03.382 Yeah. So you have to make sure it's formatted as an Excel.
00:32:06.132 --> 00:32:09.010 It took me like an hour of fiddling around with it before I
00:32:09.010 --> 00:32:11.072 realized it's just cause the see has been.
00:32:10.412 --> 00:32:12.142 Ohh, got it. Yeah, yeah.
00:32:13.012 --> 00:32:15.815 I just want to call it out because you'll end up sending a
00:32:15.815 --> 00:32:18.524 file that you think Ohh formatted it all nicely and then
00:32:17.532 --> 00:32:18.492 It looks so nice.
00:32:18.524 --> 00:32:21.374 the client opens it up and it's like what? What happened to
00:32:20.122 --> 00:32:20.692 Garbage.
00:32:20.372 --> 00:32:23.927 Ah, that makes total sense. I was on a call with Trenton
00:32:21.374 --> 00:32:21.612 this?
00:32:23.732 --> 00:32:24.192 Yep.
00:32:23.927 --> 00:32:28.043 earlier because I was working on cleaning up athlete tickets that
00:32:28.043 --> 00:32:31.598 have been there. That can probably closed out or removed
00:32:31.598 --> 00:32:35.652 or something, and I worked on it for an hour, hour and a half on
00:32:35.652 --> 00:32:39.581 2 hours on Wednesday, I opened it back up yesterday and it was
00:32:39.581 --> 00:32:43.447 all gone. I was like, wait a minute, where is it? I worked on
00:32:43.447 --> 00:32:47.501 this. There was stuff in there I promised I saved it and it's no
00:32:47.501 --> 00:32:49.372 longer here. That makes sense.
00:32:50.772 --> 00:32:54.933 And like I'll, I'll just show real quick my screen if people
00:32:54.933 --> 00:32:56.092 with that Daniel.
00:32:56.832 --> 00:32:57.312 Please do.
00:32:57.142 --> 00:32:59.192 So after I.
00:33:01.332 --> 00:33:05.674 After I export to CSV which again you have to reformat it
00:33:05.674 --> 00:33:10.166 into an Excel, you can come in here and just put totals for
00:33:10.166 --> 00:33:14.508 like add in QA EM meetings separately. I like adding them
00:33:14.508 --> 00:33:15.182 together.
00:33:16.902 --> 00:33:20.051 I like adding them together because it makes it easier for
00:33:20.051 --> 00:33:21.172 the client to accept.
00:33:21.992 --> 00:33:25.261 When you put project management, it's something, but it's like
00:33:25.261 --> 00:33:26.662 ohh yeah, four hours of QA.
00:33:27.972 --> 00:33:32.326 4 hours of PM 29 hours of meetings, whatever. And then you
00:33:32.326 --> 00:33:33.802 just sell it all up.
00:33:36.232 --> 00:33:40.051 Probably walk quicker way of doing this and it's like cool
00:33:40.051 --> 00:33:42.122 your project this Sprint period.
00:33:43.542 --> 00:33:47.591 1216 and if you want, you could even put the full like Sprint in
00:33:47.591 --> 00:33:51.454 the title when you save it. The client can get a quick export
00:33:51.454 --> 00:33:51.952 view of.
00:33:53.112 --> 00:33:56.670 Here's your think. Here's the Lee hours are gonna spend, you
00:33:56.670 --> 00:34:00.402 know, like, reformat it our best you can so that it looks good.
00:34:01.612 --> 00:34:02.102 But.
00:34:02.812 --> 00:34:05.463 This is a quick way to clients can get an understanding. Hey,
00:34:05.463 --> 00:34:07.858 you're going to use 18 hours because often that's where
00:34:07.858 --> 00:34:09.782 clients get so confused. It's like we spent.
00:34:10.692 --> 00:34:13.362 29 hours how it's like well.
00:34:14.932 --> 00:34:15.562 Yeah.
00:34:17.662 --> 00:34:18.312 Here's why.
00:34:21.532 --> 00:34:25.422 This is just a useful way of like and. It's also good for
00:34:25.422 --> 00:34:29.179 your own sanity. I often misunderstand how many hours I
00:34:29.179 --> 00:34:30.252 put in a Sprint.
00:34:31.512 --> 00:34:35.371 And then I'll go into invoicing and Crystal will be like Yep,
00:34:35.371 --> 00:34:39.105 project went from 50 hours to five. It's like what, how and
00:34:39.105 --> 00:34:41.532 then I look at it, it's like ohh yeah.
00:34:42.262 --> 00:34:43.842 I did put that many hours in.
00:34:46.572 --> 00:34:49.542 That's my only thing is use queries as best you can.
00:34:50.212 --> 00:34:50.492 Yeah.
00:34:52.422 --> 00:34:54.932 Charlie, you have any specific tips for the for the new game?
00:34:56.592 --> 00:35:01.170 So one thing that helps me a lot and I I am forever in Azure. I
00:35:01.170 --> 00:35:04.532 generally keep 5 Azure tabs open at all times.
00:35:03.882 --> 00:35:04.372 Yeah.
00:35:05.152 --> 00:35:11.174 Umm I have a backlog query that I use for every project that
00:35:11.174 --> 00:35:15.222 shows me all of the open remaining work.
00:35:16.702 --> 00:35:21.388 I use the Sprint view that that you guys just went through
00:35:21.388 --> 00:35:25.994 setting up a minute ago, but I keep two tabs open of that
00:35:25.994 --> 00:35:30.839 current Sprint and next Sprint so that if like all the stuff
00:35:30.839 --> 00:35:35.763 that I needed to move out of bid today to accommodate Michael
00:35:35.763 --> 00:35:40.766 going over on another ticket, I move those to the next Sprint.
00:35:40.766 --> 00:35:45.849 And I already have sort of ready access there to what's shaping
00:35:45.849 --> 00:35:48.152 up for the next sprints work.
00:35:48.292 --> 00:35:51.816 Particularly the Monday or Tuesday at the end of a Sprint
00:35:51.816 --> 00:35:55.826 when I'm sweating it like what's gonna get done, what's gonna get
00:35:55.826 --> 00:35:59.653 kicked? What are they working on? Being able to just have that
00:35:59.653 --> 00:36:02.752 open in two separate tabs I find to be a big help.
00:36:03.292 --> 00:36:03.792 Hmm.
00:36:08.422 --> 00:36:12.908 And that's, I mean other than the exports and you know I do my
00:36:12.908 --> 00:36:17.394 my ticket compliance by running through an export and updating
00:36:17.394 --> 00:36:20.242 in Excel and then importing it back in.
00:36:22.162 --> 00:36:25.272 So I I I think that those are really the high points.
00:36:26.552 --> 00:36:30.719 There's also like between looking at it on a screen and
00:36:30.719 --> 00:36:35.036 then the 20 tab pivot tabled spreadsheet that Daniel just
00:36:35.036 --> 00:36:36.152 showed us like.
00:36:37.372 --> 00:36:40.536 Excel is a fantastically powerful piece of business
00:36:40.536 --> 00:36:43.883 software. It was ungodly expensive when it debuted and
00:36:43.883 --> 00:36:47.777 companies were like, yes, I'll have that because it can just do
00:36:47.777 --> 00:36:51.671 so much and all they've done for the last what? What's a bit? I
00:36:48.412 --> 00:36:48.892 Yeah.
00:36:51.671 --> 00:36:54.592 don't know, 40 years maybe since that came out.
00:36:54.372 --> 00:36:55.412 Something like that, I mean.
00:36:55.832 --> 00:37:00.282 They've just made it better and so the more you know about
00:37:00.282 --> 00:37:05.259 Excel, the more you can get data working for you and and and then
00:37:05.259 --> 00:37:08.502 you can be a nerd like Daniel and like me.
00:37:10.182 --> 00:37:13.676 You wanna be more like Daniel, but still, it's, yeah, it's it's
00:37:11.972 --> 00:37:13.522 No, you're cooler.
00:37:13.676 --> 00:37:16.842 just, I don't know. It's a rabbit hole, but it's a it's a
00:37:16.842 --> 00:37:17.552 beneficial 1.
00:37:19.072 --> 00:37:22.222 Yeah, I can't suggest that enough. Like spending a little
00:37:22.222 --> 00:37:22.982 time on there.
00:37:24.222 --> 00:37:26.614 The little Udemy course, it's one of those things that just
00:37:26.614 --> 00:37:27.172 helps you and.
00:37:28.232 --> 00:37:31.387 I think Clint was asking me a question about Excel in general
00:37:31.387 --> 00:37:34.593 and like of all the weirdo jobs that have my whole life, Azure
00:37:34.593 --> 00:37:37.799 or Excel is probably the only one thing that's been consistent
00:37:37.799 --> 00:37:38.562 the whole time.
00:37:39.362 --> 00:37:39.822 Yeah.
00:37:40.602 --> 00:37:41.842 Learn it. Use it.
00:37:42.652 --> 00:37:43.322 So.
00:37:44.102 --> 00:37:47.552 So what I wind up with is in the mid queries section.
00:37:47.532 --> 00:37:48.252 OK, cool.
00:37:56.922 --> 00:37:57.302 Sure.
00:37:57.352 --> 00:38:01.843 I have a backlog query for every project so I can just hit my
00:38:01.843 --> 00:38:06.407 queries and hit one more link and and and I'm at the open work
00:38:04.162 --> 00:38:04.912 Well, that's great.
00:38:06.407 --> 00:38:11.115 for JBM. I also find collapse it and then expand and you get the
00:38:11.115 --> 00:38:15.461 feature view that's so much easier than being like and then
00:38:12.952 --> 00:38:13.472 Yeah.
00:38:15.461 --> 00:38:20.097 I'll collapse this one and then this one and then you know like
00:38:19.272 --> 00:38:20.242 Hmm.
00:38:20.097 --> 00:38:22.922 using that just saves a bunch of time.
00:38:22.882 --> 00:38:23.572 Yes.
00:38:24.102 --> 00:38:31.032 Umm. And then and then I have a query for blocked tickets.
00:38:25.132 --> 00:38:26.262 That's really smart, dude.
00:38:31.892 --> 00:38:36.841 Uh it Nope. I don't need the editor there. I have a query for
00:38:36.841 --> 00:38:42.030 code complete and what I have in the code complete query is like
00:38:39.122 --> 00:38:39.482 Yeah.
00:38:42.030 --> 00:38:46.739 I every task that's within a code complete item that's not
00:38:46.739 --> 00:38:51.768 closed or removed. I have show because like OK this story this
00:38:51.768 --> 00:38:56.956 bug is in code complete but it's clearly not done because it has
00:38:56.956 --> 00:38:58.952 an active task within it.
00:38:57.792 --> 00:38:58.502 Hmm.
00:39:00.382 --> 00:39:04.363 And that task is in the backlog, which is interesting and the the
00:39:00.692 --> 00:39:01.212 What else?
00:39:04.363 --> 00:39:05.992 user story was in November.
00:39:07.312 --> 00:39:11.923 Damn it, I lost it. Ohm, let me get. Yeah. And so. Yeah. So we
00:39:08.752 --> 00:39:09.162 Uh-huh.
00:39:10.692 --> 00:39:11.412 Oh, oh oh.
00:39:11.923 --> 00:39:16.681 wound up like what this tells me is. Yeah, in November we worked
00:39:16.681 --> 00:39:21.073 on it, and then it failed QA at some later date. And that's
00:39:21.073 --> 00:39:25.391 when. OK, now we've put it back in because we found it not
00:39:25.391 --> 00:39:29.710 working. I think that's what that means, but it's at least
00:39:29.302 --> 00:39:29.642 Yeah.
00:39:29.710 --> 00:39:34.248 worthy of buzz and Michael and saying, is this like, really a
00:39:34.248 --> 00:39:37.322 deal? Is this out here or did you fix it?
00:39:37.402 --> 00:39:41.642 And you did it outside a ticket like how? How did we get here?
00:39:39.722 --> 00:39:40.172 Mm-hmm.
00:39:43.192 --> 00:39:44.162 And.
00:39:46.892 --> 00:39:48.722 I've fooled around with.
00:39:48.752 --> 00:39:50.802 As for projection like next sprints work.
00:39:51.722 --> 00:39:53.012 Yes.
00:39:54.852 --> 00:39:58.428 But it's this is one that I've fooled with, but I don't like. I
00:39:58.132 --> 00:39:58.552 Yeah.
00:39:58.428 --> 00:40:01.612 don't use it because I'm not happy with the results yet.
00:40:01.652 --> 00:40:02.252 Sure.
00:40:02.772 --> 00:40:04.702 And so one of the things I have.
00:40:07.492 --> 00:40:08.082 See.
00:40:09.512 --> 00:40:11.562 The clothes. Yeah, like I don't even have.
00:40:12.062 --> 00:40:14.532 Oh, I see. It was intended with a.
00:40:16.022 --> 00:40:18.552 Future tag.
00:40:19.372 --> 00:40:23.812 Yeah, I yeah, I don't. Uh, I don't know. I think that there's
00:40:23.812 --> 00:40:25.602 something to be said for.
00:40:26.252 --> 00:40:30.052 Planning queries so that you can see in a view like this cause.
00:40:31.232 --> 00:40:34.807 I'm a huge fan of this view, but ohhh my gosh, the scrolling and
00:40:33.722 --> 00:40:34.092 Mm-hmm.
00:40:34.807 --> 00:40:38.272 the scrolling and the scrolling and this is 1 project and it's
00:40:35.892 --> 00:40:37.922 Yeah, yeah, it's a nightmare.
00:40:38.272 --> 00:40:39.702 only one developer, right?
00:40:39.472 --> 00:40:39.802 Yeah.
00:40:40.532 --> 00:40:44.827 So if I go to something like this and I can see it in a page
00:40:44.827 --> 00:40:49.333 or I can see it in a page with two swipes of a scroll, it gives
00:40:47.742 --> 00:40:48.252 Umm.
00:40:49.333 --> 00:40:50.812 me potentially a lot.
00:40:51.812 --> 00:40:55.982 Better, more holistic view of what I'm looking at.
00:40:59.132 --> 00:41:00.842 I don't know. That's probably.
00:41:01.562 --> 00:41:04.722 That's the bulk of what what I'm doing in there. I don't know if
00:41:04.722 --> 00:41:06.812 it's helpful, but that's my quick rundown.
00:41:07.292 --> 00:41:11.140 I think it's great with the Sprint view though. Whoever used
00:41:11.140 --> 00:41:12.212 the backlog view.
00:41:14.962 --> 00:41:15.622 In the Sprint.
00:41:18.382 --> 00:41:19.752 Thank you. Might like that, Charlie.
00:41:28.932 --> 00:41:30.462 You just do this here.
00:41:33.552 --> 00:41:35.452 Yes. So go to your sprints on the left hand side.
00:41:42.872 --> 00:41:45.792 Then next the task board hit backlog.
00:41:51.902 --> 00:41:55.007 And then you can still use that filter all the same. So open
00:41:55.007 --> 00:41:55.822 that filter out.
00:41:58.332 --> 00:41:59.912 And then just WBS or whatever.
00:42:05.002 --> 00:42:07.562 Over this is from 2 sprints back, so we might want to click
00:42:07.562 --> 00:42:08.372 on the current one.
00:42:09.692 --> 00:42:11.442 That that opened it up that way.
00:42:15.302 --> 00:42:16.692 Drop down just to your right.
00:42:20.672 --> 00:42:23.162 Just above it or it says Sprint 11:30 to 12:13.
00:42:26.042 --> 00:42:30.414 Now that is this friend. Well, I'm ******* I. No, no, it's not.
00:42:30.414 --> 00:42:34.717 Ohh, it's not a puppy. OK, pod be dropped down. Left hand side
00:42:34.717 --> 00:42:36.152 there do all project.
00:42:43.892 --> 00:42:45.142 And filter again.
00:42:50.342 --> 00:42:52.658 Quick view and you can add columns are just like you would
00:42:52.658 --> 00:42:52.972 a query.
00:42:54.972 --> 00:42:56.162 You need a quick view of the Sprint.
00:42:57.022 --> 00:42:57.702 Than I thought.
00:43:05.482 --> 00:43:08.320 You are muted if you're talking at all, Charlie. Sorry if it's
00:43:08.320 --> 00:43:10.032 something I'm ignoring you, you know.
00:43:09.282 --> 00:43:11.567 Oh yeah, I've totally been. I've been yammering away in the
00:43:10.692 --> 00:43:13.207 OK, I was like, I don't know if you just didn't wanna talk and
00:43:11.567 --> 00:43:13.052 background here the whole way through.
00:43:13.207 --> 00:43:15.522 that's OK like, I get it sometimes. I don't want to talk.
00:43:16.692 --> 00:43:20.973 No, you that's that's very cool and you missed much excitement.
00:43:20.973 --> 00:43:21.642 I love it.
00:43:21.612 --> 00:43:25.839 OK, cool. Cheers. Alright. Anyone else have any other
00:43:25.839 --> 00:43:29.362 questions about Azure Sprint planning? What?
00:43:28.602 --> 00:43:29.802 I have a question for client.
00:43:30.972 --> 00:43:32.422 Click OK ohh it.
00:43:32.312 --> 00:43:32.722 Here.
00:43:33.302 --> 00:43:36.332 You said you used the queries to use the hours to send to
00:43:36.332 --> 00:43:39.362 clients, or that's something that you recommend us doing.
00:43:39.362 --> 00:43:42.287 Those aren't usually the only hours that we use towards
00:43:42.287 --> 00:43:45.578 projects though, so how do you add that with the projects that
00:43:45.578 --> 00:43:48.712 you're pulling from EP, from meetings and project managers?
00:43:50.012 --> 00:43:53.555 It's a estimate, just like the actual hours in the ticket.
00:43:53.552 --> 00:43:54.392 Got it. OK.
00:43:53.555 --> 00:43:57.159 There's no way of knowing for sure like and I don't do this
00:43:55.862 --> 00:43:56.272 OK.
00:43:57.159 --> 00:44:00.522 for every project to clarify because it is like an hour
00:44:00.522 --> 00:44:01.002 process.
00:44:01.522 --> 00:44:04.102 Yeah, I was just curious if you had a way of merging the two
00:44:02.002 --> 00:44:02.552 I'll.
00:44:04.102 --> 00:44:05.032 that would be helpful.
00:44:05.922 --> 00:44:09.438 Not really. I mean, you could take an export the problem with
00:44:09.438 --> 00:44:13.011 taking export from EP is you're using historical data and that
00:44:13.011 --> 00:44:16.527 that is good if you want to use that for projecting, but it's
00:44:16.527 --> 00:44:20.044 not always gonna be accurate like some sprints. You have more
00:44:20.044 --> 00:44:23.560 meetings. Some sprints you may have less depends what's going
00:44:23.560 --> 00:44:27.189 on the like if I share my screen I provided ENISA report of all
00:44:27.189 --> 00:44:30.422 of the hours we intend to use for each of the different.
00:44:31.112 --> 00:44:34.974 Bugs and change request and then I just added in a few extra
00:44:34.974 --> 00:44:39.089 hours for PM meeting QA and like one whole hour of that was just
00:44:39.089 --> 00:44:40.102 for this report.
00:44:41.262 --> 00:44:44.834 I don't generally use that much on this project. Why do we do it
00:44:44.834 --> 00:44:48.242 on this one? Well, it's just cause they requested it as a way
00:44:48.242 --> 00:44:51.594 of getting understanding of hours usage and then in addition
00:44:51.594 --> 00:44:54.232 to that cause our hours balance was at 8 hours.
00:44:55.452 --> 00:44:59.456 And we need an additional 5.25. I recommended a 10 hour invoice,
00:44:59.456 --> 00:45:02.968 so we have at least five hours on hand in case something
00:45:02.968 --> 00:45:03.892 critical comes.
00:45:05.212 --> 00:45:11.903 I'd just jump in as a former customer and point out that that
00:45:11.903 --> 00:45:14.062 block of Excel data.
00:45:14.822 --> 00:45:23.134 In a basecamp message is so much more digestible than pages 2-3
00:45:19.632 --> 00:45:19.922 Umm.
00:45:23.134 --> 00:45:25.472 and five of a PSR.
00:45:25.512 --> 00:45:27.222 But you're saying this isn't useful.
00:45:28.412 --> 00:45:29.722 This this.
00:45:29.802 --> 00:45:31.852 The this thing isn't.
00:45:30.872 --> 00:45:34.118 I mean, I was the jerk customer who never actually looked at
00:45:34.118 --> 00:45:35.502 much of any of it because.
00:45:34.802 --> 00:45:35.692 No, they never do.
00:45:36.412 --> 00:45:40.206 Because like I'm going blind, right? It's it's too much
00:45:40.206 --> 00:45:44.340 information. But that clean one block on a base camp thread.
00:45:41.452 --> 00:45:42.542 Way too much information.
00:45:44.340 --> 00:45:47.592 Yeah, like that's. I can read that at a glance.
00:45:47.712 --> 00:45:52.522 This This is why in Nuclino where I I created this PSR.
00:45:53.862 --> 00:45:57.037 I don't take all the credit. Somebody somebody created this.
00:45:57.037 --> 00:46:00.212 Let me take that back. But what I did do is I added in here.
00:46:00.292 --> 00:46:04.268 Uh, general messaging. I put so like hours. Use hours, pay
00:46:04.268 --> 00:46:08.446 current hours, balance if you really wanna get fancy, you can
00:46:08.446 --> 00:46:12.220 put in like I just sent a message to the connect common
00:46:12.220 --> 00:46:15.994 model team, specifically management indicating how many
00:46:15.994 --> 00:46:19.902 hours were used in the date period. So like in for common
00:46:19.902 --> 00:46:21.722 model we've used 124 hours.
00:46:23.332 --> 00:46:28.294 For this period, which is the first literally 16 days, we've
00:46:28.294 --> 00:46:30.002 used that much hours.
00:46:30.882 --> 00:46:34.521 Uh, so on your project, it's a good idea to say here's the
00:46:34.521 --> 00:46:38.283 hours used, hours paid, turns, hours, balance and then maybe
00:46:38.283 --> 00:46:41.860 just like a slight summary, if you want to depends on the
00:46:41.860 --> 00:46:43.032 project, certainly.
00:46:45.322 --> 00:46:47.716 And that's what I do for all my PSR is, because you're totally
00:46:47.716 --> 00:46:49.312 right. They're never going to look at it.
00:46:50.822 --> 00:46:55.012 Yeah, I I that's I really liked. I'm totally stealing that.
00:46:51.252 --> 00:46:51.492 We.
00:46:56.512 --> 00:46:59.162 And then the other thing Stephanie does is she'll go
00:46:56.522 --> 00:46:57.752 Teaming up one of those and.
00:46:59.162 --> 00:47:01.762 through it on the meeting, which is also advisable.
00:47:02.552 --> 00:47:04.362 Because it gets that visibility out there.
00:47:05.422 --> 00:47:06.772 But the meeting is key.
00:47:05.542 --> 00:47:08.537 And I would, I would say if Stephanie was here, she would
00:47:08.537 --> 00:47:11.791 say it's required to go through it on a meeting, which I would
00:47:11.312 --> 00:47:13.352 And I believe it is. Believe it is.
00:47:11.791 --> 00:47:13.392 agree with. It is a thing that.
00:47:12.652 --> 00:47:13.242 Well, I'm going to.
00:47:14.472 --> 00:47:15.262 It is a thing.
00:47:14.512 --> 00:47:17.202 I'm also going to add as I'm sorry Clint guide.
00:47:17.812 --> 00:47:18.802 No, no, no. It's my.
00:47:19.792 --> 00:47:20.392 Go ahead.
00:47:21.042 --> 00:47:24.382 I was just going to say it is the thing that is a benefit.
00:47:27.192 --> 00:47:29.929 As a new PM, it's going to be really helpful, which is why,
00:47:29.929 --> 00:47:32.849 again, I really like that and I may still you next week to make
00:47:32.849 --> 00:47:35.404 sure that I'm pulling it correctly in a format it right
00:47:35.404 --> 00:47:38.370 and everything to use. But as a new PM coming on, the notes that
00:47:38.370 --> 00:47:40.879 we're taking and trying to get from client calls, if I
00:47:40.879 --> 00:47:43.844 accidentally miss something and they see this and they say, hey,
00:47:43.844 --> 00:47:46.582 what about this? Like, I don't see this line item we talked
00:47:46.582 --> 00:47:49.182 about adding this in this Sprint. If they notice, I mean
00:47:49.182 --> 00:47:51.965 they may not look into it that deeply, but if I accidentally
00:47:51.965 --> 00:47:53.562 miss something to put it in there.
00:47:54.052 --> 00:47:55.142 That's also going to help.
00:47:57.832 --> 00:47:58.632 Yeah, absolutely.
00:47:59.642 --> 00:48:02.710 And feel free to just snag some time and I'm happy to go through
00:48:02.710 --> 00:48:02.852 it.
00:48:03.262 --> 00:48:04.282 Perfect. Thank you.
00:48:08.782 --> 00:48:10.572 I had a question on.
00:48:13.122 --> 00:48:17.460 The balancing tickets that you had, like for example, and I
00:48:15.082 --> 00:48:15.502 Yeah.
00:48:17.460 --> 00:48:22.159 don't even know if this question will actually pertain to the PM
00:48:22.159 --> 00:48:26.714 or if this is just more falls on you. But if for example, like
00:48:23.982 --> 00:48:24.902 Yeah, yeah, let's set it.
00:48:26.714 --> 00:48:30.112 Brendan Flaherty had, I think 34 hours on his.
00:48:30.632 --> 00:48:36.037 Uh, so that means that he's only, like, actually got
00:48:36.037 --> 00:48:40.422 allocated to him about 3041 hours of work.
00:48:38.992 --> 00:48:39.522 1.
00:48:40.212 --> 00:48:41.202 Yeah. Mm-hmm.
00:48:41.102 --> 00:48:44.152 Uh, so if he burns through that and nobody has, like, gone
00:48:44.152 --> 00:48:47.460 through and pulled any of that, is that something you just keep
00:48:47.460 --> 00:48:50.768 an eye on throughout the Sprint just to make sure that he's not
00:48:50.768 --> 00:48:53.972 just about to run out of work? And if he is pick some of that
00:48:53.972 --> 00:48:57.073 hours and just assign him to something or is that something
00:48:57.073 --> 00:49:00.175 that we as PMS should be looking into to make sure that the
00:49:00.175 --> 00:49:01.932 developers don't run out of work?
00:49:02.402 --> 00:49:05.722 Yeah, it's that, that, that, that burden is squarely on me.
00:49:06.162 --> 00:49:06.572 OK.
00:49:07.672 --> 00:49:11.974 However, I will then come to you and say, like I'll look at my
00:49:11.974 --> 00:49:16.002 little board and I'll say like Ohh Brendan's on Project X.
00:49:17.172 --> 00:49:20.087 Do you have any work for him in the Sprint for that or is that
00:49:20.087 --> 00:49:21.522 he can get started on for that?
00:49:22.062 --> 00:49:22.452 OK.
00:49:23.952 --> 00:49:27.618 And that's where we might go into there's, uh, the there's
00:49:27.618 --> 00:49:31.471 always money in the banana stand kind of thing where being an
00:49:31.471 --> 00:49:35.262 internal work or maybe A through Z of other possible things.
00:49:35.732 --> 00:49:36.052 Mm-hmm.
00:49:36.852 --> 00:49:38.142 I love that reference.
00:49:38.132 --> 00:49:41.520 And it's the best you can see, especially because it works
00:49:41.520 --> 00:49:44.162 seriously and sarcastically at the same time.
00:49:44.452 --> 00:49:46.652 Me too. I giggled. Y'all couldn't hear me, though.
00:49:44.582 --> 00:49:45.292 UM.
00:49:49.112 --> 00:49:51.770 Yeah. I'll go over here and I'll just look for other projects
00:49:51.770 --> 00:49:52.542 that Brendan's on.
00:49:53.912 --> 00:49:58.168 Or I can even do just a a a query. What does he worked on in
00:49:58.168 --> 00:49:59.912 the past like six months?
00:50:01.752 --> 00:50:02.392 Excuse me.
00:50:05.392 --> 00:50:07.941 Maybe he has, you know, if he hasn't done, you know, maybe he
00:50:07.941 --> 00:50:10.448 was on bid six months ago. We said anything for a while, but
00:50:10.448 --> 00:50:12.874 that means he at least has a local. He's familiar with it.
00:50:12.874 --> 00:50:15.381 Maybe I can ask her. Like, hey, Brendan's got a little extra
00:50:15.381 --> 00:50:16.902 time. Do you need extra hand on bid?
00:50:18.492 --> 00:50:20.192 OK, makes sense.
00:50:18.572 --> 00:50:22.403 And try. I saw your hand went up. Yeah. Yeah. I don't want you
00:50:22.403 --> 00:50:26.233 have to worry about that though. You PM have enough day-to-day
00:50:26.233 --> 00:50:29.881 worrying about things. That responsibility lies squarely on
00:50:29.881 --> 00:50:32.982 me until I say I say, hey, I need help about this.
00:50:30.602 --> 00:50:31.042 Gotcha.
00:50:32.722 --> 00:50:33.952 Yeah.
00:50:33.912 --> 00:50:34.162 Yeah.
00:50:36.042 --> 00:50:38.772 It does it. It falls on you until it falls on us.
00:50:38.912 --> 00:50:40.242 Yeah, yeah, yeah. Yeah, exactly.
00:50:39.832 --> 00:50:40.442 Gotcha.
00:50:44.192 --> 00:50:44.912 You have a question?
00:50:45.742 --> 00:50:49.507 So I I pulled my hand back down because I was like ohh let me
00:50:49.507 --> 00:50:50.722 Google that for you.
00:50:51.592 --> 00:50:52.242 Umm.
00:50:51.802 --> 00:50:56.157 But does anybody know off the top of your head if I wanted to
00:50:56.157 --> 00:51:00.371 filter in a query, I wanted to select four multiple tags. I
00:51:00.371 --> 00:51:04.866 feel like I don't have to add a separate line for every. I feel
00:51:02.012 --> 00:51:02.252 Yeah.
00:51:04.866 --> 00:51:08.730 like I should be able to do a comma separated value or
00:51:05.812 --> 00:51:06.142 So.
00:51:08.730 --> 00:51:13.295 something like that, but I don't actually remember and I haven't
00:51:10.822 --> 00:51:11.142 Yeah.
00:51:13.295 --> 00:51:15.332 muddled my way through to it.
00:51:16.322 --> 00:51:17.952 Yeah, let's just say.
00:51:19.632 --> 00:51:23.024 Anything that's closed past secure and moves we wanna do
00:51:23.024 --> 00:51:23.322 tags.
00:51:25.432 --> 00:51:28.352 I believe it's in wait. Is that not it?
00:51:29.012 --> 00:51:29.742 That contains.
00:51:30.152 --> 00:51:33.232 OK, let's see. Let's find Klein.
00:51:36.852 --> 00:51:39.742 I don't know. That's what everything that yeah.
00:51:40.922 --> 00:51:43.172 I know that you can do.
00:51:47.822 --> 00:51:48.262 For that.
00:51:57.242 --> 00:51:59.932 The thing it's gonna be both. It's not an either or.
00:52:03.222 --> 00:52:04.082 If it's in there.
00:52:05.522 --> 00:52:10.275 Now that's a fair point that if you just make make a list, then
00:52:06.252 --> 00:52:06.922 But.
00:52:10.275 --> 00:52:14.804 you have no way of suggesting and versus or. So maybe you do
00:52:14.804 --> 00:52:17.552 have to do a separate line for each.
00:52:15.652 --> 00:52:16.482 Umm.
00:52:18.092 --> 00:52:21.560 I'd have the age now. There is one though we can give it up.
00:52:21.560 --> 00:52:25.027 You can feed it a handful of ones, but I guess I didn't know
00:52:25.027 --> 00:52:26.562 that it was field specific.
00:52:28.322 --> 00:52:29.042 Uh.
00:52:33.002 --> 00:52:36.250 But that's where you do the in, but I can't remember what I've
00:52:36.250 --> 00:52:36.972 used that for.
00:52:39.922 --> 00:52:41.552 Yeah. Now you just see the opera end.
00:52:44.992 --> 00:52:47.862 Alright, well, we don't need to turn this into. Like I said. I
00:52:47.862 --> 00:52:49.912 mean I could Google it and sort it out, but.
00:52:48.262 --> 00:52:51.114 That's OK. That's OK. We'll figure out if you need help
00:52:51.114 --> 00:52:54.170 tinkering though, let me know and I can get into it. If the
00:52:54.170 --> 00:52:55.392 specific query you want.
00:52:56.082 --> 00:52:56.952 OK, that's Weber.
00:52:58.662 --> 00:53:01.382 The other thing you could do is if.
00:53:02.732 --> 00:53:06.283 Like let's say they get if it was 4-1 project, that might be a
00:53:06.283 --> 00:53:09.551 place where using Excel to filter that data further would
00:53:09.551 --> 00:53:12.482 be more beneficial to you. That's where I might go.
00:53:10.472 --> 00:53:10.812 You.
00:53:11.622 --> 00:53:12.442 Yeah, potentially.
00:53:13.632 --> 00:53:16.889 Do the link to the the query and then put the tags you want in
00:53:16.889 --> 00:53:19.888 there because you can use the operands on the filters and
00:53:19.888 --> 00:53:20.922 excel really easily.
00:53:20.142 --> 00:53:21.742 No, that's true. Yeah.
00:53:22.812 --> 00:53:26.129 Yeah, yeah, dump it all to excel and then let excel do the
00:53:26.129 --> 00:53:27.872 further selection. That's cool.
00:53:27.592 --> 00:53:28.002 Yeah.
00:53:28.662 --> 00:53:29.162 Cool. Thanks.
00:53:29.872 --> 00:53:32.871 Course, cool. Any other questions? Thoughts, comments,
00:53:32.871 --> 00:53:33.362 concerns?
00:53:35.702 --> 00:53:38.272 Azure or Sprint planning tasks?
00:53:41.502 --> 00:53:42.182 Beliefs.
00:53:45.642 --> 00:53:46.742 Hopes. Dreams.
00:53:48.572 --> 00:53:50.142 And what happens is fun going on this weekend.
00:53:53.342 --> 00:53:57.321 I am house sitting and probably doing Dungeons and Dragons
00:53:55.552 --> 00:53:56.102 Ooh.
00:53:57.321 --> 00:53:58.872 virtually this weekend.
00:53:58.972 --> 00:54:00.852 Ooh, what do you guys use?
00:54:00.242 --> 00:54:01.212 Nice.
00:54:01.712 --> 00:54:02.152 Say what?
00:54:02.712 --> 00:54:05.947 What do you use for the? Do you guys do like a role 20 or
00:54:05.947 --> 00:54:07.062 something like that?
00:54:07.732 --> 00:54:13.551 Umm, so it's all like I IDM and I'll be honest, I'm a very lax
00:54:12.852 --> 00:54:13.122 Mm-hmm.
00:54:13.551 --> 00:54:18.908 DM. There's a lot of lot of drinking that goes on when we
00:54:18.908 --> 00:54:22.602 play. So it's a ours is adapted off of.
00:54:19.432 --> 00:54:20.692 That's the best way to play.
00:54:21.472 --> 00:54:23.142 Was gonna say is there another way to play?
00:54:23.332 --> 00:54:26.802 Yeah, ours is adapted off of Skyrim, actually.
00:54:26.782 --> 00:54:27.662 They were saying that.
00:54:27.362 --> 00:54:31.087 Uh, wait, Trenton. I told I told my boyfriend and I he really
00:54:27.912 --> 00:54:28.402 Yeah.
00:54:31.087 --> 00:54:34.931 wants to, like, join like either via zoom or discord, so I will
00:54:32.992 --> 00:54:33.342 Well.
00:54:34.472 --> 00:54:35.582 Yeah.
00:54:34.931 --> 00:54:35.472 give him.
00:54:36.442 --> 00:54:40.275 Or I'll give you his e-mail and cause he was so excited. He was
00:54:36.572 --> 00:54:37.162 I can.
00:54:37.902 --> 00:54:38.692 Yeah.
00:54:40.275 --> 00:54:42.012 like, no way. That's so cool.
00:54:40.502 --> 00:54:42.232 Yeah, yeah.
00:54:43.022 --> 00:54:47.322 We're probably going to. We're playing tomorrow. If everybody's
00:54:45.752 --> 00:54:46.202 Fun.
00:54:46.742 --> 00:54:48.012 But they all do it in here.
00:54:47.322 --> 00:54:48.262 able to do it.
00:54:49.182 --> 00:54:50.212 We're talking about our weekends.
00:54:51.832 --> 00:54:54.834 Yeah, we're, we're we're gonna play if everybody's able to. I'm
00:54:54.834 --> 00:54:57.788 still waiting on responses from people, but we've got a couple
00:54:55.092 --> 00:54:55.502 Mm-hmm.
00:54:56.302 --> 00:54:56.822 Umm.
00:54:57.788 --> 00:54:59.852 that are like, ohh yeah, I'll do a virtual.
00:55:01.892 --> 00:55:06.212 But if we do, uh, and he wants to join in for tomorrow, then
00:55:06.212 --> 00:55:07.982 I'm totally OK with that.
00:55:08.702 --> 00:55:11.630 Get that e-mail out, Amy, and tell her. Tell her boyfriend.
00:55:11.630 --> 00:55:14.558 You said you would have to. Trenton today. OK. Could I have
00:55:14.558 --> 00:55:16.852 your character rolled up in the next 12 hours?
00:55:14.772 --> 00:55:16.042 Gotta yeah.
00:55:15.822 --> 00:55:16.892 I'll do it tonight.
00:55:17.222 --> 00:55:18.482 Gotta get him a character.
00:55:19.972 --> 00:55:22.592 He talks to me for like 30 minutes straight about he was
00:55:20.202 --> 00:55:20.912 It'll be a.
00:55:20.232 --> 00:55:20.882 That's awesome.
00:55:22.592 --> 00:55:25.487 like about the whole concept of combining Skyrim with that and
00:55:25.487 --> 00:55:26.682 my brain. I was just like.
00:55:27.182 --> 00:55:29.032 Ha ha ha ha ha.
00:55:27.952 --> 00:55:32.626 Ohh I gotta like I gotta explain to him like the whole adaptation
00:55:32.626 --> 00:55:36.874 of it, because like the setting of it is, it's set 15 years
00:55:36.874 --> 00:55:41.265 after The Elder Scrolls 5. So there's a bunch of stuff that I
00:55:40.342 --> 00:55:41.472 Ah.
00:55:41.265 --> 00:55:45.867 had to create myself and decide on like, how does this end? What
00:55:45.867 --> 00:55:47.142 happens from here?
00:55:48.342 --> 00:55:51.730 So it's like a really unique world that you're you can still
00:55:51.730 --> 00:55:55.007 run into like the familiar characters because it's not set
00:55:55.007 --> 00:55:57.062 so far after that, they're all dead.
00:55:57.162 --> 00:55:57.752 Sure.
00:55:58.722 --> 00:55:59.162 But.
00:55:59.922 --> 00:56:04.366 There's also a lot of different stuff based on the events of
00:56:04.366 --> 00:56:05.532 Elder Scrolls 5.
00:56:05.822 --> 00:56:07.272 Got it. That's cool.
00:56:07.072 --> 00:56:07.542 Back.
00:56:08.442 --> 00:56:12.642 So does this mean everyone's invoicing notes are completed?
00:56:08.742 --> 00:56:09.132 Toll.
00:56:12.642 --> 00:56:15.792 Your time logs are up to date and you at at.
00:56:16.202 --> 00:56:18.442 Now as it says, we just did all the Azure training.
00:56:19.672 --> 00:56:21.612 That's anything fun this weekend.
00:56:19.852 --> 00:56:21.222 I'm just being obnoxious.
00:56:23.172 --> 00:56:26.551 We only got 10 minutes left. I had to say it. Get your time
00:56:26.032 --> 00:56:29.072 No, that that that's always my good. But that's at my goodbye.
00:56:26.551 --> 00:56:27.002 logs in.
00:56:29.072 --> 00:56:31.002 Shelton. What's up, man? Your hands up.
00:56:34.992 --> 00:56:40.093 Yes. And of course Stephanie joins right, is that do this,
00:56:40.093 --> 00:56:45.022 but I have one more work related question Slash request.
00:56:41.502 --> 00:56:43.122 Yeah, go for it.
00:56:42.482 --> 00:56:45.737 And what a brown nose. Yeah. Jeepers, what's here? Trying to
00:56:44.432 --> 00:56:46.932 No, no, no, no, no this.
00:56:45.102 --> 00:56:45.712 Uh.
00:56:45.737 --> 00:56:48.672 ask you about their weekends. There's gonna be a drag.
00:56:48.192 --> 00:56:52.726 Yeah. Yeah. Stephanie always say one more thing. It's from our
00:56:50.332 --> 00:56:51.782 This is from earlier.
00:56:52.726 --> 00:56:55.532 call. Earlier little inside joke, but.
00:56:54.222 --> 00:56:54.672 OK.
00:56:55.322 --> 00:56:56.272 I'm dying.
00:56:58.272 --> 00:57:02.841 So I have a request to make for the PM team and I've already
00:57:00.872 --> 00:57:01.152 OK.
00:57:01.932 --> 00:57:02.202 No.
00:57:01.932 --> 00:57:02.412 Yeah.
00:57:02.841 --> 00:57:07.111 kind of asked Charlie and Jessica about this, but once a
00:57:06.722 --> 00:57:07.212 Hard, no.
00:57:07.111 --> 00:57:11.980 week to meet with my PM's for my projects for 15 minutes just to
00:57:11.980 --> 00:57:16.175 catch up on our projects, get on the same page and plan
00:57:16.175 --> 00:57:20.819 everything out for all of our projects for the upcoming week.
00:57:20.819 --> 00:57:25.538 If that would be something that everyone would be available to
00:57:23.642 --> 00:57:24.082 Yeah.
00:57:25.538 --> 00:57:26.662 do, or if it's.
00:57:26.082 --> 00:57:28.132 Hard. No. Shelton hard, no.
00:57:28.902 --> 00:57:30.182 Uh, why they couldn't be available?
00:57:31.132 --> 00:57:32.262 Little 15 minute meeting.
00:57:32.732 --> 00:57:33.322 Umm.
00:57:32.852 --> 00:57:33.262 Uh-huh.
00:57:34.022 --> 00:57:38.269 Yeah, it's I I found we've done them twice so far and I found it
00:57:34.202 --> 00:57:34.462 Yeah.
00:57:35.862 --> 00:57:36.322 Shut.
00:57:38.269 --> 00:57:42.059 really helpful. It gets us immediately onto the same page
00:57:42.059 --> 00:57:45.392 going into the client call. Yeah, it's super cool.
00:57:46.442 --> 00:57:49.083 Would this be something like? How long do those meetings and
00:57:49.083 --> 00:57:49.992 watch the two of you?
00:57:51.182 --> 00:57:51.942 Yeah, just like.
00:57:51.352 --> 00:57:52.152 We spent a.
00:57:53.712 --> 00:57:54.172 Go ahead.
00:57:53.822 --> 00:57:54.402 Half hour.
00:57:56.932 --> 00:57:57.282 Yeah.
00:58:03.242 --> 00:58:03.522 Yeah.
00:58:03.912 --> 00:58:07.982 The 30 minute call we talked about PCs discovery and Tom's
00:58:07.982 --> 00:58:11.776 discovery, so it was two projects. So yeah, I mean you
00:58:09.222 --> 00:58:09.672 Ah.
00:58:09.492 --> 00:58:09.892 OK.
00:58:11.776 --> 00:58:15.776 can cover a lot in 15 if you need more than that then you
00:58:15.776 --> 00:58:20.122 probably like that wouldn't be a weekly 30 minutes a week on a
00:58:20.122 --> 00:58:24.537 project is probably excessive. But if you're just touching base
00:58:22.952 --> 00:58:23.562 Mm-hmm.
00:58:24.537 --> 00:58:29.089 and making sure that you're both thinking clearly and on the same
00:58:29.089 --> 00:58:30.262 wavelength on it.
00:58:31.692 --> 00:58:34.512 Then great. And if you discover ohh no, that's not what I
00:58:34.512 --> 00:58:37.527 thought at all. Alright. Well then maybe you need to dig in a
00:58:37.527 --> 00:58:38.402 little bit deeper.
00:58:39.512 --> 00:58:39.892 Mm-hmm.
00:58:41.352 --> 00:58:42.812 100% cool.
00:58:44.482 --> 00:58:44.832 OK.
00:58:46.052 --> 00:58:49.642 Ohm. OK.
00:58:50.862 --> 00:58:51.912 So anything else for the group?
00:58:52.582 --> 00:58:55.536 Shelton just called me out. Dude, did I get you my Toms
00:58:55.536 --> 00:58:55.852 notes?
00:58:57.182 --> 00:59:02.015 Ohh you said. I'm like in a teams chat, so that's a really
00:59:00.822 --> 00:59:01.432 OK.
00:59:02.015 --> 00:59:03.572 all I needed, yeah.
00:59:02.632 --> 00:59:03.462 OK, good.
00:59:06.212 --> 00:59:07.382 Ohh madness.
00:59:09.862 --> 00:59:14.253 Just make sure if you guys have myself included so this is more
00:59:14.253 --> 00:59:18.713 of a reminder for me and saying it out loud to have you all hold
00:59:18.713 --> 00:59:23.172 me accountable if you have time off coming up in the next weeks,
00:59:23.172 --> 00:59:26.877 make sure that you get your notification sent out via
00:59:26.722 --> 00:59:27.082 Yeah.
00:59:26.877 --> 00:59:31.131 Basecamp. Turn on your out of office e-mail notifications and
00:59:31.131 --> 00:59:35.041 that you're cancelling any meetings that you can and you
00:59:35.041 --> 00:59:38.952 have a coverage plan in place for those that you cannot.
00:59:40.172 --> 00:59:44.263 Please make sure that any of your invoicing notes are fully
00:59:44.263 --> 00:59:48.082 filled out if you are going to be missing a Monday, so.
00:59:50.522 --> 00:59:53.845 Clint, I think the actually this would be the Tuesday after
00:59:53.845 --> 00:59:57.333 Christmas for you. We'll need to make sure that we have all of
00:59:57.333 --> 01:00:00.988 your invoicing notes filled out, action plan, maybe you and I can
01:00:00.988 --> 01:00:04.532 sync on it beforehand, kind of the same thing for the team like
01:00:04.532 --> 01:00:05.252 let's try to.
01:00:06.412 --> 01:00:09.972 I know we typically go week over week in our lives and we are
01:00:09.972 --> 01:00:13.648 usually planning it out for that moment. But because there's so
01:00:13.648 --> 01:00:17.093 many people that and so many moving parts with people being
01:00:17.093 --> 01:00:20.826 out and the holidays, I want us to start thinking big picture of
01:00:20.826 --> 01:00:23.582 the next two weeks in terms of invoicing notes.
01:00:24.652 --> 01:00:28.818 Making sure all of your to DOS or taken care of that no loose
01:00:28.818 --> 01:00:32.647 ends are left untied. If you're going to be going out on
01:00:32.647 --> 01:00:33.252 vacation.
01:00:38.382 --> 01:00:38.872 Yes.
01:00:38.532 --> 01:00:39.282 That's it from me.
01:00:39.202 --> 01:00:40.442 Third, yes ma'am.
01:00:43.202 --> 01:00:45.752 These were all the PTO is. If you have other stuff.
01:00:49.102 --> 01:00:50.112 Let's talk on Monday.
01:00:51.072 --> 01:00:56.772 His thoughts, the Tuesday and Wednesday after Christmas.
01:00:57.012 --> 01:00:57.822 Don't tell Daniel.
01:00:57.132 --> 01:00:57.532 What?
01:00:58.582 --> 01:01:00.282 I let him out of your cage.
01:00:58.892 --> 01:00:59.752 It doesn't mean no.
01:01:00.282 --> 01:01:01.352 That's not on the list.
01:01:01.932 --> 01:01:03.562 It's on my list, Daniel.
01:01:04.372 --> 01:01:06.422 Well, it's not real.
01:01:07.802 --> 01:01:08.462 It's new.
01:01:11.522 --> 01:01:14.042 Not real, sorry, Clint. Daniel didn't approve.
01:01:12.852 --> 01:01:13.452 Not real.
01:01:13.902 --> 01:01:14.992 It's not real.
01:01:15.182 --> 01:01:16.252 It's not real.
01:01:17.242 --> 01:01:20.971 Daniel does not approve, so I'm going to go update rippling
01:01:20.971 --> 01:01:21.592 apologies.
01:01:22.502 --> 01:01:23.892 The Hunt Daniel's house.
01:01:24.982 --> 01:01:25.752 The entire time.
01:01:25.112 --> 01:01:28.360 Uh, you're already in the basement like he has the keys. I
01:01:28.322 --> 01:01:30.692 Yeah, but I'm hunting. The upper floor is now.
01:01:28.360 --> 01:01:30.232 can't let you out. If he says no.
01:01:31.182 --> 01:01:31.812 Wait, what?
01:01:32.892 --> 01:01:33.312 Go ahead.
01:01:35.172 --> 01:01:35.682 Whatever.
01:01:35.182 --> 01:01:35.782 Staggered.
01:01:36.532 --> 01:01:39.450 You you made him mad, and Daniel left. He's like I'm turning my
01:01:39.450 --> 01:01:41.502 camera off. I'm not friends with us anymore.
01:01:42.652 --> 01:01:44.572 You made my Daniel mad at me.
01:01:42.702 --> 01:01:43.352 Yeah, I mean.
01:01:45.322 --> 01:01:46.572 We just, we stopped.
01:01:46.312 --> 01:01:46.822 Get out.
01:01:47.802 --> 01:01:49.432 We stopped being friendly long time ago.
01:01:50.252 --> 01:01:53.222 Yeah, but now you've made him mad at me, so get out.
01:01:53.882 --> 01:01:56.222 Right. OK. Bye, everyone.
01:01:57.332 --> 01:01:58.622 Bye.
01:01:57.362 --> 01:02:01.342 Have a great weekend. Everybody, please let me know if you need
01:02:01.342 --> 01:02:05.011 anything from me as soon as possible. I'm going to be half
01:02:05.011 --> 01:02:05.882 day on Monday.
01:02:07.522 --> 01:02:10.525 Stephanie, I sent you some pings for these emails. If you could
01:02:10.525 --> 01:02:13.528 review it and then help me with the other e-mail real fast too.
01:02:13.528 --> 01:02:15.452 The way I can get it done. Cool. Thanks.
01:02:13.552 --> 01:02:15.252 I got you. I got you.
01:02:17.042 --> 01:02:19.425 And Stephanie, if you need any help looking after anything
01:02:19.425 --> 01:02:21.767 during the time that you're gonna be gone next week, just
01:02:20.982 --> 01:02:21.602 Oh.
01:02:21.767 --> 01:02:22.252 let me know.
01:02:22.662 --> 01:02:24.612 Oh, my dear friend, you're getting a list.
01:02:26.832 --> 01:02:27.802 Don't you worry.
01:02:28.072 --> 01:02:28.852 Sounds good.
01:02:29.582 --> 01:02:33.309 Staff. I also got an e-mail from Brian at at region. You're not
01:02:33.309 --> 01:02:36.803 on it. I'm gonna forward it to you because he put some more
01:02:35.022 --> 01:02:35.532 Of course you did.
01:02:36.803 --> 01:02:40.531 time to make our discovery calls next week, but he accepted the
01:02:36.812 --> 01:02:37.562 Of course she did.
01:02:40.531 --> 01:02:43.792 two that I sent. So I don't understand what's going on.
01:02:42.632 --> 01:02:42.992 Umm.
01:02:46.482 --> 01:02:47.812 Interesting. I'll dive in.
01:02:46.872 --> 01:02:51.017 No, I will. I will forward, I will not add. I will forward
01:02:51.017 --> 01:02:52.352 just so he doesn't.
01:02:53.042 --> 01:02:54.222 Think that I'm ignoring him.
01:02:53.362 --> 01:02:54.852 Yeah. No, that's that's cool.
01:02:55.452 --> 01:02:56.362 OK, great. Thank you.
01:02:55.942 --> 01:02:56.592 Thank you. Thank you.
01:02:59.112 --> 01:02:59.682 Alrighty.
01:03:01.842 --> 01:03:02.662 You'll have a great weekend.
01:03:01.972 --> 01:03:03.642 OK, love you. Bye.
01:03:03.522 --> 01:03:04.922 In love you. Bye.
01:03:03.532 --> 01:03:04.542 Have a good weekend.
01:03:03.592 --> 01:03:05.212 Love you. Bye.
01:03:05.462 --> 01:03:06.862 Later, everybody see you.