00:00:03.135 --> 00:00:05.935 Probably WBS is my goal.
00:00:08.605 --> 00:00:09.145 OK.
00:00:10.635 --> 00:00:12.425 OK, OK.
00:00:10.755 --> 00:00:11.465 Bring it.
00:00:15.885 --> 00:00:17.355 Ah, OK.
00:00:18.265 --> 00:00:22.887 So we're going to do the previous Sprint which ran the
00:00:22.887 --> 00:00:23.895 5th through.
00:00:23.995 --> 00:00:24.945 To.
00:00:26.685 --> 00:00:30.855 What day is this? Through the 17th. Wow.
00:00:31.055 --> 00:00:35.093 I'm muted. I'm sorry. Yeah, fifth in the 17th. I was like,
00:00:33.855 --> 00:00:34.485 Thanks.
00:00:35.093 --> 00:00:38.105 17th. No, it was the 5th of the 17th, 17th.
00:00:37.705 --> 00:00:40.735 It has been a week.
00:00:42.015 --> 00:00:42.655 OK.
00:00:43.415 --> 00:00:46.015 So first and foremost, we're gonna look at the project.
00:00:47.395 --> 00:00:52.677 If this were the second Sprint of February, this project would
00:00:52.677 --> 00:00:57.874 not be allowed into the next Sprint until we had something to
00:00:57.874 --> 00:01:02.988 address this and there needs to be a signed off plan, either
00:01:02.988 --> 00:01:08.186 from leadership or we need to have a confirmation of when the
00:01:08.186 --> 00:01:10.785 invoice is expected to be paid.
00:01:11.805 --> 00:01:12.455 So.
00:01:11.835 --> 00:01:13.485 And in Ohh go ahead.
00:01:13.605 --> 00:01:16.647 I I actually think I should go ahead and speak to that because
00:01:16.647 --> 00:01:18.385 we don't have to wait for February.
00:01:20.185 --> 00:01:24.975 The client contacts were meeting with their CEO regarding invoice
00:01:24.975 --> 00:01:29.329 payment on Tuesday and we're supposed to respond to me with
00:01:29.329 --> 00:01:33.900 an approval, or lack thereof, on Tuesday and on that basis, we
00:01:33.900 --> 00:01:38.037 entered the work in the Sprint, having discussed it with
00:01:38.037 --> 00:01:38.835 leadership.
00:01:40.535 --> 00:01:45.945 Since Tuesday, they have ghosted me. I have kicked all of Brendan
00:01:45.945 --> 00:01:51.109 Lyons work and Michael Perez is all marked as blocked. But I'm
00:01:51.109 --> 00:01:56.355 not kicking it until I claim the hours for a different project.
00:01:57.515 --> 00:02:01.246 I don't wanna lose his capacity, but but we will not be doing any
00:02:01.246 --> 00:02:02.885 work for them in this Sprint.
00:02:03.585 --> 00:02:04.505 I think.
00:02:05.435 --> 00:02:09.823 That you might have just inadvertently put blood in the
00:02:09.823 --> 00:02:10.685 water, but.
00:02:11.825 --> 00:02:14.675 No, no. He has no available capacity. Well, Brendan does.
00:02:15.465 --> 00:02:15.865 Good luck.
00:02:17.895 --> 00:02:20.717 I don't know. You see those blockers? People are gonna
00:02:20.717 --> 00:02:21.025 start.
00:02:21.835 --> 00:02:24.575 Knocking on your door, Sir, OK.
00:02:26.205 --> 00:02:29.519 So this one may not be the best example of what I'm kind of
00:02:29.519 --> 00:02:32.998 looking for here, but one of the things that we're going to be
00:02:32.998 --> 00:02:36.532 starting to do is we run through this is we're going to look at
00:02:36.532 --> 00:02:38.465 the overall line item consumption.
00:02:40.885 --> 00:02:41.865 So.
00:02:42.645 --> 00:02:46.897 We're going to take a look at things like service request
00:02:46.897 --> 00:02:51.370 creation and taking a look at Discovery and the service call
00:02:51.370 --> 00:02:56.135 status update. Anything that we have in here that has gone over.
00:02:57.025 --> 00:03:03.351 This could potentially mean that a time logs were put to an
00:03:03.351 --> 00:03:04.405 incorrect.
00:03:06.145 --> 00:03:10.251 My light item, so we may need to go in and do a quick time log
00:03:10.251 --> 00:03:13.445 audit to address that to bring that back around.
00:03:14.105 --> 00:03:15.935 Uh, yeah, go ahead.
00:03:14.115 --> 00:03:19.322 They, Stephanie, just as a side note, because of the amount we
00:03:19.322 --> 00:03:24.115 credited on this project to look at this page, this is my
00:03:24.115 --> 00:03:29.074 messiest project. You'll see much more workable, functional
00:03:29.074 --> 00:03:34.116 and realistic data to engage with in CMMC or in JBM, or to a
00:03:34.116 --> 00:03:36.595 slightly lesser extent in bid.
00:03:37.135 --> 00:03:37.575 OK.
00:03:37.965 --> 00:03:40.755 I'm Amy. I'm gonna put you in the hot seat.
00:03:42.895 --> 00:03:46.722 I would like for you to talk about something that I'm gonna
00:03:43.585 --> 00:03:44.005 Yay.
00:03:46.722 --> 00:03:50.677 be instituting kind of across the board. And I would like for
00:03:50.677 --> 00:03:53.675 you to talk about the credits that we did for.
00:03:55.115 --> 00:03:56.875 Somebody recently.
00:03:57.355 --> 00:03:57.745 Writer.
00:03:57.635 --> 00:03:59.235 And was a writer.
00:04:00.425 --> 00:04:04.013 OK, so I'm going to put you in the hot seat. Have you share
00:04:04.013 --> 00:04:07.660 your screen and show what you did for that to make your line
00:04:07.660 --> 00:04:09.035 items look good in PSR?
00:04:09.985 --> 00:04:13.148 Well, actually on that remember when I think it was last week
00:04:13.148 --> 00:04:16.361 when I had asked you about that and we said to wait until that
00:04:15.105 --> 00:04:15.405 Uh-huh.
00:04:16.361 --> 00:04:19.065 second invoice was paid to go change the line items.
00:04:19.145 --> 00:04:22.975 Umm OK perfect so.
00:04:23.635 --> 00:04:25.305 When we're doing a credit request.
00:04:26.885 --> 00:04:28.405 I think you've all seen this form.
00:04:30.655 --> 00:04:31.835 Uh.
00:04:36.095 --> 00:04:39.469 We are actually putting in here the relevant line items that
00:04:39.469 --> 00:04:40.465 we're looking for.
00:04:41.125 --> 00:04:44.195 Umm. Amy, do you have that spreadsheet?
00:04:45.455 --> 00:04:46.105 For rider.
00:04:45.685 --> 00:04:48.891 Yeah, let let me find it. When my computer crashed other day,
00:04:48.891 --> 00:04:52.097 all my stuff got closed because I had it open for like a good
00:04:52.097 --> 00:04:55.355 week. But give Me 2 seconds and I will find it. Yeah. Yeah. My
00:04:52.955 --> 00:04:53.615 The worst?
00:04:55.355 --> 00:04:58.613 timelogs disappeared. And I was, like, wanted to cry, throw up
00:04:58.613 --> 00:04:59.595 the same time, but.
00:04:59.345 --> 00:04:59.805 Uh.
00:05:02.585 --> 00:05:03.775 Let me find it.
00:05:11.845 --> 00:05:15.914 Must have been the same feeling I had when I reviewed that bed
00:05:15.914 --> 00:05:18.755 demo the day before or the day of the yeah.
00:05:16.675 --> 00:05:18.095 So the one without audio.
00:05:19.995 --> 00:05:22.505 The cry and throw up at the same time. Ohh God.
00:05:24.245 --> 00:05:24.995 Uh-huh.
00:05:26.215 --> 00:05:27.815 Hmm hmm.
00:05:30.015 --> 00:05:30.505 So.
00:05:31.165 --> 00:05:35.910 What I'll quick do is I'll pop over to EP if I have it. Oh,
00:05:35.910 --> 00:05:36.305 guys.
00:05:38.695 --> 00:05:40.315 Anybody have EP pulled up?
00:05:43.835 --> 00:05:45.965 I do, but I always have EP up.
00:05:44.425 --> 00:05:44.945 I do.
00:05:47.345 --> 00:05:47.875 I've got it.
00:05:48.265 --> 00:05:50.462 Who's going to share their screen? Who's going into the hot
00:05:50.462 --> 00:05:50.645 seat?
00:05:51.555 --> 00:05:52.495 I'll go in the hot seat.
00:05:53.185 --> 00:05:53.625 Got you.
00:05:53.335 --> 00:05:54.365 Go in the hot seat.
00:05:53.835 --> 00:05:56.015 Up Jessica's Jessica, already in the hot seat.
00:05:55.145 --> 00:05:56.675 Jessica's in the hot seat.
00:05:56.115 --> 00:05:59.275 Look at that. There you go. Jeepers creepers.
00:05:57.025 --> 00:05:57.745 She beat me.
00:05:58.165 --> 00:05:58.925 Heck yeah.
00:05:59.645 --> 00:06:07.415 So, Jessica, can you go to projects and pull up?
00:06:08.635 --> 00:06:10.555 Was that writer? It was writer.
00:06:11.965 --> 00:06:12.685 Uh, so I found it.
00:06:13.265 --> 00:06:13.705 OK, cool.
00:06:22.665 --> 00:06:23.025 Sweet.
00:06:23.745 --> 00:06:28.931 So when we did the change request for Rider, there were a
00:06:28.931 --> 00:06:32.775 few lines where we were able to determine.
00:06:33.615 --> 00:06:35.465 After a review with leadership.
00:06:36.705 --> 00:06:38.605 And the developers, thank you, Daniel.
00:06:40.285 --> 00:06:43.735 And Amy, both of you, you were both involved in that. We were
00:06:43.735 --> 00:06:45.015 able to determine with.
00:06:47.135 --> 00:06:50.829 Reviewing with the developers as well as leadership items and
00:06:50.829 --> 00:06:54.583 line items that were eligible for a credit and we broke it out
00:06:54.583 --> 00:06:55.775 into literally like.
00:06:56.555 --> 00:07:00.493 I wanna say there was one that had like 1.25 hours credit that
00:07:00.493 --> 00:07:04.618 we were going to do. And So what we're gonna do with that to make
00:07:04.618 --> 00:07:07.805 sure that when we're going through these PSRS that
00:07:07.805 --> 00:07:11.368 everything makes sense. When we apply a credit, which is
00:07:11.368 --> 00:07:15.368 something that we're gonna have to keep our eyeballs on because
00:07:15.368 --> 00:07:18.868 we do credits applied upon payment. So when that client
00:07:18.868 --> 00:07:22.743 pays that invoice, we're going to come back in here just like
00:07:22.743 --> 00:07:26.430 we would with a change request. And we're gonna update the
00:07:26.430 --> 00:07:28.305 estimated hours per line item.
00:07:28.425 --> 00:07:33.055 So if you click into meetings and project management.
00:07:37.885 --> 00:07:43.502 Yes. So under the estimated hours for this activity, there
00:07:43.502 --> 00:07:48.833 is and maybe it's just my screen, but there's usually a
00:07:48.833 --> 00:07:49.785 box there.
00:07:49.905 --> 00:07:54.316 I don't think I have access because I have to be added to
00:07:53.585 --> 00:07:55.895 Ohh, got it. Got it. OK.
00:07:54.316 --> 00:07:56.065 this project I believe.
00:07:56.565 --> 00:07:59.785 I think I have access. If you want me to get to that point.
00:07:56.575 --> 00:07:57.105 Yes.
00:08:01.715 --> 00:08:02.085 Alright.
00:08:03.925 --> 00:08:04.595 I tried.
00:08:04.015 --> 00:08:04.845 On 2nd.
00:08:05.775 --> 00:08:09.204 Also, I think if you're logged in as PM team, but it may work
00:08:06.015 --> 00:08:06.905 Try to make sure.
00:08:09.204 --> 00:08:09.425 too.
00:08:15.835 --> 00:08:19.345 Also, the sheet I have pulled up I think because it didn't save
00:08:19.345 --> 00:08:22.800 cause uh everything crashed, but there was ohh you have it OK?
00:08:20.195 --> 00:08:22.305 That's OK, I have it somewhere.
00:08:22.800 --> 00:08:26.256 Because this one has 20, but I know it's up to 30 so I don't I
00:08:26.256 --> 00:08:29.821 just can't recall what the extra 10 if it all went to PM line or
00:08:26.675 --> 00:08:27.185 There we go.
00:08:29.821 --> 00:08:30.095 what.
00:08:30.065 --> 00:08:31.395 It did. Yep.
00:08:30.925 --> 00:08:31.195 OK.
00:08:33.405 --> 00:08:35.105 Alright, Jeff, there we go, yeah.
00:08:33.445 --> 00:08:37.357 There we go. So you can. Yeah. So you can see under the
00:08:34.985 --> 00:08:36.435 Oh, OK, you got it. Cool.
00:08:37.357 --> 00:08:41.129 estimated hours for this activity we have an edit box
00:08:41.129 --> 00:08:45.320 there. That is the original estimation that we uploaded the
00:08:45.320 --> 00:08:49.791 project with E uploaded into EP with the project hours. So when
00:08:49.791 --> 00:08:54.262 we do a credit and it goes to a specific line item, we're gonna
00:08:54.262 --> 00:08:58.244 update that. And then in the activity description, we're
00:08:58.244 --> 00:09:02.365 going to notate such and such amount of hours as a credit.
00:09:04.095 --> 00:09:07.977 That way the next time a you know if a project manager shifts
00:09:07.977 --> 00:09:11.734 on a project which you know there's enough of us and enough
00:09:11.734 --> 00:09:15.304 projects going around that shifts are going to happen on
00:09:15.304 --> 00:09:16.055 the regular.
00:09:18.255 --> 00:09:22.295 The next person that picks that up can see immediately. Ohh,
00:09:22.295 --> 00:09:26.666 this line item was credited, but it does balance and so the hours
00:09:26.666 --> 00:09:30.706 balance that you're seeing in the PSR with the credit is not
00:09:30.706 --> 00:09:34.415 gonna have that weird negative, which is something that
00:09:34.415 --> 00:09:38.455 traditionally we have never done. And this is something that
00:09:38.455 --> 00:09:42.628 we really need to start doing because it's going to make stuff
00:09:42.628 --> 00:09:46.933 so much cleaner when explaining to a client because they're just
00:09:46.933 --> 00:09:48.125 gonna see the red.
00:09:48.325 --> 00:09:52.085 In the PSR and be like, why is this over? And then we have to
00:09:52.085 --> 00:09:55.664 go back and be like well, but this is the line item that I
00:09:55.664 --> 00:09:59.546 credited and it it adds a layer of confusion and complexity for
00:09:59.546 --> 00:10:03.063 the client adds to your meeting times because you have to
00:10:03.063 --> 00:10:06.884 explain the same thing probably 15 times, which we all know we
00:10:06.884 --> 00:10:10.645 have to do anyway. It's that salt shaker, right. But the less
00:10:10.645 --> 00:10:14.163 you have to do that with the client, the better off we're
00:10:14.163 --> 00:10:17.862 going to be. So we're going to start adding the credits into
00:10:17.862 --> 00:10:18.105 the.
00:10:18.825 --> 00:10:21.869 Estimated hours so that it matches in the line items. Does
00:10:21.869 --> 00:10:23.365 that make sense to everybody?
00:10:25.355 --> 00:10:29.216 That's a huge help. Like I've never known what to do with
00:10:29.216 --> 00:10:30.215 those and it's.
00:10:30.945 --> 00:10:32.145 Like that makes sense.
00:10:33.105 --> 00:10:33.915 That's very cool.
00:10:34.445 --> 00:10:35.055 Yes.
00:10:34.535 --> 00:10:37.175 So we basically add those credited hours to the estimated.
00:10:37.655 --> 00:10:38.095 Uh-huh.
00:10:38.615 --> 00:10:41.850 Little box right there and make a note of the date. We did it
00:10:40.535 --> 00:10:41.105 Yep.
00:10:41.850 --> 00:10:42.215 on, OK.
00:10:42.775 --> 00:10:45.680 And then if your change request also encompasses project
00:10:45.680 --> 00:10:48.892 management in this case, which I believe it does, every change
00:10:48.892 --> 00:10:51.950 request should because we have that additional line item in
00:10:51.950 --> 00:10:55.059 there that also goes into those re estimates with a separate
00:10:55.059 --> 00:10:58.270 note that it says that it's part of the change request on that
00:10:58.270 --> 00:10:58.525 date.
00:10:59.115 --> 00:10:59.485 Mm-hmm.
00:11:00.995 --> 00:11:04.904 See and with this in particular, because those the invoices were
00:11:04.904 --> 00:11:08.212 split into and I did see that either broke or Caroline
00:11:08.212 --> 00:11:12.001 followed up on Basecamp today, and I think Stan is on, as they
00:11:12.001 --> 00:11:13.745 say in in the UK, on holiday.
00:11:15.255 --> 00:11:15.765 But.
00:11:15.965 --> 00:11:16.495 Do it again.
00:11:16.975 --> 00:11:17.925 On holiday.
00:11:19.325 --> 00:11:19.755 Thanks.
00:11:19.925 --> 00:11:23.495 But I think what's his name? The.
00:11:24.515 --> 00:11:27.560 Blanking on his name, but he responded and said that he sent
00:11:27.560 --> 00:11:30.755 it up to their accounts team. So what it makes sense to kind of
00:11:30.755 --> 00:11:33.950 just get ahead of it and Add all those like the from the change
00:11:33.950 --> 00:11:36.745 request and the credited hours just so EP looks normal.
00:11:37.355 --> 00:11:38.055 Might as well.
00:11:37.655 --> 00:11:38.775 Right. OK.
00:11:39.275 --> 00:11:42.845 It'll be easier for you to edit and verify what's coming next.
00:11:43.125 --> 00:11:43.435 Umm.
00:11:43.775 --> 00:11:47.135 Since we know that invoices on its way through the process.
00:11:47.405 --> 00:11:47.645 Yeah.
00:11:50.155 --> 00:11:50.815 Beautiful.
00:11:51.805 --> 00:11:52.405 All righty.
00:11:54.625 --> 00:11:54.995 So.
00:11:57.115 --> 00:12:00.775 Let me go back to who did you say would be better to pick on
00:12:00.775 --> 00:12:02.095 you with Charlie CMMC?
00:12:02.775 --> 00:12:06.705 Uh CMMC is clean. JBM is clean, you know.
00:12:07.175 --> 00:12:10.395 Alright, see, I'm gonna steal it here in a minute.
00:12:07.395 --> 00:12:08.575 He went the screen back.
00:12:10.805 --> 00:12:11.185 OK.
00:12:11.595 --> 00:12:11.955 Once.
00:12:12.205 --> 00:12:16.155 I get my navigation. Alrighty. Beautiful.
00:12:18.535 --> 00:12:18.905 So.
00:12:21.005 --> 00:12:26.315 Going back to cmmc, we have a positive balance on hand, so the
00:12:26.315 --> 00:12:31.793 next thing I'm gonna ask is what are how many hours do we intend
00:12:31.793 --> 00:12:37.271 to burn through the next? Well, we're mid month, but through the
00:12:37.271 --> 00:12:38.535 end of January.
00:12:39.075 --> 00:12:45.145 We are roughly on a 133 hour per Sprint allocation.
00:12:46.525 --> 00:12:51.598 So I don't know exactly based on where we are today, but we have
00:12:51.598 --> 00:12:53.315 an invoice in process.
00:12:54.095 --> 00:12:58.065 OK, so there is an outstanding invoice.
00:12:59.445 --> 00:13:03.136 So I'm going to come down and poke at that 267, so
00:13:03.136 --> 00:13:07.550 theoretically this should now does that invoice encompass or
00:13:07.550 --> 00:13:11.964 does that burn rate encompass the project management time on
00:13:11.964 --> 00:13:12.905 this as well?
00:13:13.425 --> 00:13:13.935 It does.
00:13:14.405 --> 00:13:15.425 Beautiful.
00:13:15.415 --> 00:13:16.225 It's everything.
00:13:16.795 --> 00:13:18.665 Beautiful. OK.
00:13:19.915 --> 00:13:25.326 So when we ask you the burn rate of a project, we need to make
00:13:25.326 --> 00:13:29.105 sure that the response encompasses QA time.
00:13:30.135 --> 00:13:32.825 PM time, which I'm gonna.
00:13:34.865 --> 00:13:38.485 Caroline or Daniel? Is he still on hold?
00:13:39.615 --> 00:13:41.585 Daniel's on hold. But I'm here. What do you need?
00:13:41.665 --> 00:13:46.192 OK, I'm trying to figure out my preference here with the QA time
00:13:46.192 --> 00:13:50.789 from the project management side and if we should be logging that
00:13:50.789 --> 00:13:55.107 to the QA line item or if we should. Yeah, I think that's the
00:13:54.475 --> 00:13:58.338 I feel like it should be logged towards the QA line item as
00:13:55.107 --> 00:13:55.455 move.
00:13:58.338 --> 00:13:59.625 specific like to QA.
00:13:59.865 --> 00:14:03.320 As soon as I set it out of my mouth, I was like ohh protect
00:14:03.320 --> 00:14:07.062 your PM time. Yes that needs to be logged anytime you're doing a
00:14:07.062 --> 00:14:10.748 QA run through on a site, you're doing your code completes that
00:14:10.748 --> 00:14:14.375 kind of stuff that's gonna be logged to the QA line item when.
00:14:13.895 --> 00:14:17.649 I'll have to make some changes. I did 7 hours of QA on bid
00:14:13.925 --> 00:14:15.135 I also think that will.
00:14:17.649 --> 00:14:18.285 yesterday.
00:14:18.455 --> 00:14:20.445 And did you just put it on PM time?
00:14:20.645 --> 00:14:21.615 Yeah, totally.
00:14:21.955 --> 00:14:24.455 Yeah, I think it also just makes sense because.
00:14:22.535 --> 00:14:26.626 Now that's detailed in my notes. So like I I can look it right
00:14:26.626 --> 00:14:27.925 back up, but whoops.
00:14:27.585 --> 00:14:30.846 Oh yeah, it'll be easy to reallocate, but I think that
00:14:30.846 --> 00:14:34.759 will also help, because whenever at least what I would imagine is
00:14:34.759 --> 00:14:38.553 if you have a conversation with the client and they are wanting
00:14:38.553 --> 00:14:42.229 our team to do more of the QA versus if they want to do a lot
00:14:42.229 --> 00:14:45.846 of the QA, we could probably like estimate the hours for any
00:14:45.846 --> 00:14:49.581 change requests and then make sure y'all shows in the PSR that
00:14:49.581 --> 00:14:50.055 way too.
00:14:50.285 --> 00:14:52.655 Beautiful. Yeah. As soon as it came out of my mouth.
00:14:51.305 --> 00:14:52.525 Wait. Code complete.
00:14:53.265 --> 00:14:55.565 Cocomplete audits could fall under QA.
00:14:55.945 --> 00:14:57.225 The potentially.
00:14:57.955 --> 00:15:01.145 I don't. I haven't fully decided on code complete yet.
00:15:02.265 --> 00:15:02.655 OK.
00:15:03.905 --> 00:15:05.105 Jessica, you're hands up.
00:15:07.215 --> 00:15:10.972 Yes. So when we were talking about ADI, you said anything
00:15:10.972 --> 00:15:15.183 that I'm that I am touching the project on even if it's relating
00:15:15.183 --> 00:15:19.135 to another line you want it under PM work. Is it because you
00:15:19.135 --> 00:15:23.022 had more hours like meetings versus PM work we buffered for
00:15:23.022 --> 00:15:26.585 the PM side of things even though I'm doing a meeting.
00:15:24.645 --> 00:15:25.355 Umm.
00:15:26.955 --> 00:15:28.005 Excellent call out.
00:15:28.105 --> 00:15:30.215 Umm so.
00:15:31.525 --> 00:15:36.105 The vast majority of everything that you guys touch is going to
00:15:36.105 --> 00:15:40.327 be under the PM line. The only exception to that really is
00:15:40.327 --> 00:15:44.620 going to be if you are actively doing something in DNN that
00:15:44.620 --> 00:15:48.914 would be like development work for the client or if you are
00:15:48.914 --> 00:15:52.993 doing QA. In the case of ADI, they are a little bit of a
00:15:52.993 --> 00:15:53.565 special.
00:15:54.685 --> 00:15:58.933 Situation because they actually go back through and audit all of
00:15:58.933 --> 00:16:02.724 the work. So most of the time we're completing stuff in a
00:16:02.724 --> 00:16:06.842 working session and then letting them know that it's available
00:16:06.842 --> 00:16:10.829 for them on stage and then they go in and they test and they
00:16:10.829 --> 00:16:14.881 audit and they send the reports back. So they're doing all of
00:16:14.355 --> 00:16:14.645 Mm-hmm.
00:16:14.881 --> 00:16:15.535 their own.
00:16:18.415 --> 00:16:22.071 OK, so in yes completely and there has been a couple other
00:16:18.505 --> 00:16:19.435 Does that make sense?
00:16:22.071 --> 00:16:26.099 ones in the past few weeks. I I can't tell you at the moment who
00:16:26.099 --> 00:16:29.941 they were, but there have been a couple lines where I've been
00:16:29.941 --> 00:16:33.783 told assign it to PM lines and so is that kind of our call or
00:16:33.783 --> 00:16:37.253 is it depend on how many hours are on hand like between
00:16:37.253 --> 00:16:41.281 meetings and PM work or whatever we're having to do towards that
00:16:41.281 --> 00:16:45.185 specific job is that our call is that something that we should
00:16:45.185 --> 00:16:48.655 run through you to approve before we do it differently?
00:16:50.055 --> 00:16:53.944 Interesting. So meetings and I'm I'm curious like what the
00:16:53.944 --> 00:16:58.164 specifics were on that because meetings is a project management
00:16:58.164 --> 00:17:02.317 thing like do your project if you're doing just like a project
00:17:02.317 --> 00:17:06.602 update like you're meeting with the client, just give them their
00:17:06.602 --> 00:17:10.557 status update, let them know what's going on in the Sprint,
00:17:10.557 --> 00:17:14.512 all of that kind of stuff that absolutely from this team is
00:17:14.512 --> 00:17:15.765 project management.
00:17:17.285 --> 00:17:21.928 If you have developers on that call or you have leadership on
00:17:21.928 --> 00:17:26.795 that call or you have BA on that call, those are the people that
00:17:26.795 --> 00:17:30.015 are gonna be logging to that meeting line.
00:17:31.085 --> 00:17:34.869 OK, so I made to do any I may need to do an EP audit because
00:17:34.869 --> 00:17:38.716 of myself because there is some, I know GFS, I've done it and
00:17:38.716 --> 00:17:41.135 then I believe with ANAE I've done it.
00:17:41.825 --> 00:17:45.975 Umm for calls that I've logged to meetings.
00:17:47.305 --> 00:17:50.007 I'll have to go back through and look. So that's why I was
00:17:50.007 --> 00:17:52.755 curious about about that one, just to double check my work.
00:17:50.095 --> 00:17:50.515 Yeah.
00:17:51.265 --> 00:17:52.475 Yeah, absolutely.
00:17:53.565 --> 00:17:53.915 Thank you.
00:17:53.975 --> 00:17:57.551 Thank you. Yeah, if you don't mind, just doing a quick audit
00:17:57.551 --> 00:18:01.186 that would be fantastic. But yeah, from our perspective, even
00:18:01.186 --> 00:18:04.938 if we're running the meeting and it technically is, you're dead
00:18:04.938 --> 00:18:08.514 on, it's a meeting, but we want to reserve that time for the
00:18:08.514 --> 00:18:12.031 other folks because it does fall in line with what we would
00:18:12.031 --> 00:18:14.845 normally need to do to conduct the project, so.
00:18:14.705 --> 00:18:15.305 Makes sense?
00:18:20.915 --> 00:18:25.280 Additional 10 hour credit would go towards the meeting project
00:18:25.280 --> 00:18:29.575 management customization line item Amy with that one there is
00:18:29.575 --> 00:18:33.455 an internal there are two project management line items
00:18:33.455 --> 00:18:36.365 and So what I want you to do is actually.
00:18:37.985 --> 00:18:40.535 You know split out the.
00:18:42.145 --> 00:18:46.316 The amount that we're getting from the invoice as well as the
00:18:46.316 --> 00:18:50.218 amount of the credit to make sure that both of those line
00:18:50.218 --> 00:18:54.389 items are not negative or not over on their estimations. Does
00:18:54.389 --> 00:18:55.465 that make sense?
00:18:56.655 --> 00:19:00.512 And then close out one of them so that we're only logging to
00:18:57.015 --> 00:18:58.155 Yes.
00:19:00.512 --> 00:19:04.432 one. So make sure that one of them has any additional balance
00:19:04.432 --> 00:19:08.100 and is, you know, has more of an estimate and then one is
00:19:08.100 --> 00:19:11.514 completely closed out just to keep it cleaner like we
00:19:11.514 --> 00:19:15.245 shouldn't have it split out into two line items like that.
00:19:15.995 --> 00:19:19.639 OK. Because that that the thing with that in what's in EP, all
00:19:19.639 --> 00:19:23.225 the other ones are closed out. The only one that's still open
00:19:23.225 --> 00:19:26.117 right now is that meetings in project management,
00:19:26.117 --> 00:19:27.505 customization line item.
00:19:27.895 --> 00:19:28.295 OK.
00:19:28.185 --> 00:19:30.810 So that's where I'm wondering like would it makes sense to
00:19:30.810 --> 00:19:33.035 have the credit to there because it's closed out?
00:19:34.505 --> 00:19:35.235 Is it over?
00:19:36.535 --> 00:19:38.185 Yeah, all all of them are over, I think.
00:19:38.595 --> 00:19:39.285 OK. Yeah.
00:19:41.665 --> 00:19:46.622 Get it? Just closed out to, like up a balance so that it's, you
00:19:46.622 --> 00:19:51.347 know, if it was 10.25 hours or whatever, get it to where the
00:19:51.347 --> 00:19:53.825 it's 10.25 estimated 10.25 used.
00:19:54.815 --> 00:20:00.229 And then put whatever remainder is left from the change request
00:20:00.229 --> 00:20:05.305 and credit for those line items to the active PM line item.
00:20:07.135 --> 00:20:07.425 OK.
00:20:08.535 --> 00:20:09.555 So I have a question.
00:20:10.035 --> 00:20:10.295 OK.
00:20:11.495 --> 00:20:16.134 If, for example, uh, when Amy, if Amy was to go and close out
00:20:16.134 --> 00:20:20.323 one of those extra project management line items and it
00:20:20.323 --> 00:20:25.037 didn't have a, it wasn't over and say it had like 2 hours left
00:20:25.037 --> 00:20:29.526 on it, can you pull those two hours from that and put it on
00:20:29.526 --> 00:20:29.825 the?
00:20:30.715 --> 00:20:33.205 The project management line item that's still open.
00:20:33.525 --> 00:20:34.895 10 million percent yes.
00:20:35.185 --> 00:20:35.525 OK.
00:20:35.365 --> 00:20:36.655 And like percent.
00:20:38.645 --> 00:20:40.395 All the yes please do.
00:20:41.625 --> 00:20:42.605 OK, cool.
00:20:45.335 --> 00:20:50.909 So the next thing that I want us to be going through when we're
00:20:50.909 --> 00:20:54.045 reviewing all of this is comparing.
00:20:56.615 --> 00:21:00.700 Where we actually went over individually in the Sprint. So
00:21:00.700 --> 00:21:04.923 this is one of the things that historically we just have not
00:21:04.923 --> 00:21:05.685 been doing.
00:21:08.315 --> 00:21:10.525 Well enough as a group.
00:21:11.615 --> 00:21:14.835 And I certainly include myself in there.
00:21:16.505 --> 00:21:20.474 We need to be reviewing our tickets. Uh, with our developers
00:21:20.474 --> 00:21:24.573 on the regular and making sure that we are calling out any you
00:21:24.573 --> 00:21:28.541 know, if do you need more time on this? What's going on with
00:21:28.541 --> 00:21:32.445 this ticket? If we notice that things are getting close to.
00:21:33.525 --> 00:21:36.860 Being exceeding their estimations because knowledge is
00:21:36.860 --> 00:21:40.741 power and the faster you can get ahead of something, the better
00:21:40.741 --> 00:21:42.075 off we're gonna be so.
00:21:43.015 --> 00:21:47.820 We know that this particular ticket went over well. Let's do
00:21:47.820 --> 00:21:52.547 this one uh, we know that this went over by one hour and 15
00:21:52.547 --> 00:21:57.667 minutes, but this one went under and is also closed out. But are
00:21:57.667 --> 00:22:00.345 they assigned to the same person?
00:22:01.045 --> 00:22:05.822 No, but still within our hours we have a little bit of wiggle
00:22:05.822 --> 00:22:09.675 room there. So have I completely lost all of you.
00:22:10.765 --> 00:22:11.395 Hmm.
00:22:11.875 --> 00:22:12.315 Umm.
00:22:12.285 --> 00:22:13.835 No, but.
00:22:13.765 --> 00:22:14.255 I'm with you.
00:22:16.615 --> 00:22:17.465 I was going to say.
00:22:19.615 --> 00:22:22.509 Definitely go on this with the step, but I can just give you
00:22:22.509 --> 00:22:23.505 guys this report too.
00:22:24.015 --> 00:22:24.545 Mm-hmm.
00:22:25.445 --> 00:22:28.348 Yeah. So sorry. Go on about, I'll quick whip one up for last
00:22:25.485 --> 00:22:26.335 Yeah.
00:22:28.348 --> 00:22:31.394 Sprint and rip that up for you guys right now and you can get a
00:22:31.394 --> 00:22:34.393 look at it for that. And I can keep on doing this every Sprint
00:22:34.393 --> 00:22:36.725 because I already do it. The send it to you all.
00:22:37.405 --> 00:22:43.005 Beautiful love that so we need to know why.
00:22:44.045 --> 00:22:45.485 The sprintly support.
00:22:46.365 --> 00:22:49.575 Was exceeded by 3 1/2 hours.
00:22:50.775 --> 00:22:54.771 And if we had hours on hand to accommodate that, if that's
00:22:54.771 --> 00:22:58.767 going to cause any issues downstream with CMMC, they're in
00:22:58.767 --> 00:23:02.898 a little bit of a different cadence. But when you're working
00:23:02.898 --> 00:23:06.827 in active development against stories that are not like a
00:23:06.827 --> 00:23:10.958 bucket ticket where we're just like, oh, I think we're gonna
00:23:10.958 --> 00:23:13.735 need about this much time in the Sprint.
00:23:14.855 --> 00:23:17.815 Which hopefully none of us are doing it quite that.
00:23:19.855 --> 00:23:20.235 You know.
00:23:21.425 --> 00:23:26.203 Unorganized, but we're actually planning out approximately how
00:23:26.203 --> 00:23:27.795 much we'll need, but.
00:23:29.255 --> 00:23:32.325 If we're going against a feature that was.
00:23:33.275 --> 00:23:38.056 Very specifically estimated out, and it starts to exceed. That's
00:23:38.056 --> 00:23:42.470 our cue right there that if we went over on this particular
00:23:42.470 --> 00:23:46.957 task, there's a good chance that we're gonna go over on this
00:23:46.957 --> 00:23:47.545 feature.
00:23:48.285 --> 00:23:53.565 Especially as we are closing out the majority of the tickets with
00:23:53.565 --> 00:23:58.445 it a given feature, because remember our goal is to actually
00:23:58.445 --> 00:24:02.845 have our sprints planned in a way so that we're doing.
00:24:02.965 --> 00:24:07.205 Uh, you know, feature completion at the end of a Sprint.
00:24:08.365 --> 00:24:11.579 So if we know we're going over on one ticket, we know that that
00:24:11.579 --> 00:24:12.985 feature is going to go over.
00:24:13.675 --> 00:24:17.135 Which means we're likely going to need a change request for
00:24:17.135 --> 00:24:17.885 that feature.
00:24:19.285 --> 00:24:23.551 Even if they have hours on hand, even if it's, you know, the
00:24:23.551 --> 00:24:27.816 CMMC's of the world and and we've got a specific cadence, we
00:24:27.816 --> 00:24:32.362 know that if we're going over on this task that is associated to
00:24:32.362 --> 00:24:36.627 this feature, this feature is going to be exceeded. But that
00:24:36.627 --> 00:24:40.893 doesn't mean that even if I have hours on hand, I can ignore
00:24:40.893 --> 00:24:45.298 this. So we need to get ahead of it at the beginning and start
00:24:45.298 --> 00:24:48.655 paying more attention to this. So every Sprint.
00:24:48.735 --> 00:24:51.685 I want us to have a rolling change request with anything
00:24:51.685 --> 00:24:53.755 that exceeded from the previous Sprint.
00:24:54.795 --> 00:24:58.158 So that we can communicate that to the clients and even if we're
00:24:58.158 --> 00:24:58.365 not.
00:24:59.205 --> 00:25:02.474 Directly invoicing at that time, at least having that
00:25:02.474 --> 00:25:06.348 documentation running and being able to address it. Sprint over
00:25:06.348 --> 00:25:09.980 Sprint in every one of your BI weeklies with the client, so
00:25:09.980 --> 00:25:13.612 that they're up to speed on everything that's going on. And
00:25:13.612 --> 00:25:17.365 if we're keeping our side of the street clean with the PSR's.
00:25:18.045 --> 00:25:20.675 And we're able to speak to that each time.
00:25:22.175 --> 00:25:25.235 Then when we do present them with a change request, it's
00:25:25.235 --> 00:25:26.845 going to go much easier Micki.
00:25:29.205 --> 00:25:32.805 When you have a feature that's not being completed but it's
00:25:32.805 --> 00:25:36.465 already going over what when is the proper time to call that
00:25:36.465 --> 00:25:36.705 out?
00:25:37.165 --> 00:25:37.855 Immediately.
00:25:39.985 --> 00:25:43.509 So would you be looking for a developer to give you a estimate
00:25:40.175 --> 00:25:41.755 As soon as you see it.
00:25:43.509 --> 00:25:46.530 on what remains instead of having to go to them three
00:25:46.525 --> 00:25:47.095 Ah.
00:25:46.530 --> 00:25:49.830 different times to be like? Well, now we're six hours over
00:25:49.830 --> 00:25:52.795 now we're 12 hours over and now we're 22 hours over.
00:25:53.385 --> 00:25:56.015 100% I would try to get.
00:25:57.805 --> 00:26:02.331 A conservative but in the opposite? Well, what would be
00:26:02.331 --> 00:26:04.675 the opposite of verbose like?
00:26:06.555 --> 00:26:10.679 Estimation like, yeah, yeah. Get some padding on that so that you
00:26:07.245 --> 00:26:08.415 Worst case scenario.
00:26:09.135 --> 00:26:09.515 Yeah.
00:26:10.679 --> 00:26:13.365 don't have to continue to nickel and dime.
00:26:14.135 --> 00:26:15.295 Gotcha. Heard.
00:26:15.835 --> 00:26:21.592 I think it's also dependent on how big is the feature, like if
00:26:21.592 --> 00:26:27.440 you're over on a task and it's one task and one user story, and
00:26:27.440 --> 00:26:33.014 they're five stories in the feature that's different than if
00:26:33.014 --> 00:26:38.680 it's a 20 story feature, you know, like it can only expand so
00:26:38.680 --> 00:26:43.523 much. If it's a small small count of overall stories
00:26:43.523 --> 00:26:44.345 involved.
00:26:45.685 --> 00:26:50.455 Agreed. So there was one that Amy and I were working on.
00:26:51.925 --> 00:26:56.010 I want to say it was either proper handy. I don't know why
00:26:56.010 --> 00:27:00.302 PROP handy and step are merged into one project for my brain,
00:27:00.302 --> 00:27:04.594 but we were working on one of them and there's an outstanding
00:27:04.594 --> 00:27:06.325 change request and where?
00:27:07.445 --> 00:27:11.613 Are we were prepping a change request because it was starting
00:27:11.613 --> 00:27:15.512 to go over, but there's still active work going on in the
00:27:15.512 --> 00:27:19.680 Sprint and so the call out was like, eh, we could send them a
00:27:19.680 --> 00:27:23.848 change request for this right now in this moment or we. Yeah.
00:27:21.615 --> 00:27:22.775 Yeah, that's where IDs.
00:27:23.848 --> 00:27:24.655 IDs. Thanks.
00:27:25.915 --> 00:27:29.913 Or we know that there's still at least an hour and a half of
00:27:29.913 --> 00:27:33.911 work, so rather than go into them to be like we're two hours
00:27:33.911 --> 00:27:38.171 over on this particular feature, but there's still an hour and a
00:27:38.171 --> 00:27:42.497 half remaining, can we get 2 1/2 hours now and then an hour and a
00:27:42.497 --> 00:27:46.560 half once it's completed, let's just wait till the end of the
00:27:46.560 --> 00:27:50.493 Sprint. Like use your best judgment. There's never going to
00:27:50.493 --> 00:27:54.491 be 100% perfect solution, but the idea behind this is really
00:27:54.491 --> 00:27:56.195 what I want to drive home.
00:27:56.425 --> 00:28:00.872 The idea of getting ahead of the problem before it becomes a
00:28:00.872 --> 00:28:05.391 problem, so if you are actively creating a change request for
00:28:05.391 --> 00:28:09.255 anything that was in the last Sprint that went over.
00:28:10.835 --> 00:28:14.811 It doesn't mean that you have to present it to the client that
00:28:14.811 --> 00:28:18.851 particular day, but it's keeping a rolling log and it's keeping
00:28:18.851 --> 00:28:22.385 it open and active, something that you have as tangible
00:28:22.385 --> 00:28:26.361 physical evidence to be able to trigger your brain. Oh, I have
00:28:26.361 --> 00:28:30.022 to address this. I have to go present this to the client.
00:28:30.022 --> 00:28:33.872 That's gonna make you bring it up in the biweekly with them.
00:28:33.872 --> 00:28:37.533 That's gonna trigger that conversation, which is going to
00:28:37.533 --> 00:28:41.256 eliminate surprises. So that when we do present the change
00:28:41.256 --> 00:28:42.645 request, there's less.
00:28:42.735 --> 00:28:44.365 Opportunity for pushback.
00:28:44.845 --> 00:28:50.783 Umm, I wanna say that it might have been RIE or one of Mickey's
00:28:50.783 --> 00:28:56.814 projects. We were we were doing something very similar where she
00:28:56.814 --> 00:28:58.855 had bit. Yeah, it was.
00:29:00.125 --> 00:29:01.975 Our IE I set it right, yes.
00:29:04.075 --> 00:29:08.682 It's RIE, where in every single project status update that she
00:29:08.682 --> 00:29:13.069 did, she kept a list in the agenda of all of the items that
00:29:13.069 --> 00:29:17.384 we're going over. So we had a really extensive, very large
00:29:17.384 --> 00:29:20.455 change request that we presented to them.
00:29:21.675 --> 00:29:25.970 And I'm sure that most of us on this call know from experience,
00:29:25.970 --> 00:29:30.264 the larger the change request, the scarier the conversation. So
00:29:30.264 --> 00:29:34.424 we do wanna keep it somewhat small and present them often and
00:29:34.424 --> 00:29:38.517 early just to get them in the cadence. But if you're talking
00:29:38.517 --> 00:29:40.195 about it every two weeks.
00:29:41.005 --> 00:29:45.379 There's no way that this isn't syncing in with them, that they
00:29:45.379 --> 00:29:49.822 know that it's coming and just prewiring the client because the
00:29:49.822 --> 00:29:53.848 worst thing that we can do for client SAT is to just keep
00:29:53.848 --> 00:29:58.153 kicking the can down the road. Everything's fine. Here's your
00:29:58.153 --> 00:30:02.387 status update. Everything's fine. Here's your status update.
00:30:02.387 --> 00:30:02.665 Ohh.
00:30:03.545 --> 00:30:06.863 Here we have to pause your project and here's a giant
00:30:06.863 --> 00:30:10.858 change request. You, as a ton of money and they have no idea why
00:30:10.858 --> 00:30:11.595 and then it.
00:30:11.255 --> 00:30:12.545 That's what happened with writer.
00:30:12.825 --> 00:30:14.515 Yeah. And then it becomes.
00:30:13.855 --> 00:30:14.325 Dude.
00:30:16.395 --> 00:30:17.045 Dude.
00:30:17.325 --> 00:30:20.475 Dude, it's not just, I mean, yeah.
00:30:19.805 --> 00:30:21.035 No, like.
00:30:22.015 --> 00:30:25.959 Then it becomes a thing of having to go back through the
00:30:25.959 --> 00:30:30.110 history of the project and figure out where things went off
00:30:30.110 --> 00:30:34.054 the rails. So it's very similar to losing or having your
00:30:34.054 --> 00:30:38.344 computer crash where you lost all your time logs for a day or
00:30:38.344 --> 00:30:42.426 what Daniel was speaking to earlier. The little steps that
00:30:42.426 --> 00:30:46.923 we can take right now, every two weeks with our clients is going
00:30:46.923 --> 00:30:50.936 to save so much time in the future because it can take me
00:30:50.936 --> 00:30:51.905 anywhere from.
00:30:52.065 --> 00:30:56.863 15 minutes to five hours to put together a timeline for an
00:30:56.863 --> 00:30:58.245 escalated client.
00:30:59.265 --> 00:31:02.595 And that's billable too, which just means you're change request
00:31:02.595 --> 00:31:06.029 is gonna have to increase, which means that conversation is going
00:31:06.029 --> 00:31:06.705 to be harder.
00:31:09.525 --> 00:31:10.145 Claire's mad.
00:31:10.935 --> 00:31:13.998 So that's kind of like situation earlier today when I was looking
00:31:13.998 --> 00:31:16.921 at EP and then Azure and also asked you to do that or like the
00:31:16.921 --> 00:31:19.473 query that to see like the Sprint report. So I've been
00:31:19.473 --> 00:31:22.350 trying to stay on top because I Austin definitely let me know
00:31:22.350 --> 00:31:23.835 this week that things went over.
00:31:25.085 --> 00:31:25.545 Mm-hmm.
00:31:25.345 --> 00:31:28.381 On some of these, some of the things that were in the last
00:31:28.381 --> 00:31:31.519 Sprint, but then the part that I'm for my brains breaking is
00:31:31.519 --> 00:31:34.864 like because some of these have been kind of pushed from the the
00:31:34.864 --> 00:31:38.105 previous Sprint into the last Sprint. So that's where like the
00:31:38.105 --> 00:31:40.215 disconnect where I'm like, I'm not sure.
00:31:40.955 --> 00:31:43.545 Like, obviously there's overages. I know there's been
00:31:43.545 --> 00:31:46.663 overages because I could look at EP and see. But then in regards
00:31:46.663 --> 00:31:49.493 to like what went over in the specific Sprint is where I'm
00:31:49.493 --> 00:31:50.165 getting a bit.
00:31:51.215 --> 00:31:51.995 Unclear.
00:31:52.905 --> 00:31:53.615 Like mud.
00:31:53.525 --> 00:31:53.915 So.
00:31:55.275 --> 00:31:59.832 So in that aspect, and that's why we have to pick somewhere to
00:31:59.832 --> 00:32:04.173 start and because we haven't been traditionally doing this,
00:32:04.173 --> 00:32:08.585 what I want to get us to just out of forced habit doing this
00:32:08.585 --> 00:32:13.070 every other Friday is that it becomes a two week cadence. But
00:32:13.070 --> 00:32:16.615 to begin with, we're gonna have to go back like.
00:32:18.405 --> 00:32:22.815 What I want to see little piece of homework for everybody.
00:32:24.205 --> 00:32:28.135 And I'll stop talking here in a minute and give you some heads
00:32:28.135 --> 00:32:32.065 down. Time to do that and ask any questions that come up while
00:32:32.065 --> 00:32:36.120 you're working through this. Is that by the end of shred session
00:32:36.120 --> 00:32:40.051 on Monday, you guys have like a rolling change request kind of
00:32:40.051 --> 00:32:43.981 set up for all of your clients. We know what the current hours
00:32:43.981 --> 00:32:47.724 balance is, what's planned in this current Sprint and where
00:32:47.724 --> 00:32:51.779 the overages have gone to date. So we can't, I mean, yes, we can
00:32:51.779 --> 00:32:55.397 get more detailed and more granular and look, Sprint over
00:32:55.397 --> 00:32:57.955 Sprint and see where those overages are.
00:32:58.175 --> 00:33:02.420 But we have to start somewhere, so I'd rather us on this first
00:33:02.420 --> 00:33:06.329 week start with where the overages are to date so that we
00:33:06.329 --> 00:33:10.305 can work through that change request and then starting off
00:33:10.305 --> 00:33:14.550 next time we meet about this, we'll be able to go back, OK, we
00:33:14.550 --> 00:33:17.785 did this for the Sprint that ended on the 17th.
00:33:18.075 --> 00:33:18.805 17th.
00:33:19.195 --> 00:33:20.855 And So what big studio?
00:33:21.175 --> 00:33:21.825 Of course.
00:33:21.625 --> 00:33:26.098 You know, I don't know why today's like March 297th of
00:33:26.098 --> 00:33:26.505 2020.
00:33:29.805 --> 00:33:33.377 So we'll start on the 18th and we'll just review everything
00:33:33.377 --> 00:33:37.067 that happened over the last two weeks. So this time around is
00:33:37.067 --> 00:33:40.758 gonna be a little bit tricky, but my goal is that you guys go
00:33:40.758 --> 00:33:43.615 back through, run this all just go run the CRM.
00:33:45.075 --> 00:33:48.658 While we're doing this, so pull your latest project status
00:33:48.658 --> 00:33:52.484 report, review the line items that are in there, get a rolling
00:33:52.484 --> 00:33:56.067 change request and create that for any line items that are
00:33:56.067 --> 00:33:57.585 over. If your project is.
00:33:59.045 --> 00:34:02.165 You know already on a very specific cadence for those of us
00:34:02.165 --> 00:34:04.505 that have had some things going for a while.
00:34:05.035 --> 00:34:09.101 Uh, you know, feel free to just kind of annotate that, but I do
00:34:09.101 --> 00:34:12.914 want everybody to complete this exercise just to get in the
00:34:12.914 --> 00:34:13.295 habit.
00:34:14.765 --> 00:34:15.355 So.
00:34:17.305 --> 00:34:20.803 I will stop talking for a minute and just kind of let you guys
00:34:20.803 --> 00:34:24.411 get heads down into doing that, but does everybody have a pretty
00:34:24.411 --> 00:34:26.965 good idea of what it is that I'm looking for?
00:34:30.865 --> 00:34:32.135 That's questions concerned.
00:34:37.015 --> 00:34:38.695 Do you want me to just do this for DERM?
00:34:41.135 --> 00:34:41.465 Cool.
00:34:53.625 --> 00:34:56.645 When was the last time we cleaned that up? I want to say
00:34:56.645 --> 00:34:59.558 it was December, so I would go back to like the 1st of
00:34:59.558 --> 00:35:00.035 December.
00:35:00.715 --> 00:35:01.055 OK.
00:35:10.365 --> 00:35:11.615 In what?
00:35:11.695 --> 00:35:13.745 To to related to delete it.
00:35:15.555 --> 00:35:17.505 I'm going to click show you guys this so.